VMware VS4-ENT-PL-A Setup Guide - Page 212

vSphere Installation and Setup 3 Perform a test-and-repair compliance operation for the hosts to permanently include the vSphere HA agent on the hosts. $result = Test-DeployRuleSetCompliance Host_list Repair-DeployRuleSetCompliance -TestResult $result Auto Deploy Proof of Concept Setup A proof of concept setup of an Auto Deploy environment helps administrators to evaluate the product and demonstrate its capabilities to management. When you complete the proof of concept setup workflow, you have a working Auto Deploy environment that includes a reference host and one or more other target hosts. The proof of concept setup is intended for a test or development environment, but your completed setup can be the basis for a production environment. The set of tasks starts in an environment in which no Auto Deploy components are installed. The task descriptions assume that you are using a flat network with no VLAN tagging between the physical hosts and the rest of your environment. To perform the tasks, you should have the following background knowledge and privileges. n Experience with vSphere (vCenter Server, ESX, and ESXi). n Basic knowledge of Microsoft PowerShell and vSphere PowerCLI. n Administrator rights to the target Windows and vCenter Server systems. Follow the tasks in the order presented in this document. Some steps can be performed in a different order, but the order used here limits repeated manipulation of some components. You can set up a mixed-mode environment that includes an IPv6 vCenter Server. The Auto Deploy server must have an IPv4 address because PXE booting is supported only with IPv4. Proof of Concept Preinstallation Checklist 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 that are included in the setup. You need the following hardware and software for your proof of concept setup. n vCenter Server 5.1 or later is installed on a Windows system. In this proof of concept setup, you install the Auto Deploy server and the vSphere PowerCLI on the host on which the vCenter Server is running. You perform many of the setup tasks by logging in to that host, either directly into the console or by using Remote Desktop (RDP). n Datacenter, clusters, and folders configured on the vCenter Server system. n At least 4GB of free space on the vCenter Server system. Preferably a second volume or hard drive. n Storage for ESXi datastores (NFS, iSCSI, or FibreChannel), with servers and storage arrays that are configured so the servers can see the LUNs. n List of target IP addresses for NFS or iSCSi. n List of target volume information for NFS or iSCSI. n Two or more hosts to be provisioned with Auto Deploy, and the following information for each host. n List of MAC addresses for each physical NIC. n List of IP addresses and fully qualified host names preassigned for target ESXi installs. n Default route, netmask, and primary and secondary DNS server IP addresses. n IP address and netmask for the VMkernel primary (management) network. 212 VMware, Inc.