VMware Cloud Community
ccboe
Contributor
Contributor

vcenter 5.1 to 5.5 fails

As per kb 2060511.

When I web browse to look at the cert, the dns name is wrong. It is the original name from when windows was installed not the name I changed it to.

Should I just put the wrong host name in the reg or fix the cert?

If fix the cert, how???

Thanks

Tom

Reply
0 Kudos
6 Replies
admin
Immortal
Immortal

It would not be a good idea to use the wrong hostname in the reg or to keep the certs at this stage. You can change the certs using the vCenter Certificate Automation tool -> http://kb.vmware.com/kb/2057340

ccboe
Contributor
Contributor

I get this error after I generate csr and install for sso

2013-10-02T10:04:10.285-0400 [c.v.s.cfg.SsoUpdaterMain] ERROR One or more required parameters are not set or have invalid values:

2013-10-02T10:04:10.300-0400 [c.v.s.cfg.SsoUpdaterMain] INFO    - I/O error reading the key file c:\ssl-certificate-updater-tool-1308332\requests\vCenterSSO-vcenter5: c:\ssl-certificate-updater-tool-1308332\requests\vCenterSSO-vcenter5 (Access is denied).

2013-10-02T10:04:10.300-0400 [execution] INFO  TOOL END with status code = 3

Thanks

Tom

Reply
0 Kudos
ccboe
Contributor
Contributor

The tool only creates .key and .csr files.

I was thinking it also made cert files (self signed).

I just ran openssl to make the cert file.

The update of sso still fails prematurely.

I guess I will do a fresh install. Would have saved me hours if I did this from the beginning Smiley Sad

Thanks

Tom

Reply
0 Kudos
admin
Immortal
Immortal

Sorry to hear that. Can you create a SR with support for the SSO install issue?

Reply
0 Kudos
ccboe
Contributor
Contributor

Now I can't get into my vcenter 5.1.

What is the best way to get my esxi hosts into a new vcenter server. I cant get into the old one to remove.

Thanks

Tom

Reply
0 Kudos
raog
Expert
Expert

If you have a new VC 5.5 server, you can simply add the hosts back, it will throw a warning about the hosts already being managed by another VC, ignore that and add them.

If connecting/adding back the hosts from your new VC is not working, you can to disassociate the ESX servers forcefully by deleting the vpxa agent in each ESX.

Regards

Girish

To Virtualization and beyond! PS::If you felt the answer as helpful, please mark it as helpful/answered so that it helps other users as well! Blog:: www.virtualtipsntricks.com
Reply
0 Kudos