Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Patch Manager Administration Console > Managing Software Package Rulesets

Managing Software Package Rulesets

Updated July 8th, 2016

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.

For additional information about these rulesets, see the following articles:

Note: The Rule Editor is the same regardless of the type of rule. Furthermore, it is the same whether you launch it from the Package Wizard or the New Rule task in the Administration and Reporting > Software Publishing > Rules view in the Patch Manager console.

Prerequisite Ruleset

Common prerequisite rules define the prerequisite Windows version, language, and processor architecture for the target computers. For example:

To add a rule to include only workstations running Windows XP SP 3 or later:

  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:

To add a rule to check whether the Firefox version is less than 10.0:

  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:

To add a rule to check whether the Firefox version is less than 10.0:

  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 is checking for installed versions prior to the update installer's version, and the installed rule is checking for the existence of the same version. Thus, the two rulesets combined determine whether or not the update is needed.

Last modified

Tags

Classifications

Public