VMware Cloud Community
theslim1
Contributor
Contributor

Upgrading from vCenter 5.5 U3 to 6.0 U2M - Migration Assistant - "Unable to collect Active Directory configuration"

I'm encountering issues when using the vMware migration tool to upgrade from vCenter 5.5 U3 to 6.0 U2. The site has a single SSO domain, integrated on the same server as a windows installation of vCenter. The following errors are noted in the log;

2016-11-08T19:16:58.977Z INFO base_commands Executing command: [<class 'upgrade_commands.CollectActiveDirectoryConfigWindowsCommand'>]

2016-11-08T19:16:58.978Z INFO upgrade_commands Start collecting AD configuration from host --vcenter.int.yccesa.org

2016-11-08T19:17:01.486Z ERROR ma_utils Unable to invoke MA. Error The entered VMware Single Sign-On credentials are not valid.

pastedImage_10.png

It seems to be rejecting my "administrator@vsphere.local" account, even though I have validated that this is a working account. Any ideas?

Reply
0 Kudos
2 Replies
LucianoPatrão

Hi,

Windows vCenter and VCSA work different ways with DNS Reverse Lookup

Check your DNS entries and see if all have proper Reverse Lookup. Maybe this could help.

But could be different issues, check here: https://kb.vmware.com/kb/2113115

Could be also if you use different Identity Sources or even password with special characters.

Check this ones also: https://kb.vmware.com/kb/2060746

Also dont forget to read all vCenter upgrade documentation: vSphere 6.0 Documentation Center

Hope this could help.

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT
Reply
0 Kudos
theslim1
Contributor
Contributor

Thanks for the guidance. I resolved this issue by re-entering the "administrator@vsphere.local" password in the Migration assistant helper on the windows vCenter server, and running the upgrade again. For anyone reading, remember to double check your passwords.

Reply
0 Kudos