MED-V 1.0: Single Sign-on (SSO) fails even though it is properly set in the Workspace Policy
MED-V offers a feature where persistent workspaces can leverage a host machine or domain account for single sign-on. This property is enabled only when Workspace is persistent is selected.
When you configure Single Sign-on for a workspace policy in the MED-V management console (per guidelines specified here: http://technet.microsoft.com/en-us/library/ee348992.aspx) you may find that the workspace will either:
– Logon automatically using the local administrator account.
– Prompt for a local login inside a Virtual Machine Window (especially if domain joined).
This can be caused by one of the following:
– A failure to either set the VM setup script’s “Join Domain” component properly in the management console.
– A failure to join the domain due to an underlying issue
– Not including the “Disable Auto-login” component as the last step in the VM setup script.
If this is happening you will need to verify the following:
– If the “Join Domain” option is not included, please add it per the guidelines in the following link: http://technet.microsoft.com/en-us/library/ee348997.aspx
– If there is a failure to join the domain or connect to the domain, it is best to check the System Event Log in the workspace’s guest OS. There are several ways to access this event log from MED-V. A common way is to publish the Start Menu or a Command Prompt (CMD.EXE) within the workspace policy and launch the Event Viewer directly. Refer to the following link for publishing applications: http://technet.microsoft.com/en-us/library/ee348923.aspx
– The “Disable Auto-login” component should be added as the last step in the VM setup script following the “Join Domain” component.