6.7

Table Of Contents
In this scenario, you install PowerCLI on the same system as the vCenter Server system. You can also
install PowerCLI on a different Windows system.
Prerequisites
n
Verify that Microsoft .NET Framework 4.5 or 4.5.x is installed, or install it from the Microsoft Web site.
n
Verify that Windows PowerShell 3.0 or 4.0 is installed, or install it from the Microsoft Web site.
Procedure
1 Log in with administrator privileges to the console of the Windows system on which vCenter Server is
installed, either directly or by using RDP.
2 Download PowerCLI from the Download page of the VMware Web site and install the PowerCLI
software.
3 Confirm that PowerCLI is working.
a Start a PowerCLI session.
b (Optional) If an SSL error appears, check the thumbprint and ignore the error.
c Run the Get-DeployCommand cmdlet.
PowerCLI displays a list of cmdlets and their definitions in the PowerCLI window.
4 (Optional) If Get-DeployCommand does not return the list of cmdlets, check your PowerCLI version
and uninstall and reinstall it if necessary.
What to do next
Configure the settings of your target hosts to prepare them for provisioning with vSphere Auto Deploy.
Prepare the vSphere Auto Deploy Target Hosts
You must configure the BIOS settings of the four hosts and reconfirm the MAC address of the primary
network device to prepare the target hosts for provisioning with vSphere Auto Deploy.
Prerequisites
Hosts that you want to provision with vSphere Auto Deploy must meet the requirements for ESXi.
See ESXi Hardware Requirements.
Procedure
1 Change the BIOS settings of each of the four physical hosts to force the hosts to boot from the
primary network device.
2 Reconfirm the MAC address of the primary network device.
What to do next
Set up the DHCP server to serve each target host with an iPXE binary.
VMware ESXi Installation and Setup
VMware, Inc. 174