Here's the situation... I have a logoff script that runs to copy a few files (nothing big) from a user's PC to a network share.
A lot of times, users will disconnect their laptop from their docking station and walk away with it, and shut down without being on the network. When they do this, occasionally the logoff script runs for a VERY long time. My guess is that they cannot read the script off the NETLOGON directory, since they aren't on the network, yet it's being queued to run as they log off since they still have the policy for it.
What is the method to alleviate this? I don't want them to run policy based scripts if they aren't on the network, and it happens only occasionally, but since it happened to me today (took my laptop off the dock for a presentation, and shut down... took 20 minutes!)
Thanks very much for any help.
As an aside -- I set the maximum wait time to 5 minutes for script processing... it doesn't seem to have helped much.