7.1
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Blueprints and Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for Openstack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow 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 Networking
- Custom Properties for PXE Provisioning
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_) Table
- 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
- Using Property Definitions
- Using Property Groups
- Index
By default, a machine has one network device congured with the VirtualMachine.Network0.Name property.
You can congure additional network devices by using the VirtualMachine.NetworkN.Name custom property,
where N is the network number.
N Network-specic custom properties that point to on-demand networks not supported. For example,
you cannot use network custom properties, such as VirtualMachine.Network0.NetworkProfileName, for on-
demand NAT and on-demand routed network components.
The numbering of network properties must be sequential, starting with 0. For example, if you specify
custom properties for only VirtualMachine.Network0 and VirtualMachine.Network2, the properties for
VirtualMachine.Network2 are ignored, because the preceding network, VirtualMachine.Network1, was not
specied.
Table 2‑18. Custom Properties for Networking Configuration
Custom Property Description
VirtualMachine.NetworkN.Address
Species the IP address of network device N in a machine
provisioned with a static IP address.
For Amazon, see Amazon.elasticIpAddress.ipAddress.
VirtualMachine.NetworkN.MacAddressType
Indicates whether the MAC address of network device N is
generated or user-dened (static). This property is available
for cloning.
The default value is generated. If the value is static, you
must also use VirtualMachine.NetworkN.MacAddress to
specify the MAC address.
VirtualMachine.NetworkN custom properties are
specic to individual blueprints and machines. When a
machine is requested, network and IP address allocation is
performed before the machine is assigned to a reservation.
Because blueprints are not guaranteed to be allocated to a
specic reservation, do not use this property on a
reservation.
VirtualMachine.NetworkN.MacAddress
Species the MAC address of a network device N. This
property is available for cloning.
If the value of
VirtualMachine.NetworkN.MacAddressType is
generated, this property contains the generated address.
If the value of
VirtualMachine.NetworkN.MacAddressType is static,
this property species the MAC address. For virtual
machines provisioned on ESX server hosts, the address
must be in the range specied by VMware. For details, see
vSphere documentation.
VirtualMachine.NetworkN custom properties are
specic to individual blueprints and machines. When a
machine is requested, network and IP address allocation is
performed before the machine is assigned to a reservation.
Because blueprints are not guaranteed to be allocated to a
specic reservation, do not use this property on a
reservation.
Custom Properties Reference
36 VMware, Inc.