Save time deploying vCAC by using the vCAC6-PreReq-Automation script. This article will get you up to speed on the changes with the vCAC6 installation and provide you with an automated installation script for the vCAC 6 prerequisites, allowing you to more quickly and efficiently deploy your server.
Understanding the vCAC 6 installation
VMware vCloud Automation Center 6 was released today. As many of you start to download vCAC 6 you will notice that there are a few changes in the deployment and installation of 6 over that of 5.2.
There is a Windows IAAS Server and two vApps: the Identity Server (SSO), and the vCAC appliance (the Core Product) that make up vCAC. The vApps deploy quickly while the Windows machine requires a little more configuration. Once SSO is setup on the Identity Server and the vCAC appliance has been configured, a custom setup file can be downloaded onto the Windows IAAS server from the vCAC appliance. When run, the setup creates a connection to the vCAC appliance (you must supply the username and password of the appliance) and will then allow you to run through the prerequisite checker, followed by the rest of the installation.
There are 38 total pre-reqs involved in configuring the IAAS server. The prerequisites mainly consist of:
- Server Roles
- Server Features
- Firewall Rules
- MSDTC Settings
- Batch Logon Rights
The prereq automation script
In an effort to decrease the effort and time to deploy vCAC, I am releasing the vCAC6-PreReq-Automation script (download link at the bottom of this post), which will automate 37 of the pre-reqs (the final pre-req consists of enabling TCP/IP for SQL which can be found HERE in the vCAC Installation Guide). Although the vCAC prerequisite checker cannot be run until the vApps are deployed and configured, this script can be run as soon as the Windows server has been deployed and .NET framework 4.5 has been installed.
Prerequisite checker before automation script is run:
Prerequisite checker after the automation script runs:
You will notice after when performing the vCAC setup that the database MSSQLSERVER TCP/IP Protocol has not been enabled. This is not part of the automation script and must be performed manually after MS SQL is installed on the server. You will also notice that the firewall entries will have the ‘bypass’ icon next to their title. Double-check that these settings have been enabled and click ‘Next’.
So, how does it work?
The PowerShell script has been created to run ‘out-of-the-box’ on the Windows server. There are three variables at the beginning of the script that can be edited prior to running it, however, the defaults are sufficient.
For the script to run correctly, PowerShell should be run with elevated privileges, 64-bit PowerShell should be used, and .NET Framework 4.5 or higher must be installed. The script will check these requirements and will terminate with an explanation of what is missing should one of these requirements not be fulfilled.
Running the script:
To run the script, simply open PowerShell as administrator, locate the directory of the script and select it, then hit enter.
The script will begin adding the required server roles and features.
The rest of the settings are applied once the roles and features have been added successfully.
Once the script has completed, you will see the following green-text directing you to proceed with the SQL server portion of the installation.
At this point, the IAAS server is ready to continue with the installation of the vCAC components.
*Note: This script is given as-is and may not be suitable to use in all environments
If anyone has any questions or suggestions, post your comments below.