View Single Post
Old 08-27-2015, 10:58 PM
kinook kinook is online now
Join Date: 03-06-2001
Location: Colorado
Posts: 5,758
This is fixed in the latest build (VisBuildPro.exe in Help | About after installing). There were two problems:

1) PowerShell didn't like the path to the temporary script specified as \\computer\c$\xyz.ps1 on the remote call -- this was changed to reference as C:\xyz.ps1 instead.

2) PowerShell doesn't exit when called remotely -- a 'None' option was added to the Input format field on the Options tab, which must be used for remote calls to PowerShell to avoid this (see here for details).

Also, you should be able to specify Remote Signed rather than Unrestricted for the Execution policy on the Options tab.
Reply With Quote