vSphere

vCenter Server (5.5) on Windows to vCSA 6.5: Ho… |VMware Communities

Hi,

 

I attempted to update a Windows vCenter Server 5.5 to vCSA 6.5

 

After reviewing the migration-assistant.log I see a reference to a hostname and AD domain that no longer exists and the current CorrectFQDN and AD domain that does exist.

 

migration-assistant-15259038| I: ParsePreUpgradeOutput: VC machine/cert parameters. AppNetPnid: [CorrectHostname.contoso.local], CertIPs: [], CertFQDNs: [IncorrectFQDN.contoso-wrong-domain.local].

migration-assistant-15259038| I: ParsePreUpgradeOutput: SSO machine/cert parameters. AppNetPnid: [CorrectHostname.contoso.local], CertIPs: [172.X.X.X,192.X.X.X], CertFQDNs: [CorrectHostname.contoso.local].

migration-assistant-15259038| I: ParsePreUpgradeOutput: Database settings: Type=’embedded’

 

Error: Failed to discover a system name that is compatible with both your VMware CorrectHostname Server certificate and your VMware Single Sign-On certificate that can be used to migrate to a VMware CorrectHostname Server Appliance with an embedded Platform Services Controller.

migration-assistant-15259038| I: ParsePreUpgradeOutput: Resolution: Regenerate your VMware CorrectHostname Server SSL certificate and your VMware Single Sign-On SSL certificate to have a common system name that can be used to migrate your system to VMware CorrectHostname Server Appliance with Platform Services Controller.

 

I check here: C:ProgramDataVMwareVMware VirtualCenterSSL

 

rui.crt references the incorrect hostname and AD domain

sso.crt references the correct hostname and AD domain

 

Do I need to follow this: VMware Knowledge Base 2110943?

Is it advisable to take a snapshot in case of human error so we can revert back? Or is it better to just go through and regenerate the certs again?

 

edit: grammar, sp


Source link

Tags

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Close