7.1

Table 3‑14. Custom Properties V Table (Continued)
Property Description
n
VirtualMachine.NetworkN.SubnetMask
n
VirtualMachine.NetworkN.Gateway
n
VirtualMachine.NetworkN.PrimaryDns
n
VirtualMachine.NetworkN.SecondaryDns
n
VirtualMachine.NetworkN.PrimaryWins
n
VirtualMachine.NetworkN.SecondaryWins
n
VirtualMachine.NetworkN.DnsSuffix
n
VirtualMachine.NetworkN.DnsSearchSuffixes
Congures aributes of the network prole specied
in VirtualMachine.NetworkN.ProfileName.
VirtualMachine.NetworkN custom properties are
specic to individual blueprints and machines.
When a machine is requested, network and IP
address allocation is performed before the machine
is assigned to a reservation. Because blueprints are
not guaranteed to be allocated to a specic
reservation, do not use this property on a
reservation.
When specifying values for multiple DNS search
suxes using
VirtualMachine.NetworkN.DnsSearchSuffixes,
you can use commas to separate values for a
Windows deployment.
VirtualMachine.Rdp.File
Species the RDP le that contains seings to be
used when opening an RDP link to the machine. Can
be used together with, or as an alternative to,
VirtualMachine.Rdp.SettingN. The le must be
located in the vRealize Automation server
installation directory, for example %SystemDrive
%\Program Files
x86\VMware\vCAC\Server\Rdp\console.rdp.
You must create the Rdp directory.
VirtualMachine.Rdp.SettingN
Congures specic RDP seings. N is a unique
number used to distinguish one RDP seing from
another. For example, to specify the Authentication
Level so that no authentication requirement is
specied, dene the custom property
VirtualMachine.Rdp.Setting1 and set the value
to authentication level:i:3. Use to open an RDP link
to specify seings.
For a list of available seings and correct syntax, see
the Microsoft Windows RDP documentation.
VirtualMachine.Reconfigure.DisableHotCpu
Set to true to specify that the recongure machine
action restarts the specied machine. By default, the
recongure machine action does not restart the
machine.
Performing a hot add of CPU, memory, or storage
causes the recongure machine action to fail and not
to restart the machine unless the Hot Add seing is
enabled in vSphere for the machine or template. You
can add
VirtualMachine.Reconfigure.DisableHotCpu=t
rue to a machine component in a
vRealize Automation blueprint to disable the Hot
Add seing and force the machine to restart
regardless of the vSphere Hot Add seing. The
custom property is only available for machine types
that support hardware reconguration, which are
vSphere, vCloud Air, and vCloud Director.
VirtualMachine.Request.Layout
Species the property layout to be used in the virtual
machine request page. The value must match the
name of the layout to be used.
Chapter 3 Custom Properties Grouped by Name
VMware, Inc. 75