I've got a handful of tools that I would like to be able to run with command line parameters attached to them, most notably, some of the Sysinternals programs which allow for /acceptEULA, others for passing on drive letters, and such.

I could cobble together an AutoIt script that would drop the program onto the client's system and then start it with parameters but that doesn't help the average SC user.




Another thing I'd like to be able to do is automatically run a Tool as Admin. My first thought would be either tools in a specific folder or renamed to start with a specific character so that any file starting with, say, "&" would be sent to the client with Admin authorities.

Well, in AutoIt, it could be a script as simple as:

FileInstall("c:\tools\df.exe", "c:\support\df.exe") ;pack the file into the compiled exe and drop it to the Support folder on customer's system
Run("c:\support\df.exe c: /qd") ;run a quick defrag using Piriform's defraggler on the C drive


As for running as Admin, to be honest, I'm surprised that every app doesn't _already_ run with privileges. If I run a batch file as Admin, every program that it starts gets the same authority. If SC is running as a service.... ?