There was an issue with the installation of the SecureDX agent due to an unsigned PowerShell script. The customer did not want to change the ExecutionPolicy and the team was unable to find any documentation on the topic. The agent is installed through a script added to the edge dx script list, which will not work if blocked.
Read the entire ‘Troubleshooting SecureDX Agent Installation’ thread below:
SecureDX agent install fails because of unsigned PowerShell script!?
Customer is not willing to change ExecutionPolicy for a good reason 🙂
Did I overlook something?
The agent is installed through a script (which is added to the edge dx script list)
So if that script gets blocked, no install
i thought we were going to document something on this topic, but can’t find it
Continue reading and comment on the thread ‘Troubleshooting SecureDX Agent Installation’. Not a member? Join Here!
Categories: All Archives, ControlUp for Compliance, ControlUp for Desktops, ControlUp Scripts & Triggers