Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Patch Manager > Manage software package rulesets

Manage software package rulesets

Created by Leif Amland, last modified by MindTouch on Jun 23, 2016

Views: 46 Votes: 0 Revisions: 5

Overview

WSUS uses software publishing rules to evaluate if a package is appropriate to be deployed to a specific client and if the package is applicable or already installed. The following sections describe each type of software publishing ruleset and provide a corresponding example.

Environment

Patch Manager 2.1.0.1087

Steps

Prerequisite Ruleset

Common prerequisite rules define the prerequisite Windows version, language, and processor architecture for the target computers. For example, you can add a rule to include only workstations running Windows XP SP 3 or later by performing the following steps:

  1. On the Rule Editor window, select Create Basic Rule.
  2. In the Rule Type field, select Windows Version.
  3. In the Comparison field, select Greater Than or Equal To.
  4. In the Major Version field, enter or select 5.
  5. In the Minor Version field, enter or select 1.
  6. In the SP Major Version field, enter or select 3.
  7. In the Product Type field, select Workstation.

The following are the current Windows operating system version numbers in majorVersion.minorVersion.SPMajorVersion format:

  • 5.1.3: Windows XP Service Pack 3
  • 5.2.2: Windows Server 2003 Service Pack 2
  • 6.0.2: Windows Vista Service Pack 2 and Windows Server 2008 Service Pack 2
  • 6.1.1: Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1

Applicability Ruleset

Common applicability rules check to see whether certain registry keys or values exist on the target computer. Generally, applicability ruleset works hand-in-hand with the installed ruleset to define whether or not a target computer requires the update. For example, you can add a rule to check whether the Firefox version is less than 10.0 by performing the following steps:

  1. On the Rule Editor window, select Create Basic Rule.
  2. In the Rule Type field, select >File Version with Registry Value.
  3. In the Registry Key field, enter HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\firefox.exe
  4. In the Registry Value field, enter Path, and then select Use 32-bit registry.
  5. In the Sub-path> field, enter firefox.exe.
  6. In the Comparison field, select Less Than.
  7. In the Version field, enter 10.0.0.441.

Installed Ruleset

Common installed rules check to see whether certain registry keys or values exist on the target computer. Generally, installed ruleset works hand-in-hand with the applicability ruleset to define whether or not a target computer requires the update. For example, you can add a rule to check whether the Firefox version is less than 10.0 by performing the following steps:

  1. On the Rule Editor window, select Create Basic Rule.
  2. In the Rule Type field, select File Version with Registry Value.
  3. In the Registry Key field, enter HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\firefox.exe
  4. In the Registry Value field, enter Path, and then select Use 32-bit registry.
  5. In the Sub-path field, enter firefox.exe.
  6. In the Comparison field, select Equal To.
  7. In the Version field, enter 10.0.0.441.

 

Note: The only difference between the applicability and installed rules in these examples is that the applicability rule checks for installed versions prior to the update installer's version, while the installed rule checks for the existence of the same version. Combining the two rulesets can determine whether or not the update is needed.

 

Last modified
01:06, 23 Jun 2016

Tags

Classifications

Public