Run a command as a separate / background process
Running a client-side command via the Commands tab is limited not only by amount of output but also by time. In other words a command run at the prompt will be killed if it exceeds a web.config specified period of time (10 seconds by default). It is quite common to want to run a command that takes longer than 10 seconds. For example, I have a disk cleanup powershell script that I push to clients that can take 10-12 minutes to run. Changing the default timeout period in web.config is not a good solution to this problem, as the system essentially hangs waiting for the command to complete.
Suggestion: offer an option to run the command as a spawned / background process on the client, similar to running a program or batch script via the START or CALL commands (and suppressing the pop up of a command window on the client). Thus, the command will execute on the client without tying up the Commands tab. An additional enhancement would allow for capture of output to a log file and emailing the result to the technician upon completion of the command.
Please do this and also tag commands with a unique id so we can tie requests/responses together.