After publishing my recent article on how to audit vCenter Cloud Gateway and vCenter Server registrations for the vSphere+ Cloud Service, I thought it would also be useful to share some tips on how you can easily find your existing vCenter Cloud Gateway (VCGW) deployment(s) within your environment?
You might wonder, do I not already know about my VCGW deployment(s) or for that matter any other solution that is deployed within my own infrastructure? Yes, that would ideally be the case and you should also be able to look that up in your change management database (CMDB). However, over the years in speaking to many customers and hearing about some of the requests from our field teams, I have come to learn that this nirvana state does not exist for many of our customers.
In some organizations, it has been described as the wild wild west where teams of administrators with access to their vSphere environment can deploy any number of solution without ever communicating amongst each other to organizations that provide shared infrastructure access to other small teams and/or companies with a simliar set of challenges. Net net, it is certainly possible that solutions like the VCGW gateway may have been deployed or potentially even retired but have not been removed from your environment.
