Everybody knows this warning. Now I show you how to change the vCenter Certificate to avoid this ugly page.
For those who are completely new to this topic I suggest you to check out https://tenthirtyam.org/inf4529/index.html
VMware vSphere has multiple components who own a Certificate. There are:
- ESXi Certificates
- Machine SSL Certificates
- Solution User Certificates
- Single Sign-On Certificates
We have four different options for doing Certificates in vCenter Server 6
- VMCA (VMware CA) as root CA
- VMCA as Enterprise CA Subordinate
- Custom CA
Today we care about the Hybrid Mode. That means we will replace the Machine SSL Certificate with an official one from eg. QuoVadis and leave the other Certificates like ESXi or Solution Users by default.
First we have to open the vSphere Certificate Manager witch is located under:
- Windows vCenter 6.0 “C:\Program Files\VMware\vCenter Server\vmcad\certificate-manager”
- vCSA 6.0 (vCenter Server Appliance) “/usr/lib/vmware-vmca/bin/”
(The Certificate Manager is the same in Windows vCenter as in vCSA)
We use Option 1 and fill out the requested information.
With your created CSR-File you can go to your CA to request a Certificate. After some checks, you should get from your CA a .csr-File back.
With our .csr-File we can start the import.
So, again we start the Certificate Manager. Select option 1 and option 2 to replace the Certificate and follow the wizard. We have to fill out the paths to the Machine-Certificate, the created Keyfile and finally the Root-Certificate.
In the end, hopefully you get the message “All tasks completed successfully” 😉
After all vCenter services were restarted, be patient for the Webclient-Service (a few minutes) to complete everything.
You should see now the correct Certificate when you connect to your vCenter.
- Don’t forget to tell your 3rd Party Applications about the new vCenter Certificate (eg. the Backup Software)
SSL Error with Update Manager:
I got the following SSL error after changing the vCenter Certificate:
To avoid or solve this, we have to re-register the Update Manager Service. (Described in KB: 2048210)
Go to: “C:\Program Files (x86)\VMware\Infrastructure\Update Manager” and start the “VMwareUpdateManagerUtility.exe”
Choose “Re-register to vCenter”
Restart the Update Manager Service
Enjoy and share 😉 !