6.3

VMware, Inc. 25
Chapter 2 vCenter Server Heartbeat Installation
Post Installation Configuration
Upon completion of installation, a series of tasks must be performed to ensure that vCenter Server Heartbeat
is properly configured.
1 Verify that the SetSPN.exe (Service Principal Names) executable is present in the Windows\System32
directory on both the Primary and Secondary servers (this is normally present as a component of the
Windows 2008 operating system).
SetSPN.exe is a Microsoft command-line tool that reads, modifies, or deletes the Service Principal Names
(SPN) directory property for an Active Directory service account and is required to be present on both
servers prior to starting vCenter Server Heartbeat for the first time.
2 Start vCenter Server Heartbeat on the Primary server. Right-click the vCenter Server Heartbeat System
Tray icon and select Start VMware vCenter Server Heartbeat. The icons change from a double dash (–/–)
to a P, indicating the server is the Primary server, and an A indicating the server is acting in an active role
(P/A).
3 Start vCenter Server Heartbeat on the Secondary server. Right-click the vCenter Server Heartbeat System
Tray icon and select Start VMware vCenter Server Heartbeat. The icon changes from a double dash (–/–)
to an S, indicating that the server is the Secondary server, and a dash (–), indicating that the server is in a
passive role (S/–).
The Primary and Secondary servers establish a handshake and commence replication.
4 Verify that Nslookup resolves as shown below:
 Nslookup resolves the Service Name to the Public IP
 Nslookup resolves the Primary Name to the Public IP
 Nslookup resolves the Secondary Name to the Secondary Passive IP
If SQL Server is to be installed on a separate host from vCenter Server, repeat the installation process for
the Primary and Secondary servers at the remote site and select SQL Server only. See go to “Primary
Server” on page 14.
Configuring VirtualCenter Plug-in with the Correct Credentials
After installation is complete, you must enter the credentials for an account with rights to the vSphere
Infrastructure.
To add the vSphere Infrastructure credentials
1 Navigate to the Applications: Plug-ins page.
2 Select the VirtualCenterNFPlugin.dll
3Click Edit.
4 Type the Username and Password for an account with rights to the vSphere Infrastructure.
5Click OK.
Configuring SQL Server Plug-in to run with the Correct Credentials
After installation, you must configure the SQL Server Plug-in with the correct credentials.
To add the SQL Server Plug-in credentials
1 Launch the vCenter Server Heartbeat Console and navigate to the Applications: Tasks page.
2Click User Accounts. Verify that the user account under which you installed vCenter Server Heartbeat is
present in the list of User Accounts. If it is present and is a member of the Domain Admins group,
Enterprise Admins group, or has been delegated Administrator rights, go to Step 6.
3In the User Accounts dialog, click Add.