VMware’s vCloud Automation Center 6.0 solution is made up of 3 core components:

  • vCAC VA – Delivered as a Virtual Appliance (.OVA), vCAC’s primary interface for administration and user self-service. Also includes an imbedded vCO server.
  • vCAC ID – Delivered as a Virtual Appliance (.OVA), vCAC’s stand-alone Single Sign-On engine, which provides multi-tenant LDAP and Active Directory authentication services for vCAC tenants.
  • vCAC IaaS – Windows Installable (.exe), vCAC’s IaaS engine for heterogeneous infrastructure as a service (covered in detail in Parts 3 & 4).
source: vCAC 6.0 Install and Configure [beta] documentation


Additional components to the solution (based on licensing) include the vCAC Financial Management engine (delivered as an .OVA), and the Appication Provisioning engine (also an .OVA).  Both are covered much later.

Part 2 of this series will dive into the the configuration/integration of the vCAC VA and ID/SSO VA components.

NOTE: this video guide was created using vCAC BETA builds and some of the steps will differ from the generally-available builds.  I will try to update all the videos pre-GA.

Other videos available in this series:




  1. Jonas / Brian – vCAC 6.0 has an SSO dependance that did not ship with the existing vCenter SSO (5.5) code — you will soon be able to update the vCenter SSO 5.5 service to provide compatibility with vCAC 6 — look for that update in the next week or so.

  2. Re: vCAC Identity Appliance; the manual states that you should not use an existing SSO instance, e.g. vSphere SSO from the vCenter. Now my questions would be:
    1. Why?

    2. Does it work anyway, e.g. for lab environments, if I use the same SSO Server as for vSphere?

    – Jonas

Comments are closed.