[link text][1]Hi Hi Börnibär - Thanks for your detailed post. What version of PAExec are you using? -n: So if I understand correctly, PsExec will honor the timeout for connection, but then whether it connects or not, will still try to run the command? -i: This one is very tricky. Since it was (unfortunately) defined to take a parameter or not, it's hard to know if the thing that comes right after it is a session identifier or not. For example, with PsExec, the following will try to launch sess as though it was an executable: PsExec \\\\computer -i sess app So neither app seems to support -i as the last option. I'm not sure how to improve this in the parser. -s: Oh, I didn't know -s and -u could be used together in PsExec! It's now enabled in PAExec :) -cnodel: This one is simply a bug. Fixed. -clist: In the example given, the C:\bliblablub.txt C:\\bliblablub.txt file has a list of files to copy. But the command doesn't specify which app to launch (ie it needs blub.exe appended to the end). -csrc: This one was really added for us :) If you want to launch C:\\Test.exe on the remote server, but the file exists in C:\\MyFiles\\Test.exe, then you can use -csrc to tell PAExec where to copy the source file from. As I mentioned above, two fixes were made and the new version is now on the [PAExec website][1] [1]: http://www.poweradmin.com/PAExec/

[link text][1]Hi Börnibär - Thanks for your detailed post. What version of PAExec are you using? -n: So if I understand correctly, PsExec will honor the timeout for connection, but then whether it connects or not, will still try to run the command? -i: This one is very tricky. Since it was (unfortunately) defined to take a parameter or not, it's hard to know if the thing that comes right after it is a session identifier or not. For example, with PsExec, the following will try to launch sess as though it was an executable: PsExec \\\\computer -i sess app So neither app seems to support -i as the last option. I'm not sure how to improve this in the parser. -s: Oh, I didn't know -s and -u could be used together in PsExec! It's now enabled in PAExec :) -cnodel: This one is simply a bug. Fixed. -clist: In the example given, the C:\bliblablub.txt file has a list of files to copy. But the command doesn't specify which app to launch (ie it needs blub.exe appended to the end). -csrc: This one was really added for us :) If you want to launch C:\\Test.exe on the remote server, but the file exists in C:\\MyFiles\\Test.exe, then you can use -csrc to tell PAExec where to copy the source file from. As I mentioned above, two fixes were made and the new version is now on the [PAExec website][1] [1]: http://www.poweradmin.com/PAExec/