7.2
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
Table 2‑18. Custom Properties for Networking Configuration (Continued)
Custom Property Description
VCNS.SecurityGroup.Names.name
Species the NSX security group or groups to which the
virtual machine is assigned during provisioning. The value
is a security group name or a list of names separated by
commas. Names are case-sensitive.
Appending a name allows you to create multiple versions
of the property, which can be used separately or in
combination. For example, the following properties can list
security groups intended for general use, for the sales
force, and for support:
n
VCNS.SecurityGroup.Names
n
VCNS.SecurityGroup.Names.sales
n
VCNS.SecurityGroup.Names.support
VCNS.SecurityTag.Names.name
Species the NSX security tag or tags to which the virtual
machine is associated during provisioning. The value is a
security tag name or a list of names separated by commas.
Names are case-sensitive.
Appending a name allows you to create multiple versions
of the property, which can be used separately or in
combination. For example, the following properties can list
security tags intended for general use, for the sales force,
and for support:
n
VCNS.SecurityTag.Names
n
VCNS.SecurityTag.Names.sales
n
VCNS.SecurityTag.Names.support
Custom Properties for PXE Provisioning
PXE is the only provisioning method supported for Cisco UCS Manager. You can use the network bootstrap
program with vRealize Automation custom properties to initiate WIM, SCCM, or Linux Kickstart
provisioning. You can also use custom properties to call your own PowerShell scripts. Linux Kickstart
provisioning does not require custom properties.
Custom Properties for Provisioning With PowerShell Scripts
You can use these properties for calling PowerShell scripts.
Table 2‑19. Custom Properties for Calling PowerShell Scripts
Custom Property Description
Pxe.Setup.ScriptName
Species a custom EPI PowerShell script to run on the
machine before it is started by using the PXE network boot
program. The value is the name assigned to the script when
it is uploaded to the model manager, for example
setup.ps1.
Pxe.Clean.ScriptName
Species the name of an EPI PowerShell script installed in
the vRealize Automation Model Manager, to run on the
machine after it is provisioned. The value is the name
assigned to the script when it is uploaded to the Model
Manager, for example clean.ps1.
Custom Properties For PXE and SCCM Provisioning
You can use these properties for PXE and SCCM provisioning.
Custom Properties Reference
40 VMware, Inc.