There is some configuration required outside of vRealize Automation to prepare for machine provisioning. Enabling Visual Basic Scripts in ProvisioningVisual 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. Choosing a Provisioning ScenarioThere are several methods you can use with vRealize Automation to provision physical machines. Preparing for PXE ProvisioningPrepare to provision a machine by querying a PXE boot server for a network boot strap program (NBP). You can configure the NBP to then download and execute any boot image-based provisioning method to deploy an operating system. Preparing for Linux Kickstart ProvisioningLinux Kickstart provisioning uses a configuration file to automate a Linux installation on a newly provisioned machine. To prepare for provisioning you must create a bootable ISO image and a kickstart or autoYaST configuration file. Preparing for SCCM ProvisioningvRealize Automation boots a newly provisioned machine from an ISO image, and then passes control to the specified SCCM task sequence. Preparing for WIM ProvisioningProvision a machine by booting into a WinPE environment and then install an operating system using a Windows Imaging File Format (WIM) image of an existing Windows reference machine.