Completed the vsphere 5.1 upgrade on my production virtualcenter today and ran into what I consider to be a less than ideal situation. VMware support tells me that the issue has to do with the way Microsoft handles SSO. While that seems a reasonable enough explanation ( I mean who doesn't want to blame their problem on Microsoft), I am a bit skeptical about the whole matter. I'm wondering if anyone else has seen this issue and if it truly is a "feature" or there is a fix. Let me explain my setup to better paint the picture of what I'm seeing. First, I have a total of 3 domains. For the sake of this discussion we'll call the domain parent.com. I also have two child domains, child1.com and child2.com. All user accounts and computer accounts reside in child1.com.
Prior to today's upgrade an administrator could log into the web client and/or the Windows client using child1\username and password.
After the upgrade, the only way someone can log into either the web or the Windows client is by entering the entire FQDN (i.e., child1.parent.com\username) and their password. Using child1\username will fail to authenticate. This obviously means that the checkbox to use the Windows session credentials is absolutely worthless at this point.
As mentioned earlier VMware support blamed SSO and/or Microsoft saying that it has something to do with the fact that the accounts are coming from a child domain. I am having a difficult time swallowing the entire explanation and an interested in finding out if there is a way to get back the old login capabilities. Any assistance would be greatly appreciated as I have to do this again soon on my vdi virtualcenter and if this is the result of something I did wrong I would prefer to avoid that.