Isolate A Vcenter Server Instance From A Linked Mode Group - VMware ESX 4.0 - INSTALLATION GUIDE UPDATE 1 Installation Manual

ESX and vCenter Server Installation Guide
6 If the vCenter Server installer detects a role conflict, select how to resolve the conflict.
Option
Yes, let VMware vCenter Server
resolve the conflicts for me
No, I'll resolve the conflicts myself
A conflict results if the joining system and the Linked Mode group each contain a role with the same name
but with different privileges.
7 Click Finish.
vCenter Server restarts. Depending on the size of your inventory, the change to Linked Mode might take
from a few seconds to a few minutes to complete.
The vCenter Server instance is now part of a Linked Mode group. After you form a Linked Mode group, you
can log in to any single instance of vCenter Server and view and manage the inventories of all the vCenter
Servers in the group. 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.
What to do next
For information about configuring and using your Linked Mode group, see Basic System Administration.

Isolate a vCenter Server Instance from a Linked Mode Group

You can isolate a vCenter Server instance from a Linked Mode group.
Procedure
1 Select Start > All Programs > VMware > vCenter Server Linked Mode Configuration.
2 Click Modify linked mode configuration and click Next.
3 Click Isolate this vCenter Server instance from linked mode group and click Next.
4 Click Continue and click Finish.
vCenter Server restarts. Depending on the size of your inventory, the change to Linked Mode might take
from a few seconds to a few minutes to complete.
The vCenter Server instance is no longer part of the Linked Mode group.
112
Description
Click Next.
The role on the joining system is renamed to <vcenter_name> <role_name>,
where <vcenter_name> is the name of the vCenter Server system that is joining
the Linked Mode group, and <role_name> is the name of the original role.
To resolve the conflicts manually:
a Using the vSphere Client, log in to one of the vCenter Server systems
using an account with Administrator privileges.
b Rename the conflicting role.
c Close the vSphere Client session and return to the vCenter Server
installer.
d Click Back and click Next.
The installation continues without conflicts.
VMware, Inc.