I know this question is answered but you can also create a manual label called "blocked" and add it to the patches that are causing you an issue. Then when you build your smart label out , include a line that states " Label Name" "Does not contain" "Blocked".

This way:

1. no patches with that label get added to your production smart label.

2. you can easily search for the ones that were blocked, where as making them inactive makes finding them touch without searches by their KB number, one at a time.

3. if you need to apply it, you can just remove the "blocked" label and it will get deployed out on the next schedule, if the patch is still active.

Share

This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ