Skip to main content

How to Build vCAC 6.2 LAB on VMware Workstation 11 – Part 3

VMware vRealize Automation 6.2 (vCAC) installation

vCAC contains 3 components: vCAC itself, vRealize Orchestrator (VCO) and IaaS server. I used native VCO to save resource. I'm going to share how to install vCAC by two sections: vCAC installation and IaaS installation.

vCAC installation

vCAC installation file is OVA. You just simply double click the file and keep default setting while importing it to VMware Workstation. I gave 6GB RAM, 2 vCPU and default disk size. DNS is

  1. You need to enter root password during first boot up. Password must matches complexity.

  2. Wait until virtual machine console shows To manage this appliance browse to https://x.x.x.x:5480/. vCAC installation completed.

IaaS installation

IaaS is based on Windows, you need a Windows Server 2008 R2 virtual machine (Please run C:windowsSystem32SysprepSysprep.exe /generalize /reboot /oobe if the machine is cloned). Make sure it's static IP address and domain member. I'll only share Windows preparation since IaaS needs vCAC is fully ready. The detail IaaS installation will be shared in another article. I gave 2GB RAM, 2 vCPU and 40GB disk. DNS is

  1. Install Java 7 runtime once server is ready. Then set System Variable: JAVA_HOME to C:Program FilesJavajre7.

  2. Then add new role Web Server (IIS).

    Keep all settings default. Add following two additional services in Role Services:

    1. Windows Authentication in Security.

    2. ASP.NET in Application Development.

  3. Open Add
    Features wizard. Add all features under Windows Process Activation Service. Add all features under .Net Framework 3.5.1 Features.

  4. Install Microsoft .Net Framework 4.5.2.

  5. Reboot server.

  6. Startup Secondary Logon service.

  7. All required system components of IaaS is installed.


Till now, we created domain/DNS server (, vCenter Server (, 3 ESXi servers (ESX01/02/, vCAC server (, IaaS server ( and FreeNAS server ( The 3 Windows servers DC01, VC01 and IaaS have static IP address. In next couple of articles I'll share how to setup and integration the components. I hope my articles can help you deploy lab quickly and easy. Do let me know if you have question. J

Serials of How to build/configure vCAC 6.2 LAB on VMware Workstation 11 (系e列文章):

How to Build vCAC 6.2 LAB on VMware Workstation 11 – Part 1
How to Build vCAC 6.2 LAB on VMware Workstation 11 – Part 2
How to Build vCAC 6.2 LAB on VMware Workstation 11 – Part 3

How to configure vCAC 6.2 LAB on VMware Workstation 11 – Part 1
How to configure vCAC 6.2 LAB on VMware Workstation 11 – Part 2
How to configure vCAC 6.2 LAB on VMware Workstation 11 – Part 3

*** Chinese Version ***

VMware vRealize Automation Center 6.2(vCAC)安装

vCAC包括3个组件:vCAC本身、vRealize Orchestrator(VCO)、IaaS服务器。为了节省我的笔记本资源,我采用vCAC自带的VCO。所以下面我将分两个部分分享如何安装vCAC套件:vCAC服务器的安装IaaS服务器的安装


vCAC的安装文件是OVA文件,只要双击此文件并保持默认选项即可导入到VMware Workstation中。此虚拟机最终我给了6GB内存、2 vCPU、磁盘默认大小,虚拟机DNS名

  1. 第一次启动vCAC时候会要求你设定root密码,需要确保密码符合复杂要求。

  2. 等待直到虚拟机控制台显示To manage this appliance browse to https://x.x.x.x:5480/ 表示vCAC安装完毕。


IaaS是基于Windows服务器的套件,首先要有一台Windows Server 2008 R2虚拟机(如果虚拟机是克隆的,必须先运行命令:C:windowsSystem32SysprepSysprep.exe /generalize /reboot /oobe)。机器要设定固定IP地址并且加域。由于IaaS的安装依赖于vCAC服务器,以下我将只分享哪些基本组建需要安装,具体的IaaS安装将在以后分享。IaaS虚拟机我给了2GB内存、2 vCPU、40GB硬盘。虚拟机的DNS名为

  1. 服务器准备就绪后,首先安装Java 7 runtime。安装完毕后,设定系统变量JAVA_HOME路径为C:Program FilesJavajre7

  2. 添加新角色Web Server(IIS)

    一路默认设定,在Role Services界面,保持默认选项,并勾选以下服务:

    1. Security 下的Windows Authentication

    2. Application Development下的ASP.NET

  3. 打开Add Features向导,添加Windows Process Activation Service下的全部功能,添加.Net Framework 3.5.1 Features下的全部功能。

  4. 安装Microsoft .Net Framework 4.5.2

  5. 重启服务器。

  6. 启动Secondary Logon服务。

  7. 至此IaaS的必备组件已经安装完毕,IaaS的安装将在以后介绍。


至此,我们创建了域控制器与DNS服务器、vCenter Server服务器、三台ESXi服务器ESX01/02/、vCAC服务器、vCAC的IaaS服务器、以及FreeNAS服务器。其中DC01、VC01、IaaS三台Windows服务器已经具备静态IP地址。在接下来的几篇文章里我会继续分享各服务器的简单配置和相互整合,我希望通过我的系列文章可以帮大家快速搭建起vCAC的试验环境。发邮件给我如果你有任何疑问。J

Popular posts from this blog

Connect-NsxtServer shows "Unable to connect to the remote server"

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install yum -y install yum -y install yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $