Re: Configuring profiles

Tech-Archive recommends: Fix windows errors by optimizing your registry

You can avoid creating multiple user accounts, when you use
loopback processing of the GPO, and link the GPO to the OU which
contains the Terminal Server machine accounts, *not* the user
accounts.
Loopback processing is especially created for this situation.

260370 - How to Apply Group Policy Objects to Terminal Services
Servers
http://support.microsoft.com/?kbid=260370

231287 - Loopback Processing of Group Policy
http://support.microsoft.com/?kbid=231287
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Rob S <robatworkDeleteTheseFourWords@xxxxxxxx> wrote on 31 maj
2006 in microsoft.public.win2000.termserv.clients:

On 30 May 2006 13:38:50 -0700,
"jude@xxxxxxxxxxxxxxxxxxxxxxxxxxx"
<jude@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

-Hello, I am in the process of installing a new Win2K3 network,
with one -server for active directory, and one server for
applications. One -application will be run under terminal
services. I am thinking that a -good setup would be to create a
terminal services OU for the 7 users. -Then I can apply policies
to the OU. The clients would log onto the -domain, and then
invoke a term. services session; thereby preventing -any
conflict with their domain profile and a term. services profile.
-Does anyone have any feedback for me on this scenario? Thanks,
Jude


We do something similar. Points to note:

Use different user names for the users "windows" id, and their
terminal services one, so the windows ones don't get effected by
the policies on the OU

If you put a policy on the OU, and then put the users in it,
only the User configuration is acted upon, the Computer Config
is ignored.

This may help
http://www.microsoft.com/windowsserver2003/techinfo/overview/lock
down.mspx

regards
-Rob
-Rob
robatwork at mail dot com
.

Relevant Pages

  • Re: Disable Automatic Locking
    ... your Terminal Server runs on a different server than your SBS2003? ... Configure this in a GPO which is linked to the OU that contains ... 231287 - Loopback Processing of Group Policy ... > Terminal Services. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Time in Exchange through Terminal Services
    ... Configuring Terminal Server for Differing Time Zones ... 260370 - How to Apply Group Policy Objects to Terminal Services ... 231287 - Loopback Processing of Group Policy ...
    (microsoft.public.windows.server.sbs)
  • Re: Time in Exchange through Terminal Services
    ... Configuring Terminal Server for Differing Time Zones ... 260370 - How to Apply Group Policy Objects to Terminal Services ... 231287 - Loopback Processing of Group Policy ...
    (microsoft.public.windows.terminal_services)
  • RE: Cannot log in
    ... Corrupted or very large Terminal Server profile? ... > One of my accounts cannot login into any of my servers via Terminal Services. ... When they put the UserName and Password to login it looks like it is going in ok but then just sits at the Blue Desktop screen and never brings up any icons. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Incorrect colors
    ... Terminal Services relies heavily on a glyph cache for onscreen ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > interesting that some controls do change and some do not. ... >>> display in the selected background color. ...
    (microsoft.public.win2000.termserv.clients)