Good idea.... but that means having a file with a password in plain txt on the LAN?
Don't know why you would think so... The scheduled task runs with the credentials you supply, and doesn't need any additional credentials in the script.
The script that creates the scheduled task only needs to be run once to create the task - it's being done by you, not the end user, and you can supply the password as an argument when you invoke it.
There are ways to obfuscate the password (see CODEC UDF), and tokenizing the setup script would ad a level of security as well. There's also Shawn's Runnas.exe.
Glenn
_________________________
Actually I
am a Rocket Scientist!
