vCenter - Windows session credentials cannot be used

[KapsZ28]

This is driving me nuts. I recently installed vCenter Server Appliance 6.0 with an external Platform Service Controller. I found this article which would be great news if it applied to me. http://kb.vmware.com/selfservice/mi...nguage=en_US&cmd=displayKC&externalId=2119332

Apparently this was a known issue that was resolved with Update 1. Well, I am using Update 1. I downloaded and installed the latest version and there are no updates available.

I also came across this article which is think is more closely related to the problem. http://kb.vmware.com/selfservice/mi...nguage=en_US&cmd=displayKC&externalId=2020970

Reason being is when I was adding the ESXi servers to vCenter, they would not resolve using just the hostname. I needed to enter in the FQDN. Funny thing is it worked at first and then all the sudden stopped resolving just the hostname. Going by the last article, I made sure the hostname, FQDN and search domains are correct in the vCenter Server appliance and Platform Services Controller. Hell, when I am SSH'd into either of them I can ping hostames without any issues.

I've rebooted both countless times and even removed the PSC from our domain, and re-added it. I checked our DNS servers multiple times and there are no duplicates, the IPs are correct, RDNS is setup. I pointed vCenter and PSC at different domain controllers. Doesn't seem to matter. I can login fine if I type in my credentials, but I can't check the friggin box to use Windows session credentials and it is making me mad.

What could it possibly be?

 

[t_ski]

Possibly either LDAP setting or something wrong with the SSO service. On a side note, I have a random issue that pops up on my 5.5 environment where I can't log in the first time using Windows session credentials, but the second time it goes right through. Probably not the same issue though.

 

[KapsZ28]

For the Identity Source type I am using AD Integrated Windows Authentication with the Machine account. So there really aren't any settings.

I did however come across an article about the C# client not supporting Windows session credentials in 6.0. Not sure if it is true or not since it did work originally. I tested the web client and that does seem to work fine.

 

[Mackintire]

Log into the vcenter 6.0 update 1 appliance using your vCenter SSO setup master account (the one that defaults to using vsphere.local)

Do this: http://www.virten.net/2015/02/how-t...n-in-vcenter-6-0-platform-service-controller/

Restart the VMCA

Then do this: http://www.virten.net/2015/02/vcenter-server-appliance-6-0-vcsa-ad-domain-join/

Restart the VMCA again

The go to Administration --> Single Sign-On--> User's and Groups: And create a Domain vCenter Administration group MAKE CERTAIN you create this group in the vsphere.local domain. In the bottom half of the page add your company's domain user accounts to the vsphere.local group you just created. Add your preferred working domain account to this group. Note: when using the VMCA you can not add domain groups to local permissions groups.

Create a Datacenter, go to the permissions for that datacenter and add the vCenter Administration group you created above,. Give that group Administrator rights to the datacenter, make certain you have the "apply to child object button checked".

Restart the VMCA.

Log back into the VMCA portal with your company's domain account. You should have administrator rights to the datacenter and every child object below.


Life should be good now.... go have a beer.