I’ve been privileged to be a part of the vCAC Beta Program, and as such I’ve seen a lot of “installation issues”. There have been a few valid bugs, but the vast majority of people have simply failed to RTFM and decided to just have a go – after all, how hard can it be?

Here are some of the more common issues that have come up, in some semblance of the installation order.

1. Help! I can’t register the vCAC VA against the SSO VA!

Check your DNS.

Check your NTP.

Check your SSL certs match your hostnames.

Now go back and check NTP again.

1. Help! I can’t add my AD environment as an Identity Source!

Check that DNS is correctly configured.

1. Help! When I look at the vCAC VAMI Services list, STS isn’t Registered!

This will never show as registered, and is not the cause of any of the problems that you are having.

1. Help! The pre-requisite checker keeps failing me!

You haven’t followed the instructions. Maybe you should download this script to take care of it for you.

1. Help! My IaaS installer is failing!

This is likely because you are not using the right version of the .Net Framework. Download the correct version care of the VAMI (4.5) and remove the one that you’ve installed (probably 4.5.1). You may also be running on Windows Server 2012 R2 which is not a supported OS (as it ships with 4.5.1).

1. Help! My vCenter Endpoint isn’t collecting any information and I’m getting HTTP Unauthorised errors in my logs!

Check that your vCAC Services have all started on the IaaS Server.

1. Help! I’m getting URI errors when I try to connect to a vCenter Endpoint

Make sure you are using “https://fqdn.of.your.vc/sdk”

1. Help! My Compute Resources aren’t showing up anywhere!

You need go create a Fabric Group, and assign the Compute Resources to said Fabric Group for management.

If you have any other issues, shout out and I’ll add them to the list.

 

• Home