Setting Up for Linux Desktops

# Get the task object
$task = Get-Task | where { $_.id -eq $task }
#Wait for the taks to Complete
Wait-Task -Task $task
$newvm = Get-vm $destVMName
$customSpec = Get-OSCustomizationSpec $cSpec
Set-vm -OSCustomizationSpec $cSpec -vm $newvm -confirm:$false
if ($disableVMConsole -eq "yes")
{
Disable_VM_Console($destVMName)
}
# Start the VM
Start-VM $newvm
}
Disconnect-VIServer $vcAddress -Confirm:$false
exit
Script Execution
The following messages are from an execution of the script:
PowerCLI C:\scripts> .\CloneVMs.ps1
Your vCenter address: 10.117.44.17
Your vCenter admin user name: administrator
Your vCenter admin user password: *******
Clone Type<"linked" or "Full"> : linked
Disable vSphere VM Console ("yes" or "no", recommend "yes") : yes
The time that the cloning process takes depends on the number of desktop machines and can range from
several minutes to a number of hours. To verify that the process is complete, from vSphere client, make
sure that the last desktop virtual machine is powered on, has its own unique host name, and VMware
Tools is running.
Sample Script to Join Cloned Virtual Machines to AD
Domain
You can customize and use the following sample script to join cloned virtual machines (VMs) to an Active
Directory (AD) domain.
You need to run this script if you use the Winbind solution for AD integration because the step to join the
domain will fail for the cloned VMs. This script runs a command to join the domain on each VM. You do
not need to run this script if you use the OpenLDAP solution.
To copy and paste the script content without page breaks, use the HTML version of this topic, available
from the Horizon 7 documentation page at https://www.vmware.com/support/pubs/view_pubs.html.
Setting Up Horizon 7 for Linux Desktops
VMware, Inc. 83