Isn't SU part of the Windows resource kit utilities? If so (I may be wrong, but) you would have to copy it up to a location where the script could invoke it under the context of the user logging on. That could mean one public share on a given server, or copied to the scripts folder on all your logon server (through replication).
Then your script would have to reference the call to SU.exe with a qualified path. For example: @lserver+"\su.exe" or something. If you have the resource kit installed on every client, then forget everything I just said. I hope that helps?
_________________________
silence is golden, but duct tape is silver
