Before installing vCenter Server, review the prerequisites.

Verify that you have a separate 64-bit physical server on which to install vCenter Server 5.0. You can also install ESXi 5.0 on that system and deploy vCenter Server in a virtual machine within the host. vCenter Server 5.0 cannot run as a virtual machine on an ESXi host that runs a vSphere Storage Appliance.

Verify that the physical server or virtual machine meets the hardware requirements for vCenter Server. For more information about the vCenter Server requirements, see Hardware Requirements for vCenter Server in a VSA Cluster.

Verify that you have vSphere Storage Appliance 1.0 installation DVD, or download the vCenter Server 5.0 installer from the VMware product page http://www.vmware.com/products/.

Verify that the fully qualified domain name (FQDN) of the system where you will install vCenter Server is resolvable. To check that the FQDN is resolvable, type nslookup your_vCenter_Server_fqdn at a command line prompt. If the FQDN is resolvable, the nslookup command returns the IP and name of the domain controller machine.

Verify that the host name of the machine that you are installing vCenter Server on complies with RFC 952 guidelines.

Verify that DNS reverse lookup returns a fully qualified domain name when queried with the IP address of the vCenter Server. When you install vCenter Server, the installation of the web server component that supports the vSphere Client fails if the installer cannot look up the fully qualified domain name of the vCenter Server from its IP address. Reverse lookup is implemented using PTR records. To create a PTR record, see the documentation for your vCenter Server host operating system.

Verify that no Network Address Translation (NAT) exists between the vCenter Server system and the hosts it will manage.

For small-scale deployments, VMware recommends installing the bundled SQL Server 2008 R2 Express database on one of the supported operating systems.

If the system that you use for your vCenter Server installation belongs to a workgroup rather than a domain, not all functionality is available to vCenter Server. If assigned to a workgroup, the vCenter Server system is not able to discover all domains and systems available on the network when using some features. To determine whether the system belongs to a workgroup or a domain, right-click My Computer. Click Properties and click the Computer Name tab. The Computer Name tab displays either a Workgroup label or a Domain label.

During the installation, verify that the connection between the machine and the domain controller is working.

Verify that the computer name is no more than 15 characters.

The NETWORK SERVICE account is required on the folder in which vCenter Server is installed and on the HKLM registry.

Verify that the DNS name of the machine matches the actual computer name.

Make sure the system on which you are installing vCenter Server is not an Active Directory domain controller.

On each system that is running vCenter Server, make sure that the domain user account has the following permissions:

Member of the Administrators group

Act as part of the operating system

Log on as a service

Install vCenter Server, like any other network server, on a machine with a fixed IP address and well-known DNS name, so that clients can reliably access the service. Assign a static IP address and host name to the Windows server that will host the vCenter Server system. This IP address must have a valid (internal) domain name system (DNS) registration. Ensure that the ESXi host management interface has a valid DNS resolution from the vCenter Server and all vSphere Clients. Ensure that the vCenter Server has a valid DNS resolution from all ESXi hosts and all vSphere Clients. If you use DHCP instead of a static IP address for vCenter Server, make sure that the vCenter Server computer name is updated in the domain name service (DNS). Ping the computer name to test this connection. For example, if the computer name is host-1.company.com, run the following command in the Windows command prompt:

ping host-1.company.com

If you can ping the computer name, the name is updated in DNS.