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
A custom property can optionally require that the user specify a property value when they create a machine
request. Property values are typically case-sensitive.
You can add supplied custom properties and also create and add your own properties and property groups.
For information about creating properties and property groups, see Chapter 4, “Using the Property
Dictionary,” on page 87.
For information about custom property precedence, see “Understanding Custom Properties Precedence,” on
page 10.
Using Properties in Machine Provisioning
Custom properties are vRealize Automation-supplied properties. You can also dene your own properties.
Properties are name-value pairs used to specify aributes of a machine or to override default specications.
You can use custom properties to control dierent provisioning methods, types of machines, and machine
options as in the following examples:
n
Specify a particular type of guest OS.
n
Enable WIM-based provisioning, in which a Windows Imaging File Format (WIM) image of a reference
machine is used to provision new machines.
n
Customize the behavior of Remote Desktop Protocol when connecting to a machine.
n
Register a virtual machine with a XenDesktop Desktop Delivery Controller (DDC) server.
n
Customize a virtual machine’s system specications, such as adding multiple disk drives.
n
Customize the guest OS for a machine, for instance, by including specied users in selected local
groups.
n
Specify network and security seings.
When you add a property to a blueprint, reservation, or other form you can specify if the property is to be
encrypted and also if the user must be prompted to specify a value when provisioning. These options cannot
be overridden when provisioning.
A property specied in a blueprint overrides the same property specied in a property group. This enables a
blueprint to use most of the properties in a property group while diering from the property group in some
limited way. For example, a blueprint that incorporates a standard developer workstation property group
might override the US English seings in the group with UK English seings.
You can apply properties in reservations and business groups to many machines. Their use is typically
limited to purposes related to their sources, such as resource management. Specifying the characteristics of
the machine to be provisioned is generally done by adding properties to blueprints and property groups.
Understanding Custom Properties Precedence
Properly authorized users can specify custom properties for blueprints, endpoints, business groups, and
reservations. When the same property exists in more than one source, vRealize Automation follows a
specic order of precedence when applying properties to the machine.
You can add custom properties that apply to provisioned machines to the following elements:
n
A reservation, to apply the custom properties to all machines provisioned from that reservation.
n
A business group, to apply the custom properties to all machines provisioned by business group
members.
n
A blueprint, to apply the custom properties to all machines provisioned from the blueprint.
Custom Properties Reference
10 VMware, Inc.