We have a terminal server that users from other sites RDP into. If they are on the default domain, they can use saved credentials just fine. However if their saved credentials is one of our child domains, then they get the logon screen with the domain set
to the default domain - so
their saved credentials do not work.
I do not believe this is a setting on the client's end - I can test from one of the child domains, and provided I use saved credentials from our primary domain, I can log in without prompting. However if I use saved credentials from a child domain, then
I get the logon screen with the domain set back to the primary domain.
There were a couple of GP settings I thought might be creating this behaviour so I have disabled them as follows:
Originally, the following setting was set to the primary domain: Computer Configuration > Policies > Administrative Templates > System > Logon > Assign a default domain for logon. I have now set this to disabled.
I also noticed a custom ADM template with a registry setting SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon \ DefaultDomainName set to the primary domain - I have set this to not configured, removed the template, and deleted the registry key
and rebooted the server.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.