Batch file kickoff of executable acts strangely

[Doc]

Scenario.
W2k3 domain servers
W2k + XP clients
Run Login Scripts Synchronously enabled at top level


I'm pushing a batch file to my test OU. The batch file runs an executable with a simple switch. ie
\\domain\sysvol\blah\plicies\blah\user\scripts\log on\audit.exe /auto


The batch file works fine, the login script opens it and I can see the executable process during login. 5-10 seconds later the executable stops processing, no error in logs. When I toss a pause in the batch file at the end, the process will stay open and runs fine, completes and posts. BUT, the windows 2k machines will hang for 10 minutes before giving over explorer due to synchronous logins.

When I run the batch file manually the operation completes and runs. Just the startup scenario.


Thanks for any replys and the patience. I was "handed" GP a short while ago and I'm still learning. I've read through a few dozen posts and I'm sure I've found my new home.

[AdamV]

For a bit of clarity:

does this fail on all clients, or only W2000?

reading between the lines, this is assigned as a logon script and linked to an OU with users in - is this correct?

is this the only script that is running?

[Doc]

The script fails to stay open on the XP clients, but runs fine on the 2k clients.

It's a script is a logon script assigned to a Users UO.

It's the only logon script running.