• Preetam Zare

Join a Linked Mode Group After Installation

After installing vCenter Server, you can join a vCenter Server to a Linked Mode group.


1. Select Start > All Programs > VMware > vCenter Server Linked Mode Configuration.

2. Click Next.

3. Select Modify linked mode configuration and click Next.

4. Click Join this vCenter Server instance to an existing linked mode group or another instance and click Next.

Enter the server name and LDAP port number of a remote vCenter Server instance that is a member of the group and click Next.If you enter an IP address for the remote server, the installer converts it into a fully qualified domain name.

5. If the vCenter Server installer detects a role conflict, select how to resolve the conflict.A conflict results if the joining system and the Linked Mode group each contain a role with the same name but with different privileges.

If the roles defined on each vCenter Server system are different, the roles lists of the systems are combined into a single common list. For example, if vCenter Server 1 has a role named Role A and vCenter Server 2 has a role named Role B, then both servers will have both Role A and Role B after they are joined in a linked mode group. If you remove a vCenter Server system from a linked mode group, the vCenter Server system retains all the roles it had as part of the group. vCenter Server restarts. Depending on the size of your inventory, the change to Linked Mode might takefrom a few seconds to a few minutes to complete.

Post configurations

It might take several seconds for the global data (such as user roles) that are changed on one machine to be visible on the other machines. The delay is usually 15 seconds or less. It might take a few minutes for a new vCenter Server instance to be recognized and published by the existing instances, because group members do not read the global data very often.

Share this:

  1. Facebook

  2. LinkedIn

  3. Twitter

  4. WhatsApp

  5. Reddit

#LinkedMode #vCenter #VCP510 #vSphere50


©2019 by virtual2Cloud. Proudly created with