problems of psexec

[davechurchill]

problems of psexec

[richard-kelly]

The -i option to psexec is supposed to make it launch normally. Make sure all quotes are included as in the instructions. Figuring out that command took some trial and error, and it worked going from Windows 10 (shouldn't matter) to a Windows 7 client. There may be some other requirements for the remote machine for PsExec to work properly. If the client is exiting quickly it might be a problem with the client settings. If the settings argument is incorrect or the settings file doesn't parse as JSON, or it has another error it would terminate quickly.

[davechurchill]

Keep note all this can be done without psexec, it's just for convenience of updating and starting clients

…

On Dec 15, 2017 9:12 AM, "Rick Kelly" ***@***.***> wrote: The -i option to psexec is supposed to make it launch normally. Make sure all quotes are included as in the instructions. Figuring out that command took some trial and error, and it worked going from Windows 10 (shouldn't matter) to a Windows 7 client. There may be some other requirements for the remote machine for PsExec to work properly. If the client is exiting quickly it might be a problem with the client settings. If the settings argument is incorrect or the settings file doesn't parse as JSON, or it has another error it would terminate quickly. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIkqJ5134pLsI03t9_MaWx4TednipEWks5tAnBDgaJpZM4RBoqD> .

[davechurchill]

Since this is not an issue with the TM software I will close the issue, but feel free to continue the conversation