Tips for Configuring PowerShell Policies with ControlUp

One user asks for advice on dealing with restricted PowerShell Execution Policies, specifically at a customer who has set MachinePolicy to RemoteSigned, and asks for any general advisories on configuring policies in combination with ControlUp. Another user comments, saying that this shouldn’t affect the execution of the script, and suggests trying an unrestricted policy instead. They also mention that signing the scripts is an option.

Read the entire ‘Tips for Configuring PowerShell Policies with ControlUp’ thread below:

I have to deal with restricted PowerShell Execution Policies at a customer, which are set as following:

MachinePolicy -> RemoteSigned / all other undefined

has anyone experienced problems while having this set?

I wanted to configure automated toast messages, but those seem to fail if the policy is set. Once I remove the policy it works.

So I was wondering is there any general advisory on configuring powershell policies in combination with controlup?

I’m not sure this has to do with the execution policy. The execution policy controls whether the script is executed at all. Not what happens when the script is executing.

This is literally the only thing we have changed to make the script work ¯_(ツ)_/¯

Generally speaking I think we expect unrestricted. RemoteSigned would block all scripts since none of them are signed.

You can sign the scripts if you want to do that though.

Continue reading and comment on the thread ‘Tips for Configuring PowerShell Policies with ControlUp’.  Not a member? Join Here!