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
2 Custom properties and groups at the component level
3 Custom properties for the business group
4 Custom properties for the compute resource
5 Custom properties for the reservation
6 Custom properties for the endpoint
7 Custom properties at the nested blueprint request level
8 Custom properties at the component request level
A runtime property takes higher precedence over other properties. A runtime property meets the following
conditions:
n
The property is marked as Prompt User, which specifies that the user must supply a value for it when
requesting a machine. This requires that the machine requestor customize individual characteristics
of each machine, or gives them the option of doing so when a default value is provided for the
property.
n
A business group manager is requesting a machine and the property appears in the custom
properties list on the Confirm Machine Request page.
Custom Property Types
You can use vRealize Automation external and updated property types for cloned machines. You cannot
use Internal and read-only property types for cloned machines.
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.
Custom Properties Reference
VMware, Inc. 10