Getting Script is not signed for Configuration Manager Compliance Settings

Getting Script is not signed for Configuration Manager Compliance Settings. When using the PowerShell feature in Compliance Settings to run a script, client may return errors with a description of “Script is not signed“. Below is an example of a baseline deployment status where clients are returning errors.

Work-Around (not change Windows settings)

This is due to the current execution policy for PowerShell on client machines. To allow SCCM clients to run PowerShell scripts, modify client settings to Bypass the signed requirement.

1. Open SCCM Console, click “Administration” and go to “Client Settings“;

2. Select settings and click “Properties” in upper menu or Right Mouse Button click and select “Properties“;

3. Go to “Computer Agent“;

4. Scroll down and find option “PowerShell execution policy” – set “Bypass” and click “OK“;

You might also like

Leave a Reply

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More