When the same property exists in more than one source, a specific order is followed when applying properties to the machine.
Custom properties in a vApp blueprint override runtime properties at the vApp level. This action allows the vApp blueprint to apply a consistent behavior across all its component machines, while allowing a user to override the vApp properties for each component.
You can add custom properties to the following elements and apply them to provisioned machines.
A reservation, to apply them to all machines provisioned from that reservation
A business group, to apply them to all machines provisioned by business group members
A global or local blueprint, to apply them to all machines provisioned from the blueprint
Build profiles, which can be incorporated into any global or local blueprint, to apply them to all machines provisioned from the blueprint
A machine request, if you are a fabric administrator or business group, to apply them to that machine
The applicable approval policy, if any exist and if advanced approval support is enabled, to require approvers to provide the values to be applied to the machine being approved
The full order of precedence for custom properties is that any property value specified in a source later in the list overrides values for the same property specified in sources earlier in the list.
Build profile, specified on a vApp component blueprint
vApp component blueprint
Build profile, specified on a vApp blueprint
Runtime specified on a vApp
Runtime specified on a component machine
Any runtime property takes higher precedence and overrides a property from any source. A custom property is marked as runtime if any of the following conditions exist.
The property is marked as Prompt User, which specifies that the user must supply a value for it when requesting a machine. This condition 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 required property.
A business group manager is requesting a machine and the property appears in the custom properties list on the Properties tab of the Confirm Machine Request page.
You generally specify the characteristics of the machine to be provisioned by adding properties to blueprints and build profiles. Use custom properties in reservations and business groups carefully because they can be applied to many machines. Their use is typically limited to purposes related to their sources, such as resource management, line of business accounting, and so on.
Each blueprint can optionally incorporate one build profile and thereby inherit the custom properties in that profile. Build profiles are especially useful for applying common sets of properties for specific purposes to a wide range of blueprints. For example, your site might want to add a second disk to, customize Microsoft Remote Desktop Protocol behavior for, and enable Active Directory cleanup for a wide variety of machines. If a build profile with the necessary properties is created, it can be incorporated into all of your blueprints, local or global.
When creating and managing build profiles, a fabric administrator can load a number of predefined property sets to add several related properties all at once, instead of one by one.