There is some configuration required outside of vRealize Automation to prepare for machine provisioning. Space-Efficient Storage for Virtual ProvisioningSpace-efficient storage technology eliminates the inefficiencies of traditional storage methods by using only the storage actually required for a machine's operations. Typically, this is only a fraction of the storage actually allocated to machines. vRealize Automation supports two methods of provisioning with space-efficient technology, thin provisioning and FlexClone provisioning. Preparing Your SCVMM EnvironmentBefore you begin creating SCVMM templates and hardware profiles for use in vRealize Automation machine provisioning, you must understand the naming restrictions on template and hardware profile names, and configure SCVMM network and storage settings. 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 virtual machines. Checklist for Virtual Provisioning by Cloning PreparationWith vRealize Automation, you can clone both Windows and Linux machines. Some preparation outside of vRealize Automation is required to create the template and the customization objects used to clone machines. Choosing Your Linux Kickstart Provisioning Preparation MethodYou can automate a Linux installation on newly provisioned machines. The procedures for preparing for this type of provisioning differ depending on whether you are using Solaris AI or Kickstart or autoYaST configuration files to perform your machine provisioning. 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.