Custom properties are name-value pairs used to specify attributes of a machine or to override default specifications.

Different custom properties are used for different provisioning methods, types of machines, and machine options. For example, you can use custom properties to perform the following tasks:

  • Configure a machine’s system specifications, such as adding multiple hard disk drives

  • Configure a machine’s guest operating system, for example by including specified users in selected local groups

Specify the characteristics of the machines to be provisioned by adding custom properties or build profiles to blueprints. You can make custom properties available to blueprints and business groups by placing them in build profiles.

Any property specified in a blueprint overrides the same property specified in the incorporated build profile. This enables a blueprint to use most of the properties in a profile while differing from the profile in some limited way. For example, a blueprint that incorporates a standard developer workstation profile might override the US English settings in the profile with UK English settings. On the other hand, if no appropriate profile is available, you can specify the needed properties in the blueprint itself. This arrangement ensures that the number and complexity of blueprints remain manageable.

When a new machine is requested, vRealize Automation has not yet allocated a reservation and the compute resource and endpoint are unknown. Only custom properties from a build profile, blueprint, or business group are reconciled and presented when the machine is initially requested.