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.
Hi All,
Late last year we introduced Backstage mode, which allows host to complete Windows terminal and powershell commands on the remote machine without interrupting the end user. Take a look at the documentation link above, it sounds like our Backstage feature meets this request!
This does not answer the request. We need one of the two options, or both:
1. An option in the "Run Tool" dialog that will run the tool/script in the backstage environment.
2. Running commands with unlimited or adjustable timeout (say 0-60 minutes).