I don't know if you saw my thread from the other day, but I'm having the exact same issue. The discovery script works no problem, but the remediation script doesn't do anything and I can't tell if it's even trying to execute. I see no errors in the DCMAgent.log or the CIAgent.log
From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Thursday, July 10, 2014 10:56 AM To: [email protected] Subject: [mssms] Compliance Settings: Remediation Script is not executed Folks, In ConfigMgr 2012 R2, I created a Configuration Item per the following: * Baseline o Configuration Item ? Script Setting * Discovery Script --> Checks if a process is running (PowerShell) * Remediation Script --> Kicks off a process (PowerShell) * Compliance Rule --> Script returns at least one value I assigned the Baseline to a Collection, containing two test systems. Both test systems are validating the Configuration Item, and its Script Setting correctly, but the remediation script is not being executed. I have validated the following: * PowerShell Execution Policy is set to Bypass (via a custom Device Client Settings Package) * Discovery Script is being successfully executed * Compliance Rule is working correctly * Configuration Manager Control Panel applet shows Baseline as non-compliant, when process is not running * Baseline Deployment --> Checked the boxes for: o Remediate noncompliant rules when supported o Allow remediation outside the maintenance window Has anyone else seen this behavior? How do you ensure that remediation scripts are executed in Compliance Settings? Cheers, Trevor Sullivan Microsoft PowerShell MVP ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
