6.3

QuickStart Guide
22 VMware, Inc.
After installation you rename the Secondary server to “vCSHB-Secondary” and then rename the Primary
server to “vCSHB-Primary”. You then use the Configure Server Wizard and identify the Service Name as
“vCenterServer” thereby allowing access to vCenter Server on either the Primary or Secondary servers.
To rename the Secondary server
1 Navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Manual,
Stopped, and close the dialog.
2 Right-click the Secondary server image and select Edit Settings.
3 Disable the virtual network adapters for both the VMware Channel and Principal (Public) NICs.
4 Open Network Connections, right-click the Principal (Public) network connection and select Properties.
Select Internet Protocol (TCP/IP) and click Properties.
5 Change the IP address to the match that of the Secondary management IP address previously entered in
the Configure Server wizard. Click OK twice to close the dialogs.
6 Navigate to the server’s System Properties, select the Computer Name tab, and click Change to rename
the Secondary server and join a Workgroup. When requested, restart the server.
7 Right-click the Secondary server image and select Edit Settings.
8 Re-enable the virtual network adapters for both the VMware Channel and Principal (Public) NICs.
9 Navigate to the server’s System Properties, select the Computer Name tab, and click Change to join the
domain. When requested, restart the server.
To rename the Primary Server
1 Navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Manual,
Stopped, and close the dialog.
2 Navigate to the server’s System Properties, select the Computer Name tab, and click Change to rename
the Primary server. When requested, restart the server.
Post Installation
On both the Primary and Secondary servers, navigate to Start > Administrative Tools > Services and set the
Neverfail Server R2 service to Automatic, and close the dialog. See “Post Installation Configuration”
on
page 25.
vCenter Server Heartbeat Console
vCenter Server Heartbeat can be managed via the vCenter Server Heartbeat Console installed on the Primary
or Secondary server during the installation process. It can also be managed remotely on a workstation running
Microsoft Windows XP, Vista, or Windows 7 via the vCenter Server Heartbeat Console installed using vCenter
Server Heartbeat Client Tools.
Installation of Client Tools
vCenter Server Heartbeat allows installation of vCenter Server Heartbeat Client Tools for remote management
of vCenter Server Heartbeat Pair.
N
OTE If vCenter Server Heartbeat was installed in an environment where SQL Server is on a separate host
from vCenter Server, repeat the installation process for the Primary and Secondary server specifically for the
SQL Server.
NOTE When installing vCenter Server Heartbeat Client Tools on Windows XP, the following Service Pack
levels are required.
 Windows XP 32 bit SP3
 Windows XP 64 bit SP2