A core component of VCAC is the endpoints. Endpoints as the name implies, gives the VCAC system access to compute and management resources to be consumed. Without it, VCAC won’t work. This is a note for myself as well as my readers, when I have a senior moment
Applying the KISS principle:
1) Have you licenced both the VCAC Appliance and the IAAS server. Without a fully licensed server setup you will not be able to add any endpoints.
2) Are you using the correct account to add the endpoints, i.e. the Infrastructure Admin that you assigned when you set it up?
2) Moving on through the system, check the account you wish to use is active and the username and password combo is correct. Check this by logging into the vSphere web client with the credentials. This is a quick and simple test.
3) When setting up your Endpoint, be sure to use the correct endpoint name as setup when you ran the installer (Each endpoint has a different name depending on its type. With vCenter endpoints, this will be vCenter, unless you changed it during the install. You can check what yours is by looking by checking the services
4) On your VCAC Endpoint URL have you both used https and finished the url with /sdk. Without this it wont work!
Once you have setup the Endpoint, it will take several minutes to gather the data from the vCenter server. You can monitor the progress, and check for errors.
If everything looks ok, you should be able to see the resources when you create a reservation group.
Install SQL Express as normal. This should be easy enough!
2) Enable TCP/IP under protocols. As is shown below, select the TCP/IP protocol, right click and select Enabled.