VMware vRealize Automation 7.6 Initial Configuration

Following up on the previous vRealize Automation (vRA) deployment blog post I need to take care of the initial configuration before I can start using the vRA virtual appliance (VA).

I don’t need any Infrastructure as a Service (IaaS) capabilities for my work so I’ll skip that which saves me a lot of time during architecture, deployment and maintenance. Now I just need to manage a single virtual appliance.

Follow the below steps to perform the initial vRA configuration.

  1. Access the newly deployed vRA virtual appliance via https://fqdn_IPaddress:5480 and login with the root credentials specified during the deployment
  2. Select Deployment – I. my case Minimal is good enough.
  3. Resovle the host name automatically works since it is added to the DNS 🙂
  4. Provide a Single Sign-On password, to be used by the administrator@vsphere.local account
  5. Certificate management – which everybody loves, right 🙂 Fairly simple for vRA though and in my case I Generate Certificate using the configuration tool. Press Save Generated Certificate
  6. Move on when the certificate is saved.
  7. Press Install and wait for quite some time. Way quicker when Minimal deployment type is selected compared to an Enterprise deployment including Infrastructure As A Service (IaaS).
  8. Sit back and have a coffey, coke or whatever you prefer.
  9. No need to collect logs, just click Next when completed.
  10. Provide a License key.
  11. Select if you wanna join the VMware Customer Experience Improvement Program or not.
  12. Click Finished and you’re all done.

As an additional verification you can access the vRA web interface and verify that the status looks good which it does in this screen even though it is a bit red 🙂

Now just access the vRA appliance via https://fqdn_IPaddress to get started.

All done.

Final piece of configuration required in vRA before I can create XaaS Blueprint will be to assign the XaaS Architect role to the user. See the VMware vRealize Automation XaaS Architect Configuration blog post for that information.