aaaaa

[plkjnht]

.....

Edited August 14, 2019 by plkjnht

[Chris]

Hi,

Yes, this is the normal behavior, because Pulseway execute this command as the system in the session 0.

[Paul]

To further detail Chris's reply, all processes that are launched from the terminal or powershell console will execute in the same user session as the Pulseway service, called "session 0". This user session is isolated from the others for security reasons meaning that even if an application has a GUI, you will not be able to see it in your session's desktop. You could try to invoke the GUI process using PSExec specifying the required arguments to interact with the desktop (PSExec runs apps by default in the console session so you will be able to see the GUI). It's also worth noting that you want to skip the EULA by specifying the command line argument as Pulseway will not be able to click on the "Accept" button in the GUI form that pops up.

-Paul