Click to See Complete Forum and Search --> : NT/2000 script manipulation
Brian Echard
08-12-2002, 02:52 PM
We have an NT PDC. On this same doamin, we have a 2000 Server for Terminal Server connections. Our normal user scripts are specific for each location and thus the scripts can be executed at the TS when clients log on. Aside from creating a new TS specific user account (i.e. username vs. usernamets) for each person using TS, can we somehow disable or get around the scripts just for logging into TS?
We have tried removing the usrlogon.cmd from the registry. Doesn't work.
Steve
08-14-2002, 10:56 AM
Brian,
Could you not put an environment variable on the server and then get the script to test for it and then it could be set to skip the script if the variable equalled terminal server.
------------
Brian Echard at 8/12/2002 3:52:54 PM
We have an NT PDC. On this same doamin, we have a 2000 Server for Terminal Server connections. Our normal user scripts are specific for each location and thus the scripts can be executed at the TS when clients log on. Aside from creating a new TS specific user account (i.e. username vs. usernamets) for each person using TS, can we somehow disable or get around the scripts just for logging into TS?
We have tried removing the usrlogon.cmd from the registry. Doesn't work.