7.4
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Custom Properties and the Property Dictionary
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for 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 and Security
- Custom Properties and Property Groups for Containers
- Custom Properties for PXE Provisioning
- Custom Properties for OVF Import
- 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 (_)
- Custom Properties A
- Custom Properties B
- Custom Properties C
- Custom Properties E
- Custom Properties H
- Custom Properties I
- Custom Properties L
- Custom Properties M
- Custom Properties N
- Custom Properties O
- Custom Properties P
- Custom Properties R
- Custom Properties S
- Custom Properties V
- Custom Properties X
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Defining Component Profile Settings
Table 1‑45. Custom Properties V Table
Property Description
VbScript.PreProvisioning.Name
Specifies the full path of a Visual Basic script to be run before a
machine is provisioned. For example, %System-Drive%\Program
Files(x86)\VMware\vCAC
Agents\EPI_Agent\Scripts\SendEmail.vbs. The script file must
reside on the system on which the Visual Basic script EPI agent is
installed.
VbScript.PostProvisioning.Name
Specifies the full path of a Visual Basic script to be run after a machine
is provisioned. For example, %System-Drive%\Program
Files(x86)\VMware\vCAC
Agents\EPI_Agent\Scripts\SendEmail.vbs. The script file must
reside on the system on which the Visual Basic script EPI agent is
installed.
VbScript.UnProvisioning.Name
Specifies the full path of a Visual Basic script to be run when a
machine is destroyed. For example, %System-Drive%\Program
Files (x86)\VMware\vCAC
Agents\EPI_Agent\Scripts\SendEmail.vb. The script file must
reside on the system on which the Visual Basic script EPI agent is
installed.
VCloud.Lease.Sync.TimeBufferMins
Specifies a threshold integer value for a compute resource such that
lease synchronization between vCloud Director and
vRealize Automation only occur for vCloud Director or vCloud Air-
provisioned machines that are set to expire in vCloud Director or
vCloud Air in that time period. If a conflict is found, the lease value is
synchronized to match the lease length defined in
vRealize Automation. The default
VCloud.Lease.Sync.TimeBufferMins value is 720 minutes, which is
12 hours. If VCloud.Lease.Sync.TimeBufferMins is not present, the
default value is used. For example, if the default values are used,
vRealize Automation runs the lease synchronization check workflow
every 45 minutes, which is the workflow default, and only the leases of
machines that are set to expire within 12 hours are changed to match
the lease length defined in vRealize Automation.
VCloud.Owner.UseEndpointAccount
Set to true to assign the endpoint account as the vCloud Air or
vCloud Director machine owner for provisioning and import operations.
For change ownership operations, the owner is not changed on the
endpoint. If not specified or set to false, the vRealize Automation
owner is the machine owner.
VCloud.Template.MakeIdenticalCopy
Set to true to clone an identical copy of the vCloud Air or
vCloud Director template for machine provisioning. The machine is
provisioned as an identical copy of the template. Settings specified in
the template, including storage path, supersede settings specified in
the blueprint. The only changes from the template are the names of
the cloned machines, which are generated from the machine prefix
specified in the blueprint.
vCloud Air or vCloud Director machines that are provisioned as
identical copies can use networks and storage profiles that are not
available in the vRealize Automation reservation. To avoid having
unaccounted reservation allocations, verify that the storage profile or
network specified in the template is available in the reservation.
Custom Properties Reference
VMware, Inc. 78