After setting up those CAs in the last two posts it would be a shame to have them just sitting around. As I am quite often getting the question how to replace certificates in an environment that is leveraging SSO 5.5 with vCenter 5.1 still in place the CA will be the perfect opportunity to demonstrate the process.
@fbuechsel Can you write the same for W2K12R2? :))
— Patrick Terlisten (@PTerlisten) 27. Juli 2014
Sure I can, so let’s go. Same assumptions as in the last post, this is not intended to be secure or anything, it should just serve the purpose of being easy to setup and work out of the box while being able to create certificates with Derek Seaman’s SSL toolkit, which should also be the requirement for the VSS Labs vCert Manager, and create vSphere basic stack compliant certificates.
Derek Seaman has done a great job describing on how to create a template for VMware View on 2008 and how to set up an intermediate CA structure in Windows Server 2012R2.
I tried going through the latter and found the procedure pretty elaborate for my own lab purposes so I thought about setting up a CA that still will work with his SSL toolkit but would be set up in about 10 minutes.
Chris Wahl had an interesting issue a couple of days ago on twitter.
Easy way to make the vSphere Web Client 100x faster – use the SSO Admin account. 🙁
— Chris Wahl (@ChrisWahl) 9. Juli 2014
So how would you go on with troubleshooting the issue as there are several components involved that could be the actual bottleneck. It could be an issue on the client side, in the Web Client / C# client itself, vCenter Server, the Inventory Service, SSO or the actual Active Directory infrastructure.