We have used some DCMs where we use Powershell scripts and yeah it only affects the SCCM client...
We also found that there is a bug that they fixed in SCCM2012 R2 CU2, to do with Signed scripts.. So if you are SCCM2012 R2 make sure your on CU2 (and that the sccm clients are upgraded on the machines as well) if you are going to run Signed Scripts. MAGNUS TVETEN SERVER SUPPORT ENGINEER CO CITRIX/SERVER Insurance Australia Group Limited Lvl 1, 23 Lakeside Drive, Burwood Burwood East VIC 3151 Australia T +61 3 8804 3226 M +61 411 010 460 E [email protected] www.iag.com.au PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Wednesday, 26 November 2014 10:43 AM To: [email protected] Subject: RE: [mssms] Client Settings: Powershell Great information--thank you very much! ________________________________ From: Hatem Mohamed<mailto:[email protected]> Sent: 11/25/2014 5:13 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Client Settings: Powershell >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-failed-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. _______________________________________________________________________________________ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. _______________________________________________________________________________________
