With vRealize Suite Lifecycle Manager 2.0, you can install or deploy IaaS windows of a vRealize Automation deployment without having to provision it before trying to create an environment with vRealize Automation in vRealize Suite Lifecycle Manager.

The pre-check run ensures the system requirements are met, while the Windows OS template (one or more for specific IaaS component) itself is provided by any user.

  • You can deploy IaaS components with a minimum number of steps.

  • IaaS component deployments are part of vRealize Automation deployment.

  • Pre-validations on the IaaS components should try to fix the issues wherever possible and when an issue is automatically handled you can fix from the UI.

Procedure

  1. Enter the Windows Username, and Password.
  2. Select the Applicable Time Sync mode.
  3. Select the Time Server (NTP). For more information, see Configure NTP Servers.
  4. As cloud admin you can deploy Windows VMs that are required for vRealize Automation installation, using vRSLCM installation wizard. Click Yes, and from the Configure Windows box under Product properties, select the required windows template and its associated spec.

    When you select Yes, the Window box section appears. If you select no, then vRSLCM will not deploy new Windows VMs for IaaS components.

  5. To Configure Cluster Virtual IPs, select the Yes or No options.

    If you select yes, then the load balancer is connected to the individual product and then configure the vRA Appliance, IaaS Web, and IaaS Manager manually.

  6. For deploying IaaS VMs, you can either select ISO or Template.

    When you select ISO, map a valid windows ISO image along with a correct license key in vRSLCM. For more information on ISO mapping, see ISO Mapping in vRealize Suite Lifecycle Manager.

    Note:

    When you select Template as an option for IaaS, you are asked to select a template from a pre-populated list. The templates in the list are collected from the vCenter specified at the in Infrastructure Details section. For more details on usage of templates, see Templates and Custom Specification in vCenter Server.

  7. For a customization specification, select Existing Spec or User Input. An existing spec provides an option to select a spec from the vCenter Server. For a user input, enter the fields manually. The entries for user input are not saved but will be applied for the current deployment of vRealize Automation.
  8. Enter the details required for each of the Components. For each components advanced property can be accessed to override details provided in the Windows Box section.
  9. Click Next to continue to PreCheck Details section.

    Before proceeding with precheck, see Best Practices.