Before you can start the proof of concept setup, make sure that your environment meets the hardware and software requirements, and that you have the necessary permissions for the components included in the setup.

This proof of concept setup is customized for vCenter Server 6.0 and later. For earlier versions of vCenter Server, go to the corresponding VMware Documentation Center.

For your proof of concept setup, your system must meet specific software and hardware requirements.

Table 1. Preinstallation Checklist

Required Software and Hardware

Details

Operating System

A Windows Server 2008 R2 system or later supported Windows system with Microsoft PowerShell preinstalled. For a full list of supported operating systems, see Supported host Operating Systems for VMware vCenter Server installation.

vCenter Server

Version 6.0 or later to be installed on a Windows system. You can also install vSphere PowerCLI on a different Windows system. The Auto Deploy server is part of vCenter Server. You install vSphere PowerCLI on the same Windows system. You perform many of the setup tasks by logging in to that system, either directly into the console or by using Remote Desktop (RDP).

Storage

At least 4 GB of free space on the Windows system where vCenter Server is running. Preferably a second volume or hard drive.

Storage for ESXi datastores NFS, iSCSI, or FibreChannel, with servers and storage arrays that are configured so the servers can detect the LUNs.

  • A list of target IP addresses for NFS or iSCSI.

  • A list of target volume information for NFS or iSCSI.

Host information (for two or more hosts)

A list of target IP addresses for NFS or iSCSI.

A list of target volume information for NFS or iSCSI.

  • Default route, net mask, and primary and secondary DNS server IP addresses.

  • IP address and net mask for the VMkernel primary management network.

  • IP address and net mask for other VMkernel networks such as storage, vSphere FT, or VMware vMotion.

Auto Deploy does not overwrite existing partitions by default.

vSphere PowerCLI

vSphere PowerCLI installer binaries downloaded from the Downloads page on the VMware Web site.

ESXi software depot

The location of the ESXi software depot on the Downloads page of the VMware Web site. You use a URL to point to the image profile stored at that location, or you download a ZIP file to work with a local depot. Do not download the ESXi image.

TFTP server

TFTP installer software such as WinAgents TFTP server. The TFTP server included in Windows Server 2008 is closely tied to Windows network deployment and is not suitable.

DHCP server

The DHCP server included with Windows Server 2008 is suitable for this proof of concept setup.

You also need information about and administrator privileges to the environment's core servers including the ActiveDirectory server, DNS server, DHCP server, NTP server, and so on.

You must have complete control of the broadcast domain of the subnet in which you will deploy the setup. Ensure that no other DHCP, DNS, or TFTP server are on this subnet.