I'm not exactly sure what you want to achieve, but here are the
options:

Users should *never* use the same profile for their normal
workstation logon and their TS sessions (to avoid profile
corruption).

To set a TS-specific roaming profile:
a) Use the "Terminal Services Profile" tab in the AD account
properties or
b) configure a Group Policy, linked to the OU which contains the
Terminal Server machine account, and use the setting
Computer Configuration - Administrative templates - Windows
components - Terminal Services
"Set path for TS roaming profiles"
Note that you should *not* add %username% here, just something like
\\server\TSprofiles
Combine this with the following setting:
Computer Configuration - Administrative templates - System - User
profiles:
"Delete cached copies of roaming profiles"
to avoid filling up your system disk on the TS.

If you want to enforce local profiles on the TS (which I do *not*
recommend, because it will be a pain as soon as you have more than a
single TS AND the profiles will soon fill up your system disk on the
TS):
Use a GPO with the following settings:
Computer Configuration - Administrative templates - System - User
profiles:
"Only allow local user profiles"
"Prevent Roaming Profile changes from propagating to the server"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?S1Q=?=" <KT@discussions.microsoft.com> wrote on 29 okt
2005 in microsoft.public.win2000.termserv.clients: