http://www.vstable.com/2012/04/02/vcenter-operations-5-x-vcenter-plugin-uses-ip-instead-of-dns-hostname/
However, I decided to explore the possibility of using PowerCLI to fix these registrations.
Turns out you can and the change is immediate, so you don't have restart the vCenter service.
YAY! No more cert errors! You still have to ssh into the vCOPs UI vm and update the viClientConfig.xml file, but that's easy enough.
Here is my result (specifically for vCOPs):
$BaseURL = "https://myvCOPsRegisteredDNS.Name.local" $ExtURL = "/vcops-vsphere/" Connect-VIServer my1stvCenterServer, my2ndvCenterServer Foreach ($DefaultVIServer in $global:DefaultVIServers) { $VIServerExtensionManager = Get-View -Server $DefaultVIServer ExtensionManager $vcopsext = $VIServerExtensionManager.ExtensionList | where {$_.key -match "com.vmware.vcops"} ($vcopsext.server | where {$_.url -match "viClientConfig"}).url = ($BaseURL + $ExtURL + "viClientConfig.xml") ($vcopsext.client | where {$_.url -match "vcops-ngc.zip"}).url = ($BaseURL + $ExtURL + "vcops-ngc.zip") # If you don't $null the below properties, then the objects underneath these produce errors in updating because those object properties are required. $vcopsext.ExtendedProductInfo = $null $vcopsext.solutionManagerInfo = $null $VIServerExtensionManager.UpdateExtension($vcopsext) }