7.2

Table Of Contents
Custom Properties for vRealize Automation Guest Agent
If you have installed the vRealize Automation guest agent in your templates for cloning or in your WinPE,
you can use custom properties to run custom scripts within the guest operating system of a provisioned
machine after the machine is fully deployed.
Table 222. Custom Properties for Customizing Provisioned Machines with a Guest Agent
Custom Property Description
VirtualMachine.Admin.AddOwnerToAdmins
Set to True (default) to add the machine’s owner, as
specied by the VirtualMachine.Admin.Owner property,
to the local administrators group on the machine.
This property is not available for provisioning by cloning.
VirtualMachine.Admin.AllowLogin
Set to True (default) to add the machine owner to the local
remote desktop users group, as specied by the
VirtualMachine.Admin.Owner property.
VirtualMachine.Admin.UseGuestAgent
If the guest agent is installed as a service on a template for
cloning, set to True on the machine blueprint to enable the
guest agent service on machines cloned from that template.
When the machine is started, the guest agent service is
started. Set to False to disable the guest agent. If set to
False, the enhanced clone workfow will not use the guest
agent for guest operating system tasks, reducing its
functionality to VMwareCloneWorkflow. If not specied or
set to anything other than False, the enhanced clone
workow sends work items to the guest agent.
VirtualMachine.DiskN.Active
Set to True (default) to specify that the machine's disk N is
active. Set to False to specify that the machine's disk N is
not active.
VirtualMachine.DiskN.Size
Denes the size in GB of disk N. For example, to give a size
of 150 GB to a disk G, dene the custom property
VirtualMachine.Disk0.Size and enter a value of 150.
Disk numbering must be sequential. By default a machine
has one disk referred to by VirtualMachine.Disk0.Size,
where size is specied by the storage value on the
blueprint from which the machine is provisioned. The
storage value on the blueprint user interface overwrites the
value in the VirtualMachine.Disk0.Size property. The
VirtualMachine.Disk0.Size property is not available as
a custom property because of its relationship with the
storage option on the blueprint. More disks can be added
by specifying VirtualMachine.Disk1.Size,
VirtualMachine.Disk2.Size and so on.
VirtualMachine.Admin.TotalDiskUsage always
represents the total of the .DiskN.Size properties plus the
VMware.Memory.Reservation size allocation.
VirtualMachine.DiskN.Label
Species the label for a machine’s disk N. The disk label
maximum is 32 characters. Disk numbering must be
sequential. When used with a guest agent, species the
label of a machine's disk N inside the guest operating
system.
Chapter 2 Custom Properties Grouped by Function
VMware, Inc. 43