I have found that when a RDP session that connects with Seamless SSO is interrupted, if the Network Location Awareness service decides to go into 'identifying' for even a half second, when the RDP connection goes to resume, SSO credentials do not work. However
I have found that the times that the NlaSvc does not go into 'Identifying' then the connection will resume just fine. It appears that when its 'Identifying' even if I have the local policy set to 'Private' for Identifying connections, then SSO does not work.
Is there a fix for this? Can RDP be made to wait or reattempt SSO credentials again automatically? The NlaSvc always goes back to DomainAuthenticated properly, even after half a second, but its still too late as RDP appears to have already tried reconnecting
and fails to pass credentials at which point it prompts for a password.
I really need the reconnecting feature to work. Anyone have any ideas to solve this?
