Getting “Script is not signed” for Compliance Setting

Version: SCCM 2012 SP1 CU2

Problem

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.

CM12-Compliance1

Work-Around

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.

  • Open Administration -> Client Settings -> Default Client Settings (or whichever Custom Client Setting Policy preferred).
  • Right-click select Properties
  • Click on Computer Agent
  • Modify PowerShell execution policy

CM12-Compliance2