Share This Post

ConfigMgr 2012 – Excluding Updates

A really common example that we find is that people want to exclude updates from being deployed, for example Internet Explorer 9 if the company is not quite ready to deploy it. There are a few ways to exclude the update, neither one is ideal, but you can get the expected behavior more or less.

The first way to exclude updates is to put them into a folder, then they will not show up in the primary searches.

image

This works for searches, however any Automatic Deployment Rules (ADR) will still find the updates. So the way to avoid an ADR from finding them is to set the Custom Severity on the update and then filter that severity out of your ADR.

image

So lets set the update(s) we want to exclude to “Low”.

image

In our ADR, add the Custom Severity field and set it to “None”. This will exclude any update(s) that are set to “Low”.

image

Share This Post

I am a Microsoft MVP for System Center Configuration Manager and owner of Nackers Consulting Services, LLC. I focus primarily on System Center Configuration Manager and the Microsoft Deployment Toolkit. In addition to helping clients leverage the technologies they use, I enjoy spending a lot of time on the forums and email lists helping answer questions and just seeing what people are doing with the deployment technologies available to them. I have spoken at Microsoft Management Summit on ConfigMgr/MDT integration and I have spoken at user groups around the country. If you have any questions, please feel free to contact me, I am always willing to help.

Leave a Reply