6.2

Table Of Contents

Preparing for Provisioning 3

There is some configuration required outside of vRealize Automation to prepare for machine provisioning.

This chapter includes the following topics:

Enabling Visual Basic Scripts in Provisioning

Choosing a Provisioning Scenario

Preparing for PXE Provisioning

Preparing for Linux Kickstart Provisioning

Preparing for SCCM Provisioning

Preparing for WIM Provisioning

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.

VMware, Inc.