Currently, you would need to added updates to an Exceptions Patch Group to ignore them in patch scans. It would be a good idea to submit a feature request, perhaps to be able to keyword ignore patches.
Down in the Patch library, right click on the patch library group, select add objects > Software Category. Name it whatever you choose. Make it a Dynamic group. In the LDAP filters, under the Software Object Type drop down, select the Object area. Double click Unique ID. Make it = *QP*
This will filter out all of the Quality Preview patches into this Software Category.
Now go back to patch library and right click on it again. Select your patch management menu item (Patchlink, APM, etc) and then select Manage Patch Management Rules. Create a new rule, and set the evaluation order to 1. In the properties of the rule, set the "Included Patch Categories" to whatever you named your dynamic group. Under the Patch Rollout Rule area, for Action, set it to None.
This will make sure that DSM does not download, or assign out the Quality Preview patches.
May not be feasible in your environment, but I just exclude any "non-security patch" with a vendor severity of "unassigned" from my scan template. All the QPs are lumped in those categories.
I am here looking for an answer to this question as well, could you elaborate a bit on what other patches might be categorized with "unassigned severity" ? You say this resolution may not pertain to all environments, I am curious what other "patches" could be excluded by implementing this.
I have machines failing the Monthly roll up and then also the Preview because it seems to me that the Security only patch gets applies first (successfully) and certain components of it I figure must interfere with the full packages. If I could get the previews out of my way id have a lot easier time sorting out the conflicts between security only and monthly roll ups.
Hey awright, you could browse through the patches in that category by editing a patch group and searching for patches by navigating to non-security patches and selecting "unassigned" under it
The important security updates are never categorized with no severity, let alone as a "non-security" update, so at least in my environment it's not a big deal.
ryany yes I have been finding that and will likely implement this. Thank you for the work around. Now incidentally I did actually contact support about this as well yesterday, the tech told me what we already know, but he also pointed out that others had brought this up ( no surprise there! lol ) and it turns out there is actually a feature request in the ideas board which is currently under review you can find it 3rd or 4th item down on this page : https://ivantisecurity.uservoice.com/forums/602383-patch-for-windows this feature would allow us to filter by name and I can think of a million uses We need to all go vote on this. if you are here reading this, please go to this link and vote yes for this feature.