You manage Auto Deploy with rules that you create with vSphere PowerCLI cmdlets.
Before you begin
Verify that Microsoft .NET 2.0 is installed, or install it from the Microsoft Web site following the instructions on that Web site.
Verify that Microsoft Powershell 2.0 is installed, or install it from the Microsoft website following the instructions on that Web site.
PowerShell 2.0 is preinstalled on Windows 2008 and Windows 7 systems.
About this task
This proof of concept setup installs vSphere PowerCLI on the same system as the vCenter Server system. You can also install PowerCLI on a different Windows system.
- Log in to the console of the Windows system on which vCenter Server is installed with administrator privileges, either directly by using RDP.
- Open a command prompt and type the following commands in sequence, pressing Enter after each line.
powershell Set-ExecutionPolicy RemoteSigned Exit
- Download vSphere PowerCLI from the Download page of the VMware Web site and install the vSphere PowerCLI software.
- Confirm that PowerCLI is working.
- Double-click the PowerCLI icon on the desktop to open a PowerCLI window.
- Ignore the SSL error, type Get-DeployCommand, and press Enter.
PowerCLI displays a list of cmdlets and their definitions in the PowerCLI window.
What to do next
If you do not see a list of cmdlets when you run Get-DeployCommand, check your PowerCLI version and uninstall and reinstall if necessary.
For some background information on PowerCLI, see Using Auto Deploy Cmdlets. See the vSphere PowerCLI documentation set for details.
Prepare the hosts you want to provision with Auto Deploy. See Prepare Auto Deploy Target Hosts.