Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Create custom packages

Create custom packages

Table of contents

Updated June 12, 2017


Due to the uniqueness of each environment, SolarWinds Technical Support is only able to offer the best effort for all custom packages.


All Patch Manager versions


The following webinars describe rule sets and how to create a custom package:

The file you are converting into a package must be in .msp, .msi or .exe format. 


The Package Creation Using Patch Manager webinar assists you in creating a script that will be read or interpreted by the Windows Update Agent. When a package returns as Not Applicable, this indicates that the Windows Update Agent determined that this package does not belong to its system and should not be seen as an error.


The Windows Update Agent will try to read pre-requisites. Applicability and installed rules are as follows:

  • The final rule set results of the pre-requisites should return as TRUE (if left blank, the result will default to FALSE).
  • The final rule set results of the applicability should return as TRUE (if left blank the result will default to FALSE).
  • The final rule set results of the installed rules should return as FALSE (if left blank the result will default to TRUE).


Using this information, you can make virtually any package installation by simply putting a valid system architecture in the Pre-requisites and Applicability rules and put a rule that would return as negative on the Installed rule. A "wrong" architecture on the Installed Rules would work (for example only). You are not required to add a specific rule in each rule set, but you *must* have the rules and they have to return TRUE (for pre-req), TRUE (for Applicability), FALSE (for Installed Rules) as well as any command line options.


This example was copied from a Google package. You can also select another package with very loose rules like Google Chrome:

prerequisite rules

create basic rule



applicability rules

create basic rule 

Processor Architecture="x86"/>

when all of the following 

create basic rule 

Processor Architecture="x64"/>

Property of Google © 2017


To create the custom package:

  1. Right-click and click Duplicate.
  2. Refresh and edit the duplicate package.
  3. Change the information.
  4. On the content, browse and add your package. 

As stated earlier, the results are out of scope. However, this will help you create a package with extremely loose rules.

This example uses a system running Microsoft Windows XP system 32- or 64-bit and later. 


Any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified