7.2

Table 3‑14. Custom Properties V Table (Continued)
Property Description
VirtualMachine.Admin.ForceHost
Species the name of the ESX host. The property is
only honored if
VirtualMachine.Admin.HostSelectionPolicy is
set to EXACT_MATCH.
N This property is for vSphere only.
When provisioning against a vSphere cluster, you
can use the VirtualMachine.Admin.ForceHost
property to specify the host on which a machine is to
be provisioned. This property is used only if DRS is
not set to automatic for the cluster. If the cluster has
DRS enabled and is set to Automatic, vSphere
relocates the provisioned machine when the machine
is restarted.
VirtualMachine.Admin.HostSelectionPolicy
Optionally set to EXACT_MATCH to require the
machine to be placed on the host specied by the
VirtualMachine.Admin.ForceHost property. If the
host is unavailable, the request results in a failure. If
a host is not specied, the next best available host is
selected. If set to EXACT_MATCH, an error occurs if
the specied host does not have enough memory or
is in maintenance mode.
N This property applies to vSphere only.
VirtualMachine.Agent.CopyToDisk
Set to True (default) to copy the guest agent
executable le to %System-Drive%\VRM\Build\Bin
on the machine’s disk.
VirtualMachine.Agent.GuiRunOnce
Set to True to include guest agent execution in the
SysPrep.inf run once section. Set to False for the
Linux agent to stop the provisioning workow.
VirtualMachine.Agent.Reboot
Set to True (default) to specify that the guest agent
restarts the machine following installation of the
guest operating system.
VirtualMachine.CDROM.Attach
Set to False to provision the machine without a CD-
ROM device. The default is True.
VirtualMachine.CPU.Count
Species the number of CPUs, for example 2,
allocated to a machine. The default is the value
specied by the CPU seing on the blueprint.
N This custom property value is overridden by
the CPU value on the blueprint when the machine is
rst provisioned.
VirtualMachine.Customize.WaitComplete
Set to True to prevent the provisioning workow
from sending work items to the guest agent until all
customizations are complete.
VirtualMachine.Core.Count
If set to a value greater than zero, species the
number of cores per socket when provisioning the
virtual machine.
You can use this property on a blueprint to specify
cores per virtual socket or total number of sockets.
For example, your licensing terms might restrict
software that is licensed per socket or available
operating systems only recognize so many sockets
and additional CPUs must be provisioned as
additional cores.
Custom Properties Reference
72 VMware, Inc.