>From what I've read it only applies to ConfigMgr and has been confirmed also outside of TechNet documentation.
>From the TechNet description of the client setting: "Configure how Configuration Manager clients can run Windows PowerShell scripts. These scripts are often used for detection in configuration items for compliance settings, but can also be sent in a deployment as a standard script." Also, the TechNet documentation states the "All Signed" setting: "All Signed (System Center 2012 R2 Configuration Manager and System Center 2012 Configuration Manager SP1 only): The Configuration Manager client runs scripts only if they are signed by a trusted publisher. This restriction applies independently from the current Windows PowerShell configuration on the client computer." Also, this helpful article confirmed the same. <http://www.petervanderwoude.nl/post/deployment-of-configuration-baseline-fa iled-with-error-script-is-not-signed-in-configmgr-2012/> http://www.petervanderwoude.nl/post/deployment-of-configuration-baseline-fai led-with-error-script-is-not-signed-in-configmgr-2012/ From: [email protected] [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Tuesday, November 25, 2014 5:46 PM To: [email protected] Subject: [mssms] Client Settings: Powershell Does the Powershell Execution setting in Client Settings affect only packages executed through SCCM? Or does it affect the machine as a whole? I've got mine set to AllSigned and am wondering if that is interfering with a PS script being ran outside of an SCCM package.
