In testing the unsupported by VMware VCS-to-VCSA converter fling in my autolab lab I've run into a strange issue.
The conversion seemed to go well, but for some reason I cannot log into the new vcenter server appliance using active directory accounts via the fat client. Each time it will give the error 'incorrect username or password.' Web client works fine with the same account though. Very weird. So right there we know the username and password is correct, it just logged in!
Administrator@vsphere.local gets in via the web and fat client just fine.
I found this kb article that matches my issue and I confirmed my logs show the same events mentioned.
http://kb.vmware.com/kb/2091631
However, their workaround does not work for me.
I tried resetting the account's password or adding a new account, removing and re-adding the AD domain as an identity source, removing and re-adding the users to the permissions of the vcenter using the SSO admin account.
I restarted everything a few times and confirmed from the vcenter admin portal that the VCSA was connected to AD, and tried just using another workstation to log in. No dice.
I then fell back to the original VCS and turned off the VCSA. I needed to disjoin it from the domain and re-join it before removing and re-adding the users from the vcenter, but eventually I was able to log in using the fat client.
I'm just wondering if anybody else has run into this who would know of a solution.
I'm running this in the lab to see what to expect for an eventual production migration so suffice it to say things are not looking good for this plan, but I'd love to get off the VCS!
Thanks