vRealize Automation 6.2 Installation

Installing vRealize Automation 6.2 (previously known as vCAC)

What will you need?

1. vRealize Automation Appliance from www.vmware.com
2. Windows server 2008 R2 64-bit machine.
3. SQL server
4. Identity appliance from www.vmware.com

Where to start?

1. You will need an Esxi host for deploying vRealize Automation Appliance. Import the    .ovf template file and deploy the virtual machine,
2. Similarly deploy identity appliance using Identity Appliance .ovf template file.
3. Create a virtual machine with Windows Server 2008R2 64-bit Operating System.
4. You can install the SQL server on the same machine deployed in step 3 or on a separate windows machine.

Configuration of vRealize Automation Appliance!

1. Launch a browser (preferably Firefox) and browse to https://FQDN/IP(of vRealize automation appliance):5480 (VAMI [Virtual Appliance Management Interface])
2. Login with username root and the password you specified.
3. Click Admin and configure time settings (preferably use time server, active directory by default is a time server, you can use that.)
4. Click vRA settings Tab, and click host settings.
5. Provide host name. Make sure you have an entry in the DNS so that name resolution is possible.
6. In SSL settings, make sure "Common Name" matches the FQDN of the vRealize Automation Appliance, else there will communication issues as the host name will not match the name on the certificate (in case generating a new certificate).
7. You can optionally upload a certificate which you may have already bought for your vRA server.
8. Click save settings and wait for the message that confirms successful operation.
9. Click on the SSO tab.
10. Provide the FQDN of the identity appliance (make sure that you have configured Identity Appliance by logging into its VAMI at port 5480) or vCenter server (only in case you are planning to use the SSO of vCenter server 5.5 or above). Verify the status: it must show connected.
11. In default tenant, make sure vsphere.local is populated. The username will be administrator@vphere.local and the password you specified.
12. Next task would be licensing. Provide the license (License may have 3 editions: Standard, Advanced or Enterprise)
13. Click on Database Tab and verify that status shows connected.
14. This completes configuration of the vRA appliance.

Pre-requisites for IAAS installation!

1. Assuming that Windows Server 2008R2 64-bit machine is ready, let's configure the server before we can start the installation of IAAS components.
2. Copy the script from HERE, from line 1 through line 535, paste the script in a notepad file, Make sure you change the extension to .ps1 to make it PowerShell executable.
3. Before you start the script, it would be a good idea to download, .NET framework 4.5.2, NTRights.exe and Jre1.7 or later in 64-bit.
4. Run PowerShell as administrator on the IAAS server, and check if it is allowed to run script.
    Type: Get-ExecutionPolicy 
    If it shows restricted, change it to unrestricted by typing the following command
    Set-ExecutionPolicy unrestricted.
5. Run the script now on the same powershell prompt and follow the script instructions.

IAAS components installation!

1. Once the above script completes, navigate to VAMI of the vRA appliance, click on vRA settings Tab and click on IaaS Installer Tab.
2. Click Download Installer. Save the installer and make sure you do not change the name of the installer.
3. Run the installer as administrator.
4. Accept the EULA.
5. On the Appliance Login Information Screen, provide the username and the password for vRA appliance and accept the certificate.
6. Choose complete installation.
7. Run pre-requisite checker, make sure all the pre-requisites are met and the next button is highlighted to click.
8. Click next.
9. On Server Installation Information Screen provide the username and password for a user account which has installation permissions.
10. In the Microsoft SQL Server Database Installation Information, provide the name of the server where the database has been installed (in case of default instance, you do not require to provide the name of the instance however in case of named instance you need to). Provide the name of the database which will be created to store IAAS information.
11. Check the DEM worker and DEM orchestrator name.
12. Check if you need to install vSphere Agent right away, or you can also come back later and install.
13.On Component Registry Screen provide vRealize Automation server FQDN, click load to load the default tenant and download the certificate.
14. Click accept certificate. 
15. Provide SSO username (administrator@vsphere.local) and it's password.
16. Provide IaaS server FQDN and test both SSO and IaaS server connection.
17. Once the connection status shows pass. Click next and install to install the components.

Verify!

1. Once the installation completes, navigate to the location https://fqdn/ip(of vRA)/vcac and login with administrator@vsphere.local.
2. In case you are able to login successfully and you see the default tenant vsphere.local, you have done it right.

Comments

Post a Comment

Popular posts from this blog

NSX-T MP Node Liagent service has stopped

  What is liagent in NSX-T and other VMware appliances? Recently I found vRealize Network Insight sending alerts saying " NSX-T MP Node Liagent service has stopped ". Digging over the internet did not take me anywhere so I started on my own. Liagent mysteriously sounds like Li-agent "Li = Log Insight". Taking this assumption I looked at the NSX-T content pack configuration options in vRealize Log Insight and voila I found the answer and here is what I found. We can set up logging in NSX-T to send logs to vRealize Log Insight in 1 of the 2 ways. Here are the commands you can use, make sure you ssh using admin a. Using rsyslog: set logging-server <rsyslog-server IP/FQDB> proto udp/tls level info (chose from UDP and TLS) b. Using liagent: set logging-server <vRLi server IP/FQDN> proto li/li-tls level info (chose from Log Insight unencrypted "li" or encrypted "li-TLS') In the commands used above the proto parameter li or udp makes all ...
Read more

Error 401: Unauthorized: Access is denied due to invalid credentials. You do not have permissions to view this directory or page using the credentials that you supplied.

Image
Resolution:  Perform the following steps on IAAS server: 1. Run command prompt as administrator 2. Navigate to the following directory: ‘C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe’ Run the following command to update the vRA certificate for the IAAS server: ‘vcac-config.exe UpdateServerCertificates -d vCAC -s servername’ Where ‘vCAC’ is the name of the vCAC database (vCAC by default), and servername is the name of the SQL database hosting the vCAC database. e.g: ‘vcac-config.exe UpdateServerCertificates -d vCAC -s sqlserver.mylab.local’ 3. From the command prompt, type: IISReset
Read more

Error : You must have a role in at least one Business Group (vRealize Automation)

Image
Error: You must have a role in at least one Business Group. You get the above error when you try to reclaim machines in your environment. Resolution: 1. Login with tenant administrator. 2. Go to Business Group. 3. Click Edit on any of the business groups listed. 4. Add the tenant administrator to the "Group Manager" Role. 5. Try the activity to reclaim machines. Please don't forget to leave a comment as it helps me to know if the resolution works for all!
Read more