How to filter persistent undesired patches from the patch deployment schedules by using smart labels (4262799)

An example on how to use patch smart labels to exclude/block current and future patches from installing into the client devices. 

Some reasons for this is if you want to exclude certain types of patches being installed due to unique devices such as servers.

Sometimes, given the subscription settings on the Patch module, some undesired patches might get downloaded and detected to be needed by the client machines, however the customer might not want to have this patch installed due to multiple reasons such as, the patch gets installed via windows updates, the patch conflicts with other patches or software already installed on the machine, the patch is too big and the network can’t handle it, etc.

When this is a onetime event the patch can be easily excluded by inactivating it on the patch catalog; nonetheless, there are patches that come out every month, have the same name, are added to the patch catalog as a new patch and hence depending on the subscription settings are found active but might be permanently undesired by the customer.