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
You can add properties and property groups when you create a blueprint, or later when the blueprint is in
the draft or published state. Alternatively you can add custom properties and property groups to individual
components in the blueprint.
Blueprint-level custom properties take precedence over custom properties that are configured at the
component level. You can edit blueprint-level properties by using the blueprint properties page.
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.
For information about custom property precedence, see Understanding Custom Properties Precedence.
Using Properties in Machine Provisioning
Custom properties are built-in or vRealize Automation-supplied properties. You can also create your own
properties. Properties are name-value pairs used to specify attributes of a machine or to override default
specifications.
You can use custom properties to control different 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 specifications, such as adding multiple disk drives.
n
Customize the guest OS for a machine, for instance, by including specified users in selected local
groups.
n
Specify network and security settings.
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 specified in a blueprint overrides the same property specified in a property group. This enables
a blueprint to use most of the properties in a property group while differing 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 settings in the group with UK English settings.
Custom Properties Reference
VMware, Inc. 8