Preventing Roaming Policies on a Terminal Server

[dcaine]

I have a Windows 2000 Terminal Server running in a 2003 AD environment (I hope to have it replaced with W2K3 next year). In the meantime, I need to prevent roaming profiles from being applied only on the terminal server. The roaming profiles need to be active on any other machine a user logs into. I've tried looking through a Machine policy and a local policy, but nothing seems to fit the bill.

Thanks,

[AdamV]

So you want a user A to be able to log on to PC1 and PC2 and have the same environment, but not get that when they log onto Terminal ServerX?
Do you want them to get the same profile between TS X and TS Y? (or do you have only one?)

In AD properties you can separately specify the users' TS Profiles path. This can be the same as or different from the 'normal' profiles path, or can simply be left blank to have no roaming between TServers.

If you already have this set to blank and users are still getting this profile, make sure you clear out the profiles from the server so they start from scratch again (and be sure to set up a really good .default profile for them)