Now that we have the vCloud Automation Center / vRealize Automation appliance deployed and working, it is time to get the Infrastructure-as-a-Service components installed. The IaaS components run on Windows and need to connect a Microsoft SQL server instance. In my case I am going to use SQL express installed on the same VM I will install the IaaS components on, again we are in a lab here - typically you would have a separate database server to host the DB. As always, and a point I’ve not referenced really at all this month, always check the documentation to ensure you are installing on a supported platform. The vCloud Automation Center / vRealize Automation documentation is excellent, as is the support matrix PDF.
Since Microsoft SQL Server 2014 is supported, that is what I will use. Also, as of 6.1 you can now install the IaaS components on Windows Server 2012 R2, in 6.0 you could not use R2 because of the native .NET version that shipped with R2 (4.5.1). I am using Windows Server 2012 here because that happens to be what I have downloaded but the same steps should work fine for R2. A few prerequisite steps to take care of first:
- Log into your domain controller and create a user account for the IaaS components to run as, something like svc_vra_iaas; we will give this account administrative permission to the IaaS virtual machine and in SQL to create the database
- Create a group called iaasAdmins; we will put the user account in this group and give the group permission on the server
First step is to clone another Windows 2012 virtual machine in VMware Workstation, see Part 2 of my home lab series if you need a walk though on setting up the template or on how to do the clone. Once you have your clone, boot your virtual machine, name it accordingly and join it to your domain.
- Log in as an administrative user, we will grant access to our administrative user we created in AD to perform the rest of the tasks
- In Server manager click on Tools >> Computer Management >> Local Users and Groups >> Groups
- Right click Administrators >> Add to Group...
- Click the add button and enter iaasAdmins, log in with domain credentials (if you logged in as the local admin)
- Click OK twice and Close Computer Management
- You should now be back in the Server Manager Dashboard (if not open Server Manager) and click on Local Server
- Disable Windows Firewall and IE Enhanced Security Configuration
- Click back on Dashboard, then Add roles and features
- When the wizard starts, click Next
- Select Role-based or feature-based and click Next
- Ensure your server is selected and click Next
- On the roles page just click Next
- On the Select Features page expand .NET Framework 4.5 Features and select all options under WCF Services, when prompted add any required features
- Once all have been selected, click Next, then next 2 more times
- On the confirm installation selections page click the box to restart the destination server automatically if required (it shouldn't) and click the Install button; the installation will start
- Once finished click the close button
Okay so a little of that may have been left over from the 6.0 days, it looks like the new pre-req script from Brian Graf may handle most of that, in any case know that we could have had a lot of boxes to tick here but we can avoid that error thanks to Brian’s script. You can download the script from http://blogs.vmware.com/PowerCLI/2014/09/vcac-6-1-pre-req-automation-script-released.html. Save it to a folder on the IaaS server, I prefer c:\admin\scripts but you can put it where ever you like.
- Once the script has been downloaded and extracted, open PowerShell as an administrator (right click Run as Administrator) and run
In production you shouldn’t do that, RemoteSigned maybe then unblock the script - follow your security policies there.
- Log out of your IaaS server and log back in as the user account we created, in my case svc_vra_iaas
- Change to the directory where you downloaded and extracted the script
- Run vCAC61-PreReq-Automation.ps1
- Answer any questions the script presents specific to your environment
- Some of the steps could take a long time, so be patient while it runs (e.g. downloading and installing .NET updates)
This is a very good script, if you have any errors (text in red) check them and re-run the script, otherwise we are ready to install Microsoft SQL in our next post!