Prev: Desktop / Taskbar not visible when auto-launched program closed
Next: Could-based/Hosted/SaaS Terminal Services or Citrix solution?
From: Filken on 20 May 2010 16:54
There is a simple solution to this issue. The connection will use whatever
selection was last used to log into the Console session.
If you are physically at that server, or run the "MSTSC /admin" command it
will change the default login location to whatever you select when you log in.

Simple fix: Log into the server's console session (Session 0) and select the
desired domain. From then on it will default to the domain you selected.


"OC" wrote:

> Default Domain Name for Terminal Server login defaults to local computer name
> instead of domain name
>
> Hello All!
>
> It's about a 20 Terminal Servers 2003 network clustered through Microsoft NLB.
> DC, FS, SAN are all redundant and the network is a stable one, having been
> live for years.
> Most users reach the terminal servers by means of Neoware thin clients.
> There are about 1000 accounts, average online user number is 200.
>
> The issue is that sometimes at log-in time (read below) all terminal servers
> seem to agree to default to their computer name instead of the domain name
> (there is only one domain name, no trusts). This confuses thin client users
> who are used to click the 'Single button sign-in' on the initial login screen
> and enter their username and password to get into the system. Now they also
> have to pick the domain name which is indeed annoying for somebody with
> little technical background. Needless to say, most of them believe they
> forgot their passwords and call us to get them changed.
>
> Initial research pointed us to the DefaultDomainName key in the registry. We
> have created an Administrative Template file and loaded it in the GPO
> corresponding to the Terminal Servers OU. This seemed to have fixed the issue
> for a while.
>
> Afterwards, when the problem re-emerged we have taken the same setting and
> added it to the Default Domain Policy GPO. Again, things seem to have
> improved for a while.
>
> The last attempt was adding a vbs startup script to the terminal servers,
> which again seemed to improve things for a short while (I say 'seems' because
> the issue is intermittent, it sometimes works well for weeks and then
> suddenly goes crazy, without anyone of us making changes to their AD).
>
> We are looking for a permanent solution for this problem. This behavior is
> very strange to us, especially because everybody else seems to point out that
> this registry key is the solution.
>
> Thanks!
 | 
Pages: 1
Prev: Desktop / Taskbar not visible when auto-launched program closed
Next: Could-based/Hosted/SaaS Terminal Services or Citrix solution?