Troubleshooting AD Replication in Windows Azure VMs

With administrative users setup so we can actually configure various options in vRealize Automation / vCloud Automation Center – its now time to add some compute resource, so we can actually deploy things!  Endpoints in vRealize Automation / vCloud Automation Center can be several things:

• Hypervisor management platforms such as vCenter, vCenter Orchestrator, and SCVMM
• Cloud providers such as vCloud Air (formerly vCloud Hybrid Service), vCloud Director providers including vCloud Air, OpenStack using RHEV 3.1
• Physical hardware from Cisco, HP, and Dell

If you recall from the IaaS installation post, one of the options asked us to name the vCenter endpoint, now we are going to log in and configure our vCenter server as an endpoint so we can use it to deploy virtual machines through the catalog.

• Log into your vRealize Automation / vCloud Automation Center appliance (in my case as…. do you recall from the last post who to log in as?  That’s right iaasadmin as that user was assigned the infrastructure administrator role which can manage endpoints
• Once logged in, click on the infrastructure tab >> Monitoring >> Log
• Notice here the errors related to the VRM agent occurring every minute, that is because we have not added our vCenter server yet
• Click Back to infrastructure, then click on Endpoints >> Endpoints