Created new Windows 7 desktop in a linked-clone pool. Using the View Client to access the new VM, I am prompted a second time with the Windows 7 login. It is not passing the credentials through for the SSO login to Windows.
Using this document (KB 1029391) I have checked the following:
To troubleshoot issues when using SSO in a VMware View Environment:
I also checked the setting mentioned in KB 1019466:
On Windows Vista, if you install the PCoIP Server component, the Windows group policy Disable or enable software Secure Attention Sequence is enabled and set to Services and Ease of Access applications. If you change this setting, single sign-on does not work correctly. Ensure that the Windows group policy Disable or enable software Secure Attention Sequence is enabled and set to Services and Ease of Access applications. This is also set as stipulated here.
Anyone have any ideas? I've spent an embarrassing amount of time on this and have not come any closer to getting the SSO to work. I must be missing something -but what?
Thank you for your suggestions folks. After some more troubleshooting, I started to remove components from the equation and found the problem to be Imprivata which we use for our SSO here. Apparently the version I was attempting to use had issues with Windows 7, because we installed a newer version (after updating our appliance) and voila! the sso worked perfectly. I don't know why I didn't think of that earlier, hopefully this thread will save someone else some time.
Have You tried to create a Blank OU and disabled Override Policies
Have you tried completely uninstalling the VMware View agent, reboot, then re-install? We ran into an issue where a program got installed later on in the image that overwrote the VMware View SSO settings.
Thanks
Thank you for your suggestions folks. After some more troubleshooting, I started to remove components from the equation and found the problem to be Imprivata which we use for our SSO here. Apparently the version I was attempting to use had issues with Windows 7, because we installed a newer version (after updating our appliance) and voila! the sso worked perfectly. I don't know why I didn't think of that earlier, hopefully this thread will save someone else some time.