There are several ways to do this:
1) define the logon script in a Group Policy. Link the GPO to the
OU that contains the user accounts. Define another, TS-specific GPO
which does *not* run the logon script (or runs a TS-specific logon
script). Configure the TS-specific GPO with "loopback processing"
with the "replace" option, and link it to the OU that contains the
Terminal Server machine account (but not the user accounts!).
This is my recommended approach.
2) you can check on the environment variable %computername% in your
logon script, and when it equals to the name of the Terminal
Server, jump out of the script. This is initially easier to
implement, but less flexible and becomes a nightmare when you have
several Terminal Servers.
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
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___