6.2
Table Of Contents
- IaaS Configuration for Physical Machines
- Contents
- IaaS Configuration for Physical Platforms
- Configuring IaaS
- Optional Configurations
- Preparing for Provisioning
- Enabling Visual Basic Scripts in Provisioning
- Choosing a Provisioning Scenario
- Preparing for PXE Provisioning
- Preparing for Linux Kickstart Provisioning
- Preparing for SCCM Provisioning
- Preparing for WIM Provisioning
- Creating Blueprints
- Configuring Advanced Blueprint Settings
- Managing Infrastructure
- Monitoring Workflows and Viewing Logs
6 Endpoint
7 Runtime
For vApps, the order is similar, as shown in the following list:
1 Build profile, specified on a vApp component blueprint
2 vApp component blueprint
3 Build profile, specified on a vApp blueprint
4 vApp blueprint
5 Business group
6 Compute resources
7 Reservations
8 Endpoint
9 Runtime specified on a vApp
10 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 the following conditions exist:
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
required property.
n
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.
Custom properties in reservations and business groups may be applied to many machines so they should
be used carefully. Their use is typically limited to purposes related to their sources, such as resource
management, line of business accounting, and so on. Specifying the characteristics of the machine to be
provisioned is generally done by adding properties to blueprints and build profiles.
Each blueprint of any type can optionally incorporate one or more build profiles and thereby inherit the
custom properties in those profiles. 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.
IaaS Configuration for Physical Machines
VMware, Inc. 10