6.2
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Openstack Endpoints
- 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 vApp Blueprints
- Custom Properties for vRealize Automation Guest Agent
- 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
The following vRealize Automation custom property types are available.
n
Internal
The specified value is maintained in the database only. For example, the email address of the
manager who approved a machine request is recorded in the VirtualMachine.Admin.Approver
property but the property has no effect on the machine.
n
Read-only
The specified value is implemented on the machine and cannot be changed. For example,
VirtualMachine.Admin.UUID specifies the UUID of the machine, which cannot be changed.
n
External
A machine’s external properties are determined when the virtualization platform creates the machine
or during the WinPE phase of the build process. To set these properties, their values must be
provided to the proxy agent, which passes them on to the virtualization platform, or to the guest
agent , which implements them in the WinPE phase.
The specified value is implemented on the machine but is never updated. For example, if the property
VirtualMachine.Admin.AddOwnerToAdmins is set to true, the owner of the machine is added to its
local administrators group. If the owner is later removed from this group, the property is not updated
to false.
n
Updated
The specified value is implemented on the machine and is updated through data collection. For
example, if the compute resource of a machine is changed, a proxy agent updates the value of the
machine’s VirtualMachine.Admin.Hostname property.
Internal and read-only property types set attributes that the template determines.
You can use the vRealize Automation machine menu to change all reserved custom properties except the
read-only properties VirtualMachine.Admin.AgentID, VirtualMachine.Admin.UUID, and
VirtualMachine.Admin.Name.
Creating Custom Properties for Application Services
You can use custom properties that you define on a vRealize Automation blueprint when you define an
application blueprint in Application Services.
Using vRealize Automation you can add custom properties to blueprints either individually or in a build
profile. A build profile is a named collection of a group of custom properties. If you enable the Prompt
User option for a custom property, the user is required to enter a value for the property when they use that
blueprint to request machine provisioning.
Custom properties that have been made available to a specific business group are also available to
members of that group as they create and edit blueprints.
You can use the custom properties on vRealize Automation blueprints to define applications in Application
Services and publish them to the vRealize Automation catalog.
Custom Properties Reference
VMware, Inc. 13