Hi,
So here is my setup. I recently migrated from vSphere 5.1 u1 to vSphere 5.5 u2 by way of building a new Windows 2012 R2 server, migrating the SSL directory from ProgramData, and creating and ODBC connection to the existing SQL 2012 DB (I did an upgrade of the DB as well). This is try #2 - the first try was on a server that was named as the original, and then the old 5.1 server unjoined from the domain, this one joined etc. In the end that was scrapped because as the time I had thought it was just something messed up with the install, the server etc.
This server was a fresh manual build of Windows 2012 R2 (meaning I didn't deploy via a template etc). Same issues. The reason for upgrading this way is that I am running Citrix XenDesktop and it is a major hassle when using the MCS to allocate VM's to point to a new vSphere instance (it breaks it).
So, the install went perfect, and it was on to generating new certificates for the server, and having done this many times I tried it manual and also used the Derek Seaman vCenter 5.5 toolkit script to generate certs. Then when moving into the Cert Automation tool, running ssl-updater.bat failed with java errors at the point where it should prompt for the admin password when replacing the SSO Certificate (same deal for inventory etc). Why I cannot find a valid reason, so, I then moved on to a manual replacement.
To list the services:
ssolscli.cmd listServices https://blabla.local:7444/lookupservice/sdk
Intializing registration provider...
Getting SSL certificates for https://blabla.local:7444/lookupservice/sdk
General failure.
com.vmware.vim.sso.admin.exception.InternalError: General failure.
Return code is: OperationFailed
100
The thing is the Toolkit Script did create the sts gc and admin properties and _id files - how it acquired those numbers I have no idea though.
So I then tried to update the services - admin and gc worked! Lastly I tried sts and (note thats not my weak password but my password currently does have a . and @ in it):
ssolscli.cmd updateService -d https://blabla.local:7444/lookupservice/sdk -u administrator@vsphere.local -p My@pass.w0rd -si c:\certs\vCenterSSO\sts_id -ip c:\certs\vCenterSSO\sts.properties
Intializing registration provider...
Getting SSL certificates for https://blabla.local:7444/lookupservice/sdk
General failure.
Return code is: ServiceNotResponding
2
Note I was at least able to change the web services cert so at least Xendesktop can see the cluster, but I need to get inventory, sso etc certificates replaced and I am at the end of my rope LOL
Any idea what could cause this would be appreciated. Seeing that its the second server, one a custom windows template, and one a fresh manual setup, I doubt its anything build related. I have found no one that has had these same issues (have been searching for 2 days!)
Thanks in advance!
NOTE: tried numerous other things like disabling ipv6, adding host entries, checking firewall logs, etc and the CA and Sub CA of these certs are trusted