Key Points
Introduction: Explains common scenarios where patches must be declined only for selected systems and the risks of global patch blocking.
How Patch Manager Plus handles patch exclusion: Describes how patch exclusion allows administrators to decline patches at a system or group level without affecting the entire environment.
Quick Setup: Shows how to decline patches for specific systems using patch exclusion.
In real world environments, not every patch can be safely applied to all systems at the same time. Certain servers, business critical devices, or systems running sensitive applications may require extended testing or temporary deferral of specific patches. Declining patches only for these systems prevents unintended impact while still allowing the same patches to be deployed to the rest of the organization.
Patch Manager Plus handles system specific patch decline through patch exclusion. Using this approach, patches or applications can be excluded for selected computer groups. When a patch is excluded for a group, it is not considered missing for the systems in that group and is not deployed to them, including during automated patch deployments.
This allows administrators to maintain accurate patch status and compliance views while controlling patch rollout for sensitive systems independently from the rest of the environment.
Use the steps below to exclude selected patches so they are not deployed to specific systems.
Once excluded, the declined patches remain available for deployment to other systems that are not part of the selected groups.
More details on patch exclusion behavior are available here: Exclude Patches and Applications.