Some users suggested using ssh as a workaround for issues with permissions for running scripts on monitors or for more centralized management. Although it may require a "double hop" process, it can be effective. Python was also mentioned as a possible tool for opening an ssh session that opens Powershell. The advantage of ssh is that it allows for redirecting error and std_out streams. In theory, a similar approach using psexec could work but has not been successful for some users.
Read the entire ‘Troubleshooting Permissions for Running Scripts on ControlUp Monitors’ thread below:
for those who have issues getting permissions to run scripts on monitors or want it more centrally managed? Try to get permission to install ssh on the monitors and use that. I have been using it for a while now, the only thing is that you need to double hop: open a powershell sessions and use that to start an authenticated powershell session.
in qa we use python to run these things so I use python to open an ssh session that opens powershell that opens powershell 😄
the biggest challenge is what to escape and when
in theory the double hop might also be possible using psexec but I never managed to get that running. The advantage of ssh is that you can redirect err and std_out streams to get the atcual response which wont work with psexec
Continue reading and comment on the thread ‘Troubleshooting Permissions for Running Scripts on ControlUp Monitors’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI, ControlUp Scripts & Triggers