7.1

Table 2‑6. Custom Properties for Linked Clone Blueprints (Continued)
Custom Property Description
Linux.ExternalScript.Server
Species the name of the NFS server, for example lab-
ad.lab.local, on which the Linux external customization
script named in Linux.ExternalScript.Name is located.
Linux.ExternalScript.Path
Species the local path to the Linux customization script or
the export path to the Linux customization on the NFS
server. The value must begin with a forward slash and not
include the le name, for
example /scripts/linux/config.sh.
If you installed the guest agent to customize cloned machines, you use some custom properties more often
than others.
Table 2‑7. Custom Properties for Customizing Cloned Machines with a Guest Agent
Custom Property Description
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.Admin.CustomizeGuestOSDelay
Species the time to wait after customization is complete
and before starting the guest operating system
customization. The value must be in HH:MM:SS format. If
the value is not set, the default value is one minute
(00:01:00). If you choose not to include this custom
property, provisioning can fail if the virtual machine
reboots before guest agent work items are completed,
causing provisioning to fail.
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.SoftwareN.ScriptPath
Species the full path to an application's install script. The
path must be a valid absolute path as seen by the guest
operating system and must include the name of the script
lename.
You can pass custom property values as parameters to the
script by inserting {CustomPropertyName} in the path string.
For example, if you have a custom property named
ActivationKey whose value is 1234, the script path is
D:\InstallApp.bat –key {ActivationKey}. The guest
agent runs the command D:\InstallApp.bat –key
1234. Your script le can then be programmed to accept
and use this value.
Chapter 2 Custom Properties Grouped by Function
VMware, Inc. 23