7.0
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Linked Clone 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 vRealize Automation Guest Agent
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for Networking
- Custom Properties for PXE Provisioning
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- 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
Table 2‑7. Custom Properties for Customizing Cloned Machines with a Guest Agent
(Continued)
Custom Property Description
VirtualMachine.Customize.WaitComplete
Set to True to prevent the provisioning workflow from sending
work items to the guest agent until all customizations have been
completed.
VirtualMachine.SoftwareN.ScriptPath
Specifies 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 file name.
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 file can then be
programmed to accept and use this value.
Custom Properties for Linux Kickstart Blueprints
vRealize Automation includes custom properties that you can use to provide additional controls for Linux
Kickstart blueprints.
Certain vRealize Automation custom properties are required to use with Linux Kickstart blueprints.
Table 2‑8. Required Custom Properties for Linux Kickstart Blueprints
Custom Property Description
VMware.VirtualCenter.OperatingSystem
Specifies the vCenter Server guest operating system version
(VirtualMachineGuestOsIdentifier) with which
vCenter Server creates the machine. This operating system
version must match the operating system version to be installed
on the provisioned machine. Administrators can create property
groups using one of several property sets, for example,
VMware[OS_Version]Properties, that are predefined to
include the correct VMware.VirtualCenter.OperatingSystem
values. This property is for virtual provisioning.
For related information, see the enumeration type
VirtualMachineGuestOsIdentifier in vSphere API/SDK
Documentation. For a list of currently accepted values, see the
vCenter Server documentation.
Image.ISO.Location
Values for this property are case sensitive. Specifies the location
of the ISO image from which to boot, for example
http://192.168.2.100/site2/winpe.iso. The format of this value
depends on your platform. For details, see documentation
provided for your platform. This property is required for WIM-
based provisioning, Linux Kickstart and autoYaST provisioning,
and SCCM-based provisioning.
Custom Properties Reference
VMware, Inc. 23