I created a configuration baseline for a critical update, have a monitor action deployed against the baseline, and created 4 collections against the deployment: compliant, error, non-compliant, unknown.  So far so good....

I then created a fresh deployment against the non-compliant collection to push the update and when I run report ' compliance 6 - -specific software update states (secondary)' for the updates against the non compliant collection I get the rather odd 'update is installed'=2.

How is the non-compliant collection meant to be updated by the baseline monitor deployment?  If I update the collection manually it makes no changes to membership

Thanks

David

Do you have a recurring schedule on the deployment of the CM baseline? You have to rerun the baseline against the machines to get an updated status back. Once the new result is returned your collection will update based on the new baseline result.

• Edited by mdkelley 14 hours 3 minutes ago

Do you have a recurring schedule on the deployment of the CM baseline? You have to rerun the baseline against the machines to get an updated status back. Once the new result is returned your collection will update based on the new baseline result.

• Edited by mdkelley Monday, March 30, 2015 5:41 PM

The configuration baseline deployment is set to run as per the default simple schedule of every 7 days - not sure how to check if it is running though

Hi,

You could check the baselines status in Configurations Tab on the client.

Best Regards,

Joyce