# PSEXEC: Program interacts with remote computers' desktop screen

**URL:** https://www.finalbuilder.com/forums/t/psexec-program-interacts-with-remote-computers-desktop-screen/2213
**Category:** Discussion
**Created:** [October 30, 2013, 8:58am UTC](https://www.finalbuilder.com/forums/t/psexec-program-interacts-with-remote-computers-desktop-screen/2213 "2013-10-30T08:58:11Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![davestiff](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/d/f08c70/32.png) [@davestiff](https://www.finalbuilder.com/forums/u/davestiff)
#### Post date: [October 30, 2013, 8:58am UTC](https://www.finalbuilder.com/forums/t/psexec-program-interacts-with-remote-computers-desktop-screen/2213/1 "2013-10-30T08:58:11Z")

</div>

Hello,

&nbsp;does using this option not allow FinalBuilder to log output from the Program that is being run?

(I enabled this option since PowerShell was not executing on the remote machine but now none of the batch file that PSEXEC launches is being logged)

Thanks,

Dave

---

<div class="post-metadata">

### Author: ![nevar](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/n/c4cdca/32.png) [@nevar](https://www.finalbuilder.com/forums/u/nevar)
#### Post date: [October 30, 2013, 11:58am UTC](https://www.finalbuilder.com/forums/t/psexec-program-interacts-with-remote-computers-desktop-screen/2213/2 "2013-10-30T11:58:20Z")

</div>

Hi Davestiff,   
  
 The typical reason for powershell not running scripts which are directed at another machine is due to permissions issues. One way to solve this is to a permission session in the script itself. These sessions get the correct permissions for the machine in question then run the commands required.   
  
 When using PSExec if interaction with the desktop is turned on then all output is written there. This means Finalbuilder has nothing to show in its logs. This is another reason as to why the powershell permission session is typically a good option. The script is running locally and calling at certain points to the other machine.

---

<div class="post-metadata">

### Author: ![davestiff](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/d/f08c70/32.png) [@davestiff](https://www.finalbuilder.com/forums/u/davestiff)
#### Post date: [October 31, 2013, 2:21am UTC](https://www.finalbuilder.com/forums/t/psexec-program-interacts-with-remote-computers-desktop-screen/2213/3 "2013-10-31T02:21:27Z")

</div>

Thanks!

I Google'd around a bit and found a workaround.

I remove the -i option for the PSEXEC Action in FinalBuilder and then, in the batch file that calls PowerShell, add '

e.g.

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe AddRemoveGACAssembly.ps1 add C:\Filename.dll&nbsp; \< NULL

This allows PowerShell to run and FinalBuilder to log the output.

Thanks,  
Dave