We were a vSphere 5.0 shop for many years and enjoyed the C# client from 4.0, 4.1 and then 5.0 days. We just upgraded to 6.0 update 2 this week and while we still are primarally used to the C# client and will use it for some time to come, I am trying to get used to the web client for the new features that are only accessible in it, like SRM and VR.
I was able to click through the numours nag screens to get in via Firefox after all those certificate warnings, and even easier simply click the one or two things in Chrome or IE to get in. However how would I eliminate the certificate errors altogether? Example, right now I'm in with Chrome but the https:// in the address bar is red with a slash through it.
In most every other web based appliance or connection we have, like HP iLO, Dell iDrac etc... we usually create a CSR on that device and submit it to our internal Windows CA and get a file back to return to the appliance. Is there a way to do that with the web client? We have a "Web Server 2" certificate template that generates the sha256 certificate back, and inherently all domain devices trust it because the domain imports our Root CA.
Also we run services like vSphere replication and SRM, I wouldn't want any certificate changes affect that or even vSphere Update Manager. We have two sites HQ and DR.