VMware Cloud Community
rjgwmwl
Contributor
Contributor

Unable to rename vCenter 6.7

Hello

Our customer has a vCenter server with the hostname 'vcenter'. I've upgraded to 6.7.0.42000 so that I can rename it, but the process (as outlined in Changing your vCenter Server's FQDN - VMware vSphere Blog)​​) produces the error:

"The SSO username does not have administrator privilege."

Obviously I've checked that administrator@vsphere.local is indeed an administrator and everything looks OK. I've tried to create another user, but this process only accepts administrator@vsphere.local.

Google draws a blank on that error.

Any ideas?

8 Replies
Alex_Romeo
Leadership
Leadership

Hi,

Cannot change the vCenter Server or Platform Service Controller 6.x hostname on versions prior to vCenter Server 6.7 Update 3

VMware Knowledge Base

-------

Changing your vCenter Server’s FQDN:

Changing your vCenter Server's FQDN - VMware vSphere Blog

ARomeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
jburen
Expert
Expert

Is the PSC embedded? Afaik it is only supported with an embedded PSC.

Consider giving Kudos if you think my response helped you in any way.
Reply
0 Kudos
rjgwmwl
Contributor
Contributor

Reply
0 Kudos
rjgwmwl
Contributor
Contributor

PSC is embedded

Reply
0 Kudos
Deso1ator
Enthusiast
Enthusiast

I don't know about this one. I think you need to open a support case. The rename feature is very new so I doubt there's many people experienced with troubleshooting it just yet.

Reply
0 Kudos
nullifi
Contributor
Contributor

I also experienced this exact same issue! After a week of working with VMware support they confirmed in my situation that this is a bug and it will be resolved in the next patch. I am currently on 6.7u3g, so likely 6.7u3h will resolve this.

IRIX201110141
Champion
Champion

nullifi

thx for that info! Iam facing the same problem and we are currently on 6.7u3 latest. Can you please post your #SR?

Regards,
Joerg

Reply
0 Kudos
nullifi
Contributor
Contributor

Certainly, 20139857807

looks like the next patch should be here next month according to my support tech.

I am needing this fixed so I can Cloud Gateway, currently it’s failing because the PNID isn’t matching the FQDN.

Reply
0 Kudos