In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In part 5 we look at adding an Identity Store to a Tenant in vCAC.
1) Generate the variables for adding an Identity Store
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In part 4 we look at the first part of creating a Tenant in vCAC.
1) Create the parent workflow
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too. In part 3 we look at installing the vCAC plugin for vCO
Navigate to the Configuration webpage, in my case https://localhost:8283/
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In part 2 we will create the AD Users, Groups and OUs to support the vCAC tenant. In this example we will create:
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In parts 1 and 2 we will look at the AD requirements for a tenant. Since most organisations will likely use AD for authentication we will create the minimum users and groups required for a vCAC tenant in a structure that lends itself to further expansion.
While using the Create a user group in an organizational unit Active Directory workflow in vCenter Orchestrator 5.5.1 I noticed an unexpected result after the group had been created in AD.
Although the group was successfully created, the SamAccountName attribute appeared to have been populated with a seemingly random string and not the name of the group as I would have expected.
Apart from being a bit inconsistent for my liking this could have potentially undesired results from applications querying AD using the SamAccountName property.
While setting up vCAC 6.0 in my home lab, I encountered the following error when trying to deploy a machine from a blueprint.
Error requesting machine. Inner Exception: Exception has been thrown by the target of an invocation. Base Exception: The partner transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D025)
I found a VMware KB article for an earlier version along similar lines which requires configuring some MSDTC settings on the SQL server holding the vCAC database.
The other day I noticed some comments on Twitter around the time taken to install VMware vCloud Automation Center 5.2
Being of curious nature I decided to check it out further and in doing so discovered this extensive installation guide from Jad El-Zein. Seeing as a lot of the pre-requisites are installing Windows Roles / Features and configuring IIS, I figured this would make a good candidate for some PowerShell work and might save you some time if you need to do this yourself.