VMware: Error 26002/26006 - Upgrading vCenter from 5.0 to 5.5 w/ CA signed certs
There are troves of these articles online about this so I'll try to keep this concise.
Steps for moving from one VM (assuming Windows and SSO/PSC already in place) to another:
Details:
Essentially, getting the error above was because I did not follow VMware's instructions on updating my signed cert. If I did things properly, meaning updating both the Inventory Service and vCenter Service w/ the same signed cert, I would not have gotten the above error.
Meaning I generated a signed cert from my internal CA and only applied it to the vCenter service. The Inventory Service was still using a self-signed cert, which when an upgrade is attempted causes it to blurt out the above error.
Steps for moving from one VM (assuming Windows and SSO/PSC already in place) to another:
- Shut down and disable services on original VM.
- Rename original VM.
- Rename new VM to original VM's name.
- Create the following directories on new VM:
- C:\ProgramData\VMware\Infrastructure\Inventory Service\SSL
- ProgramData is typically always on C: drive, so this is a must.
- C:\ProgramData\VMware\VMware VirtualCenter\SSL
- ProgramData is typically always on C: drive, so this is a must.
- C:\Program Files\VMware\Infrastructure\Inventory Service\SSL
- C: drive can be replaced w/ drive that you plan to install inventory services.
- Copy your signed certs from your old VM to this new one in the above directories.
- rui.pfx
- rui.crt
- rui.key
- In the case of the VirtualCenter SSL directory, you'll probably also need the following, I think they are used for the custom spec passwords:
- sms.truststore
- sms.keystore
- End Result before installations begin, should look like this:
- Once you do this and backup the SQL server database, you should be ready to move forward.
Details:
Essentially, getting the error above was because I did not follow VMware's instructions on updating my signed cert. If I did things properly, meaning updating both the Inventory Service and vCenter Service w/ the same signed cert, I would not have gotten the above error.
Meaning I generated a signed cert from my internal CA and only applied it to the vCenter service. The Inventory Service was still using a self-signed cert, which when an upgrade is attempted causes it to blurt out the above error.
Comments