How to solve the "The specified displayname is already in use by another agent" issue when protecting VMs agentlessly (4040482)

Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

How to solve the "The specified displayname is already in use by another agent" issue when protecting VMs agentlessly
Description

You are using a VCenter Server to access your VMWare environment. The VCenter server is already protected using the agent software.You attempt to protect VMs agentlessly
You try to use the VCenter in this respect. Protection fails for ALL VMs with “duplicate display name” although none of these machines was previously protected using agent software.
Cause

The issue is caused by attempting to use the display name of the VCenter twice:
1. For the protected VCenter
2. For the Top-Most node of agentless VMs shown in the GUI
The displayed error message "The specified displayname is already in use by another agent" although correct, is misleading. It suggest that the issue lays with any of the VM which needs to be protected when in fact the VCenter display name is the issue.
Resolution
To solve the issue:
- Identify the vCenter in the list of already protected machines.
- Change its display name in the Rapid Recovery GUI
  - Select the vCenter (In the protected server list) & click on the arrow to open the pull down menu.
  - Click settings in the pull down menu
  - Click "display name" in the General section and change the display name of the vCenter
Alternatively, you may protect the the VCenter using its IP address and change the display name the same way as above after the protection job is finished.
You should be able to protect VMs via the Agentless option now.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

How to solve the "The specified displayname is already in use by another agent" issue when protecting VMs agentlessly (4040482)

Title

Description

Cause

Resolution

Leave a Comment