If you run the task from the login script, you potentially expose the admin credentials to the users, since the script / config file is readable to all users from the netlogon share. My tools send a request to the server. Only the server knows the admin credentials associated with the desired task, and the file that holds the task/credential data is restricted to Administrators only.
I can brush the dust off of the script and make sure there's sufficient docs if you or Doc want to give it a whirl. Basically, you- Extract the server tool to a file server
- Configure an INI file to define the task - NAME, BAT file, User Credentials, Drop Folder, and such
- You write a Kix script to detect a specific condition and call it from your login script. The script uses the APIs - a set of Kix UDFs - to communicate with the server.
- When the server receives the file from the client, it immediatey performs the command(s) associated with the task. This allows a single script to report multiple conditions and initiate multiple admin-level commands.
This is software that we sell to our clients through implementation. I'm offering you and Doc a copy if you are interested. Your cost will be feedback - tell me what can be improved in the API, User Guide, etc. I've been considering making this an add-on to our Universal Login Script.
PM me with your email address and I'll send the ZIP package once I clean it up a bit.
Glenn
_________________________
Actually I
am a Rocket Scientist!
