Are you sure you checked the box on your rule to run the remediation script when the setting is noncompliant? It's easy to miss.
[image: Inline image 1] On Thu, Jul 10, 2014 at 9:56 AM, Trevor Sullivan <[email protected]> wrote: > 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 > > > >
