Same (one) user on any workstation. Haven't tried a "plain" bat file yet. If I could get the command window to stay up long enough to read the stupid error I could do more I'm sure. I've tried DEBUG ON, but it ignores it until the script is called "manually" (as opposed to invoked during logon). The script runs perfectly fine when called "manually" by this user. It only fails during the logon.
[ 20. August 2003, 17:38: Message edited by: DaveS ]
_________________________
silence is golden, but duct tape is silver
