We are just getting started standing up our K1000 in our enterprise and I had a question about what everyone is doing for Microsoft Patch Labels, specifically non-OS patches.

Originally I had a smart label setup to all Critical, Active patches where the vendor = Microsoft for a specific OS (i.e. Win7sp1x64) to capture all MS crits. I created a label such as this for each OS but this leads to very bloated labels. So now I'm trying out breaking the patch labels down a bit further so setup a configuration that has just OS crits in one label, Office in another, etc.

My question is how to best capture and separate these non-OS Microsoft patches in a separate labels but ensure that I'm not missing anything important. Plus, to make matters worse, it seems that the office 2010 patches do not all include "Microsoft Office" in the title so how do you, for example, create a patch label that only includes Microsoft Office 2010 patches.

Any tips or tricks would be appreciated.

Thanks in advance!
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer

Here is what i usually use for my App patches:
Vendor contains "Your Vendor"
Impact = Critical
Status = "Active"
That leaves one field to mess with depending on the situation.
Answered 03/24/2012 by: dchristian
Red Belt

  • Do you do this also for the Application Microsoft Patches? I basically have that setup now for MS but it leads to these extremely large labels that I would like to avoid.
Please log in to comment



Actually, you can have more than just one field left. You can create a label name ("Vendor-Crit-Active"). Then, you can create a whole new label in which the first criteria is LABEL NAMES contains "Vendor-Crit-Active", and then add the other criteria that you want, such as Title contains Office and Version contains 12, or whatever.

This trick works for any Smart Label. If you need more criteria for the label that you want to build, just create an interim label for use in the building of the final label that you want.

Answered 07/12/2012 by: polandll
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.