You can add certain custom properties to a vCloud Air or vCloud Director machine component definition in a blueprint.
For machine components that do not have a Network or Security tab, you can add network and security custom properties, such as VirtualMachine.Network0.Name, to their Properties tab in the design canvas. NSX network, security, and load balancer properties are only applicable to vSphere machines.
| Custom Property | Description |
|---|---|
| Sysprep.Identification.DomainAdmin | Specifies a user name with administrator-level access to the target domain in Active Directory. Do not include the user domain in the credentials that you send to vCloud Director or vCloud Air. |
| Sysprep.Identification.DomainAdminPassword | Specifies the password to associate with the Sysprep.Identification.DomainAdmin property. |
| Sysprep.Identification.JoinDomain | Specifies the name of the domain to join in Active Directory. |
| VirtualMachine.DiskN.IsFixed |
Disables the editing of a specific disk when reconfiguring a machine. Set to True to disable display of the edit capacity option for a specific volume. The True value is case-sensitive. The N value is the 0-based index of the disk. Alternatively, you can set the VirtualMachine.DiskN.IsFixed custom property to True in the VirtualMachineProperties table in the database or use the Repository API to specify a URI value such as .../Repository/Data/ManagementModelEntities.svc/VirtualMachines(guid'60D93A8A-F541-4CE0-A6C6-78973AC0F1D2')/VirtualMachineProperties. |
| VirtualMachine.DiskN.StorageReservationPolicy |
Specifies the storage reservation policy to use to find storage for disk N. Also assigns the named storage reservation policy to a volume. To use this property, substitute the volume number for N in the property name and specify a storage reservation policy name as the value. This property is equivalent to the storage reservation policy name specified on the blueprint. Disk numbering must be sequential. This property is valid for all Virtual and vCloud reservations. This property is not valid for Physical, Amazon, or OpenStack reservations. |
| VirtualMachine.EULA.AcceptAll |
Set to true to specify that all the EULAs for the VM templates of the vCloud Air or vCloud Director endpoints are accepted during provisioning. |
| VirtualMachine.NetworkN.Name |
Specifies the name of the network to connect to, for example the network device N to which a machine is attached. This is equivalent to a network interface card (NIC). By default, a network is assigned from the network paths available on the reservation on which the machine is provisioned. Also see VirtualMachine.NetworkN.AddressType. You can ensure that a network device is connected to a specific network by setting the value of this property to the name of a network on an available reservation. For example, if you give properties for N= 0 and 1, you get 2 NICs and their assigned value, provided the network is selected in the associated reservation. VirtualMachine.NetworkN custom properties are specific to 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 specific reservation, do not use this property on a reservation. You can add this property to a vCloud Air or vCloud Director machine component in a blueprint. This property is not supported for on-demand NAT or on-demand routed networks. For related information, see Custom Properties for Networking. |
| VirtualMachine.NetworkN.AddressType |
Specifies how IP address allocation is supplied to the network provider, where Network
N is the network number, starting with 0. The following values are available:
This property is available for configuring vCloud Air, vCloud Director, and vSphere machine components in the blueprint. Also see VirtualMachine.NetworkN.Name. This property is not supported for on-demand NAT or on-demand routed networks. |
| VirtualMachine.Reconfigure.DisableHotCpu |
Set to true to specify that the reconfigure machine action restarts the specified machine. By default, the reconfigure machine action does not restart the machine. Performing a hot add of CPU, memory, or storage causes the reconfigure machine action to fail and not to restart the machine unless the Hot Add setting is enabled in vSphere for the machine or template. You can add VirtualMachine.Reconfigure.DisableHotCpu=true to a machine component in a vRealize Automation blueprint to disable the Hot Add setting and force the machine to restart regardless of the vSphere Hot Add setting. The custom property is only available for machine types that support hardware reconfiguration, which are vSphere, vCloud Air, and vCloud Director. |
| VCloud.Lease.Sync.TimeBufferMins | Specifies a threshold integer value for a compute resource such that lease synchronization between vCloud Director and vRealize Automation only occur for vCloud Director or vCloud Air-provisioned machines that are set to expire in vCloud Director or vCloud Air in that time period. If a conflict is found, the lease value is synchronized to match the lease length defined in vRealize Automation. The default VCloud.Lease.Sync.TimeBufferMins value is 720 minutes, which is 12 hours. If VCloud.Lease.Sync.TimeBufferMins is not present, the default value is used. For example, if the default values are used, vRealize Automation runs the lease synchronization check workflow every 45 minutes, which is the workflow default, and only the leases of machines that are set to expire within 12 hours are changed to match the lease length defined in vRealize Automation. |
| VCloud.Owner.UseEndpointAccount | Set to true to assign the endpoint account as the vCloud Air or vCloud Director machine owner for provisioning and import operations. For change ownership operations, the owner is not changed on the endpoint. If not specified or set to false, the vRealize Automation owner is the machine owner. |
| VCloud.Template.MakeIdenticalCopy | Set to true to clone an identical copy of the vCloud Air or vCloud Director template for machine provisioning. The machine is provisioned as an identical copy of the template. Settings specified in the template, including storage path, supersede settings specified in the blueprint. The only changes from the template are the names of the cloned machines, which are generated from the machine prefix specified in the blueprint. vCloud Air or vCloud Director machines that are provisioned as identical copies can use networks and storage profiles that are not available in the vRealize Automation reservation. To avoid having unaccounted reservation allocations, verify that the storage profile or network specified in the template is available in the reservation. |
| VMware.SCSI.Sharing | Specifies the sharing mode of the machine’s VMware SCSI bus. Possible values are based on the VirtualSCSISharing ENUM value and include noSharing, physicalSharing, and virtualSharing. The VMware.SCSI.Sharing property is not available for use with the CloneWorkflow provisioning workflow. If you specify the CloneWorkflow provisioning workflow when configuring your machine component in the blueprint design canvas, you cannot use the VMware.SCSI.Sharing property. |
| VMware.SCSI.Type |
For
vCloud Air,
vCloud Director, or
vSphere machine components in blueprints, specifies the SCSI machine type using one of the following case-sensitive values:
The VMware.SCSI.Type property is not available for use with the CloneWorkflow provisioning workflow. If you specify the CloneWorkflow provisioning workflow when configuring your machine component in the blueprint design canvas, you cannot use the VMware.SCSI.Type property. |
