Installation guide

To resolve this issue, make sure that the Virtualcenter.VimApiUrl key points to the location where the
vSphere Client and SDK clients can access the vCenter Server system, and the
Virtualcenter.VimWebServicesUrl key points to the location where vCenter Server Webservices is
installed. For the Virtualcenter.Instancename key, change the value so that the modified name appears in
the vCenter Server inventory view.
n
If you cannot join a vCenter Server instance, you can resolve the problem with the following actions:
n
Ensure that the machine is grouped into the correct organizational unit in the corresponding domain
controller.
n
When you install vCenter Server, ensure that the logged in user account has administrator privileges
on the machine.
n
To resolve trust problems between a machine and the domain controller, remove the machine from
the domain and then add it to the domain again.
n
To ensure that the Windows policy cache is updated, run the gpupdate /force command from the
Windows command line. This command performs a group policy update.
n
If the local host cannot reach the remote host during a join operation, verify the following:
n
Remote vCenter Server IP address or fully qualified domain name is correct.
n
LDAP port on the remote vCenter Server is correct.
n
VMwareVCMSDS service is running.
n
Make sure your Windows and network-based firewalls are configured to allow Linked Mode.
Configuring a Windows Firewall to Allow a Specified Program Access
vCenter Server 4.0 uses Microsoft ADAM/AD LDS to enable Linked Mode, which uses the Windows RPC port
mapper to open RPC ports for replication. When you install vCenter Server in Linked Mode, the firewall
configuration on the local machine must be modified.
Incorrect configuration of firewalls can cause licenses and roles to become inconsistent between instances.
Prerequisites
n
The Windows version must be an earlier than Windows Server 2008. For Windows Server 2008, Windows
automatically configures the firewall to permit access.
n
There must be no network-based firewalls between vCenter Server Linked Mode instances. For
environments with network-based firewalls, see “Configuring Firewall Access by Opening Selected
Ports,” on page 37.
Procedure
1 Select Start > Run.
2 Type firewall.cpl and click OK.
3 Make sure that the firewall is set to allow exceptions.
4 Click the Exceptions tab.
5 Click Add Program.
6 Add an exception for C:\Windows\ADAM\dsamain.exe and click OK.
7 Click OK.
vSphere Basic System Administration
36 VMware, Inc.