‎03-31-2020 01:15 PM
Solved! Go to Solution.
‎04-03-2020 11:08 AM
‎04-03-2020 11:08 AM
‎10-08-2021 03:36 PM
Jeffy wrote:
The problem wasn't bad command or unsupported environment, but the problem was with the numbers of remote connections. Powershell only allows one and that's already taken up by lansweeper. So the solution is:
powershell.exe -executionpolicy bypass -file \\computer\PackageShare$\Installers\Scripts\Script.ps1 (Setting action command)
‎03-31-2020 09:29 PM
‎03-31-2020 08:52 PM
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now