7.3
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Custom Properties and the Property Dictionary
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for 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 and Property Groups for Containers
- 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 (_)
- Custom Properties A
- Custom Properties B
- Custom Properties C
- Custom Properties E
- Custom Properties H
- Custom Properties I
- Custom Properties L
- Custom Properties M
- Custom Properties N
- Custom Properties O
- Custom Properties P
- Custom Properties R
- Custom Properties S
- Custom Properties V
- Custom Properties X
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Defining Component Profile Settings
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 1‑20. Custom Properties for Calling PowerShell Scripts
Custom Property Description
Pxe.Setup.ScriptName
Specifies 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
Specifies 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.
Table 1‑21. Custom Properties for PXE and SCCM Provisioning
Custom Property Description
SCCM.Collection.Name
Specifies the name of the SCCM collection that contains the
operating system deployment task sequence.
SCCM.Server.Name
Specifies the fully qualified domain name of the SCCM server on
which the collection resides, for example lab-sccm.lab.local.
SCCM.Server.SiteCode
Specifies the site code of the SCCM server.
SCCM.Server.UserName
Specifies a user name with administrator-level access to the
SCCM server.
SCCM.Server.Password
Specifies the password associated with the
SCCM.Server.UserName property.
SCCM.CustomVariable.
Specifies the value of a custom variable, where Name is the
name of any custom variable to be made available to the SCCM
task sequence after the provisioned machine is registered with
the SCCM collection. The value is determined by your choice of
custom variable. If your integration requires it, you can use
SCCM.RemoveCustomVariablePrefix to remove the
SCCM.CustomVariable. prefix from your custom variable.
Custom Properties Reference
VMware, Inc. 48