You can follow the listed practices when you are installing IaaS VMs using vRealize Suite Lifecycle Manager.
- Windows update, if pre-configured in the templates used for a IaaS deployment, can lead to failure. Turn off the Windows update in the templates or create the template after performing recent most applicable update of the OS.
- Have unique names for the templates in a vCenter inventory. If for a given vCenter, there are templates that do not have a unique name, then it is difficult to identify the correct one from LCM installation UI.
Windows ISO Image
You can use the ISO-based deployments of IaaS for development and test environments.
- If an ISO-based IaaS deployment is used, then IaaS database VM should be pre-deployed. Deployment of database VM using ISO is not supported in vRealize Suite Lifecycle Manager 2.0.
If an existing customization specification is being used for an IaaS deployment, then ensure that all the inputs for the custom spec are consistent and correct. Also, ensure that a valid NIC configuration with subnet details is present in the customization specification details.
IaaS installation from LCM does not support use of Run Once Commands in a customization specification. Also, the process does not configure policies, firewall rules, Antivirus, or any other software pre-bundled in the VM template or ISO. As a work-around, configure the appropriate services in the template to have them functional after first start of the deployed VMs. After you validate and deploy reports successfully, you can access the console of the deployed VMs and configure the required policies in the respective VM as per requirement.