7.2
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Blueprints and Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for Openstack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vCloud Air and vCloud Director Blueprints
- Custom Properties for Networking
- Custom Properties for PXE Provisioning
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_) Table
- Custom Properties A Table
- Custom Properties B Table
- Custom Properties C Table
- Custom Properties E Table
- Custom Properties H Table
- Custom Properties I Table
- Custom Properties L Table
- Custom Properties M Table
- Custom Properties O Table
- Custom Properties P Table
- Custom Properties R Table
- Custom Properties S Table
- Custom Properties V Table
- Custom Properties X Table
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Index
Table 3‑14. Custom Properties V Table (Continued)
Property Description
VirtualMachine.SoftwareN.Name
Species the descriptive name of a software
application N or script to install or run during
provisioning. This is an optional and information-
only property. It serves no real function for the
enhanced clone workow or the guest agent but it is
useful for a custom software selection in a user
interface or for software use reporting.
VirtualMachine.SoftwareN.ScriptPath
Species 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.
You can also pass custom property values as
parameters to the script by inserting
{YourCustomProperty} in the path string. For example,
entering the
value \\vra-
scripts.mycompany.com\scripts\changeIP.bat
runs the changeIP.bat script from a shared
location, but entering the
value \\vra-
scripts.mycompany.com\scripts\changeIP.bat
{VirtualMachine.Network0.Address} runs the
changeIP script but also passes the value of the
VirtualMachine.Network0.Address property to
the script as a parameter.
Insert {Owner} to pass the machine owner name to
the script.
Chapter 3 Custom Properties Grouped by Name
VMware, Inc. 79