6.2

Table 5‑1. Custom Properties for Networking Configuration (Continued)
Custom Property Description
VCNS.SecurityGroup.Names.name Specifies the vCloud Networking and Security 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 Specifies the vCloud Networking and Security 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
Enabling Visual Basic Scripts in Provisioning
Visual Basic scripts are run outside of vRealize Automation as additional steps in the machine life cycle
and can be used to update the custom property values of machines. Visual Basic scripts can be used with
any provisioning method.
For example, you could use a script to generate certificates or security tokens before provisioning and
then use those certificates and tokens in provisioning a machine.
Note This information does not apply to Amazon Web Services.
When executing a Visual Basic script, the EPI agent passes all machine custom properties as arguments
to the script. To return updated property values to vRealize Automation, you must place these properties
in a dictionary and call a function provided by vRealize Automation.
The sample Visual Basic script PrePostProvisioningExample.vbs is included in the Scripts
subdirectory of the EPI agent installation directory. This script contains a header to load all arguments into
a dictionary, a body in which you can include your functions, and a footer to return updated custom
properties to vRealize Automation.
The following is a high-level overview of the steps required to use Visual Basic scripts in provisioning:
1 A system administrator installs and configures an EPI agent for Visual Basic scripts. See Installation
and Configuration.
IaaS Configuration for Cloud Platforms
VMware, Inc. 96