TS logon script doesn't run

[Paul Hadfield]

All,

2000 AD setup with 2 x DC's running 2000 Server and multiple 2000 Advanced
Terminal Servers in application mode.

Hundreds of users configured in active directory each with a logon script.
Also the Environment tab is configured to load a bespoke in-house app
instead of Explorer.exe for a GUI. This works fine. When a user logs on the
script executes - as expected - followed by the custom GUI.

However, every once in a while (may be one in every 20 or so logon's) the
logon script fails to execute and I can't figure out why. The bespoke GUI
loads every time without fail, but the logon script will sometimes fail to
execute. I've managed to prove this by adding Echo %username% logged on at
%time% %date% >> \\dc01\logoncheck$\%username%.txt to the first line of the
logon script. Then created multiple test accounts and spent all morning
logging then in and out, in and out, in and out....

There seems to be no pattern. Doesn't matter which account, which TS server
etc..

Has anyone any ideas why this might be?

Cheers,
Paul.

 

[Vera Noest [MVP]]

I would add %logonserver% to your "echo" statement, just to see if
it makes a difference on which DC the users are authenticated.
What exactly is the search path to the logon script?
I would also enable verbose logging of the user environment:

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[Paul Hadfield]

Vera,

Will enabling debug logging likely lead to any kind of performance impact on
the DC's as they are pretty busy little bunnies at the moment?

Cheers,
Paul.

 

[Vera Noest [MVP]]

I don't really know. Depends on too many factors.
But you could turn it on during less busy hours (when most regular
users have already logged in), and then spend another couple of
hours logging in and out with your test accounts, until the problem
appears. And then turn logging off again.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___