So it is time to create the first vCenter endpoint. There are a couple of prerequisites to this.
1: an account with administrator privileges in vCenter. Could be a service account in AD.
2: Know the name of the vCenter agent you used during the install. (vCenter by default). If you use the spreadsheet I have mentioned before and noted it there, it is listed under “Endpoint name for the vSphere Agent:
3: You will need an agent for each vCenter that you add. I will cover this in a separate post though for now.
It is worth noting when adding a second endpoint you need to install an agent on Windows and then configure this. You can see more about this here if this is what is needed.
To create the vCenter, log on as an IaaS administrator to your sub tenant (If you followed along, then the vraadmin account should do).
Go to Infrastructure –> Endpoints –> Endpoints (again).
Click on the green plus (New)
Then select Virtual –> vSphere (vCenter)
Enter a name for the vCenter, this should be the default (vCenter). If you do not put the same name as you used during the installation then it will not work.
Put a description if you want and then add the address of the vCenter with the /sdk extension.
Finally add the account you created before we started and the password.
Press test to check if the connection works. You should see a Success message for a moment on top if all is good.
Press OK to finish.
That is pretty much it. You should now have one end point.
On a site note I learned something else here, if you only put the name you want on one part and not the second part, you need to use the default name still.
You can see here that I renamed the agent to site1mgmt but if you do not rename the endpoint also, you still get to use the default name, vCenter.
It is not so clear here but I put the Agent name as site1mgmt after taking the pic but did for whatever reason not change the endpoint name.
