Vyacheslav

Since I can't get synchronous process execution to work( https://sourceforge.net/p/staf/discussion/104046/thread/66bfe4d234/ ) I decided to try running it asynchronously like this: staf '{machine_name}' process start shell command 'C:\\something.exe' stderrtostdout returnstdout notify onend sameconsole Executing this command gives me some process handle, say, for example, 77. I can check whether its done or not by staf '{machine_name}' process query handle 77 I checked registrations, and my current...

Since I can't get synchronous process execution to work( https://sourceforge.net/p/staf/discussion/104046/thread/66bfe4d234/ ) I decided to try running it asynchronously like this: staf '{machine_name}' process start shell command 'C:\\something.exe' stderrtostdout returnstdout notify onend sameconsole Executing this command gives me some process handle, say, for example, 77. I can check whether its done or not by staf '{machine_name}' process query handle 77 I checked registrations, and my current...

Thank you for answering. Extensive googling reveals that it may have to do with the fact that all machines are virtual, and VMware Workstation has some weird things with idle tcp connections. I'll have to look into alternatives.

I'm trying to execute .exe on remote machine with the following simple command: staf '{machine_name}' process start shell command 'C:\\something.exe' stderrtostdout returnstdout wait I don't get any errors, it just stays there without any answer(ctrl-c interrupts just fine). I ran that exe locally on that machine, it works for 3 minutes, writes to file and exits without any errors. I tried running this STAF command on three different machines. Remotely, it worked on Windows Server 2016 machine, but...