vCenter Server Installation
vCenter Server 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.
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 nslookupyour_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:
If you can ping the computer name, the name is updated in DNS.
Install vCenter Server
vCenter Server allows you to centrally manage hosts from either a physical or virtual Windows machine, and enables the management of a VSA cluster as well as the use of advanced features such as vSphere High Availability (HA), vSphere vMotion, and vSphere Storage vMotion.
A vCenter Server instance can manage only one instance of a VSA cluster.
See vCenter Server Prerequisites.
vCenter Server requires the Microsoft .NET 3.5 SP1 Framework. If your system does not have it installed, the vCenter Server installer installs it. The .NET 3.5 SP1 installation might require Internet connectivity to download more files.
1 In the software installer directory, double-click the autorun.exe file to start the installer.
2 Select vCenter Server™.
3 Follow the prompts in the installation wizard to choose the installer language, agree to the end user patent and license agreements, enter your user name, organization name, and license key.
If you omit the license key, vCenter Server will be in evaluation mode, which allows you to use the full feature set for a 60-day evaluation period. After installation, you can enter the license key to convert vCenter Server to licensed mode.
4 Click Install SQL Server 2008 Express instance (for small-scale deployments).
This database is suitable for small deployments of up to 5 hosts and 50 virtual machines.
5 Select Use SYSTEM Account and click Next.
The Fully Qualified Domain Name field displays the FQDN of the system that you are installing vCenter Server on. The vCenter Server installer checks that the FQDN is resolvable. If not, a warning message is displayed when you click Next. Change the entry to a resolvable FQDN. You must enter the FQDN, not the IP address.
6 Accept the default destination folders and click Next.
7 Select Create a standalone VMware vCenter Server instance and click Next.
8 For each component that you install, accept the default port numbers and click Next.
Note: Do not change the default vCenter Server ports, as it might lead to VSA upgrade failures.
Select the size of your vCenter Server inventory to allocate memory for several Java services that are used by vCenter Server.
This setting determines the maximum JVM heap settings for VMware VirtualCenter Management Webservices (Tomcat), Inventory Service, and Profile-Driven Storage Service. You can adjust this setting after installation if the number of hosts in your environment changes. See the recommendations in the vCenter Server Hardware Requirements topic in System Requirements.
Installation might take several minutes. Multiple progress bars appear during the installation of the selected components and finish installation.