When you deploy vRealize Automation, the Microsoft SQL Server is outside of the vRealize Automation application virtual network and you must reconfigure the Microsoft SQL Server.

Procedure

  1. Log in to vCenter Server by using the vSphere Client.
    1. Open a Web browser and go to https://sfo01w01vc01.sfo01.rainpole.local/ui.
    2. Log in by using the following credentials.
      Setting Value
      User name administrator@vsphere.local
      Password vsphere_admin_password
  2. Shut down the vRealize Automation components.
    1. From the Home menu, select Hosts and Clusters and expand the sfo01w01vc01.sfo01.rainpole.local tree.
    2. Right-click each of the following virtual machines, according to their shutdown order, and select Power > Shut Down Guest OS.
      Table 1. Shutdown Order

      Product

      Virtual Machine Name

      Shutdown Order

      vRealize Business for Cloud

      Total Number of VMs (2)

      1

      sfo01vrbc01

      1

      vrb01svr01

      2

      vRealize Automation

      Total Number of VMs (4)

      2

      vra01ims01a

      1

      vra01iws01a

      2

      vra01svr01a

      3

      vra01mssql01

      4

  3. Migrate the Microsoft SQL Server virtual machine to the sfo01-w01fd-vra folder and connect it to the Mgmt-xRegion01-VXLAN port group.
    1. From the Home menu, select Hosts and Clusters and expand the sfo01w01vc01.sfo01.rainpole.local tree.
    2. Right-click vra01mssql01, select Move to folder > sfo01-w01fd-vra, and click OK.
    3. Right-click vra01mssql01 and select Edit Settings.
    4. On the Edit Settings page, browse to the following network and click OK.
      Setting Value
      Network adapter 1 A distributed port group that ends with Mgmt-xRegion01-VXLAN.
    5. Right-click vra01mssql01 and select Power > Power on.
  4. Change the IP address of the vra01mssql01 virtual machine.
    1. Right click vra01mssql01 and select Open Console.
    2. Log in by using the following credentials.
      Setting Value
      User name Windows administrator user
      Password windows_administrator_password
    3. From the Windows Start Menu, select Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings.
    4. Right-click the Ethernet adapter and select Properties.
    5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
    6. Enter the following settings and click OK.
      Setting Value
      IP address 192.168.11.62
      Subnet mask 255.255.255.0
      Default gateway 192.168.11.1
  5. Change the IP address in the DNS that resides in the sfo01.rainpole.local domain for the vra01mssql01 virtual machine.
    1. Use a Remote Desktop Protocol (RDP) client to login to the DNS server by opening an RDP connection to dc01rpl.rainpole.local.
    2. Log in by using the following credentials.
      Setting Value
      User name Active Directory administrator
      Password ad_admin_password
    3. Open the Windows Start menu, in the Search text box enter dnsmgmt.msc, and press Enter. 

      The DNS Manager dialog box appears.

    4. Under Forward Lookup Zones, select the rainpole.local domain and in the right pane locate vra01mssql01.
    5. Double-click the vra01mssql01 record, modify the IP Address, and click OK.
      Setting Value
      Fully qualified domain name (FQDN) vra01mssql01.rainpole.local
      IP Address 192.168.11.62
      Update associated pointer (PTR) record Selected
  6. Log in to the SQL Server virtual machine by using a Remote Desktop Protocol (RDP) client.
    1. Open an RDP connection to the vra01mssql01.rainpole.local virtual machine.
    2. Log in by using the following credentials.
      Settings Value
      User name Windows administrator user
      Password windows_administrator_password
  7. Install vRealize Log Insight Windows Agents in the vra01mssql01 virtual machine.

    From the vra01mssql01 Windows environment, log in to the vRealize Log Insight user interface.

    1. Open a Web browser and go to https://sfo01vrli01.sfo01.rainpole.local.
    2. Log in by using the following credentials.
      Setting Value
      User name admin
      Password deployment_admin_password
    3. Click the configuration drop-down menu icon Configuration Menu Icon and select Administration.
    4. Under Management, click Agents and click the Download Log Insight Agent Version link.
    5. In the Download Log Insight Agent Version dialog box, click Windows MSI (32-bit/64-bit) and save the .msi file to the vra01mssql01 virtual machine.
    6. Open a command prompt as Administrator, and navigate to the directory where you saved the .msi file.
    7. Run the following command and install the vRealize Log Insight agent with custom values.
      VMware-Log-Insight-Agent-4.7.0-build_number_192.168.31.10.msi SERVERPORT=9000 AUTOUPDATE=yes LIAGENT_SSL=no
    8. In the VMware vRealize Log Insight Agent Setup wizard, accept the license agreement and click Next.
    9. In the Host text box, enter sfo01vrli01.sfo01.rainpole.local, and click Install.
    10. Click Finish.
  8. Log in to vCenter Server by using the vSphere Client.
    1. Open a Web browser and go to https://sfo01w01vc01.sfo01.rainpole.local/ui.
    2. Log in by using the following credentials.
      Setting Value
      User name administrator@vsphere.local
      Password vsphere_admin_password
  9. Power on the remaining vRealize Automation components.
    1. From the Home menu, select Hosts and Clusters and expand the sfo01w01vc01.sfo01.rainpole.local tree.
    2. Right-click each of the following virtual machines, according to their startup order, and select Power > Power on.
      Table 2. Startup Order

      Product

      Virtual Machine Name

      Startup Order

      vRealize Automation

      Total Number of VMs (4)

      1

      vra01mssql01

      1

      vra01svr01a

      2

      vra01iws01a

      3

      vra01ims01a

      4

      vRealize Business for Cloud

      Total Number of VMs (2)

      2

      vrb01svr01

      1

      sfo01vrbc01

      2

What to do next

Test your environment to confirm the successful provisioning of virtual machines. See Test the Deployment of a Single Machine Blueprint for Consolidated SDDC.