Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Patch Manager Administration Console > Create software packages

Create software packages

Updated November 30, 2017

The Package Wizard is a guided interface for creating or editing a package definition. A package definition is an XML file that defines the attributes and behavior of an update package. Use the Package Wizard to view or define the following:

  • Package metadata
  • Prerequisite rules
  • Update source
  • Applicability rules
  • Installed rules

SolarWinds supports packages created and provided by the company. SolarWinds does not provide support for custom packages created by third-party sources. See the Patch Manager Product Forum on THWACK for help with custom packages.

Open the Package Wizard

  1. Log in to the Patch Manager Console.
  2. In the navigation pane, expand Administration and Reporting > Software Publishing. 

Create a new package

  1. Select any container in the Software Publishing node.
  2. In the Actions pane, click New Package. 

View the package details

  1. Select the container that contains the package you want to view.
  2. In the center pane, select the package you want to view.
  3. In the Actions pane, click Edit.

When you are finished, complete the Package Wizard.

Complete the Package Wizard

The following procedure describes each step of the Package Wizard. For detailed information about adding prerequisite, applicability, and installed rules in the wizard, see Managing Software Package Rulesets.

To complete the Package Wizard:

  1. On the Enter or modify the package information page, enter the package's metadata.
    See Defining Package Metadata for details.
  2. On the Prerequisite Rules screen, add or modify rules to define whether a target computer should evaluate the update further based on its hardware or software attributes, and then click Next. 
    See Prerequisite Ruleset for details..
  3. On the Select Package page, specify the source of the package contents, and then click Next. 
    See Defining the Package Source for details. 
  4. On the Applicability Rules page, add or modify rules to define whether the update applies to the target computers, and then click Next. 
    See Applicability Ruleset for details. 
  5. On the Installed Rules page, add or modify rules to define how to determine whether a target computer already has the update installed, and then click Next. 
    See Installed Ruleset for details. 
  6. On the Summary page, verify your settings for the package, and then click Next to save the new or modified package.

Define the package metadata

The following table describes the files on the Enter or modify the package information page located in the Package Wizard.

Field Description
Package Title (required) The text string displayed in the update listing of the administrative console and the header of the update details. Enter a string that is concise, descriptive, and 80 characters or less. 
Description (required) A longer length text field used to provide additional information on the update, particularly its purpose.
Classification (required) A pre-defined value that describes the type of update. The options in this menu are defined by Microsoft.
Bulletin ID The ID assigned to a Microsoft Security Response Center Security Bulletin. This field can also hold a similar value for security updates published by other vendors. For non-security updates this value would normally be left empty. 
Vendor (required) The software company responsible for the product to which the update applies. This field allows you to sort and filter updates in the administrative console. Enter a company, or select one from the menu. For optimal performance, keep this list as short as possible. 
Product (required) The vendor’s marketing name for the entity to which the update applies. This field allows you to sort and filter updates in the administrative console. Enter a product name, or select one from the menu. For optimal performance, keep this list as short as possible.
Article ID The ID assigned to a Microsoft Knowledge Base article. This field can also hold a similar value for updates published by other vendors.
CVE ID The ID assigned to the National Cyber Security Division's (NCSD) Common Vulnerability and Exposures (CVE) article that describes the issue the update is intended to resolve.
Severity The rating assigned to a security update by the Microsoft Security Response Center. This field is required for any update classified as a Security Update.
Support URL The URL for support information for the update, such as its applicability, deployment considerations, or the publicly available download location. Enter the URL for the vendor’s authoritative source for information about the update.
More Info URL The URL for additional information about the update, possibly not available at the time of the original update publication. 
Impact (required) A designation that dictates how target computers will handle the update. Select one of the following options: 
  • Normal. Any update that does not fit in either of the following categories. 
  • Minor. An update that does not require a system or service restart to be applied. Minor updates use the Windows Update Agent setting “Allow automatic updates immediate installation” to determine if the update can be installed immediately, or must wait until a directed or scheduled event. 
  • Requires exclusive handling. An update that must be installed individually, outside of a batch of other updates. Typically this includes updates such as operating system service packs, .NET Framework service packs and redistributables, and updates to the Component-Based Servicing Stack. 
  • Reboot Behavior (required). How the target computer should behave after the update is installed. Select Can request reboot if a reboot may be required, but is not absolutely necessary in all installation scenarios. Otherwise, select Never reboots or Always requires reboot according to the vendor's specifications. 

Define the package source

The following table describes the in on the Select Package page of the Package Wizard.

Field Description
Type The package file extension. Select whether the package is EXE, MSI, or MSP based.
I do not have the package content Specifies the URL for a web-based or FTP-based download location. Enter the direct URL for the installer in the Download URL  field. This field does not accept forwarding links.
I already have the content for the package locally on my network Specifies the name and location of content you have already downloaded. Enter the package's filename in the Package  field, and its web-based, FTP-based, or UNC file path in the Download URL field.
Use the Package Boot Helper program when performing installation of the software

Activates the Package Boot Editor button so you can define additional files and behavior to accompany the installer. 

See Use PackageBoot for details.

Include additional files with the package Activates the Package Content Editor button so you can specify additional files to accompany the installer.
Binary Language The language required by the update. If the update is not language-specific, select None.
Success Return Codes The return code(s) for the package. Separate multiple codes with commas.
Success Pending Reboot Codes The reboot code(s) for the package. Separate multiple codes with commas.
Command Line (silent install) Additional arguments to support the unattended installation.

Using PackageBoot

PackageBoot is a utility designed to assist in the successful installation of certain updates by orchestrating specific actions before and after applying an update. Use PackageBoot to verify that any files that will be overwritten during the installation process are not currently locked. 

For example, locked files can sometimes cause issues with silent installations and require reboots. Furthermore, use PackageBoot to stop and start services before and after installation, execute programs (MSI or EXE) before or after installation, and terminate processes before installation.

The Package Boot Editor  creates two files to include in the update package: 

  • PackageBoot.EXE
  • PackageBoot.XML

Both files are published with the installer to the WSUS server and then downloaded to the target computer. The PackageBoot.XML file provides the specifications for the activities and tasks that the Windows Update Agent will perform.

Complete the Package Boot Editor

  1. Open the Package Boot Editor from the Select Package  screen of the Package Wizard.
  2. In the Before applying package  section, select the actions you want to run prior to installing the update. Common examples include stopping a service, running a program, or terminating a process.
  3. In the After applying package  section, select the actions you want to run after installing the update. Common examples include running a program or starting a service.
  4. After you select a task in these sections, specify the action details in the right pane.
  5. Click Save to save the PackageBoot.XML configuration file.
  6. Close the Package Boot Editor.

The following table describes additional options in the Package Boot Editor screen.

Option Description
Import Import a PackageBoot.XML file from a local or network location.
View XML View the PackageBoot.XML configuration file the editor will generate.
Add Action Select an action to add to the active section of the editor.
Delete Delete the selected action.
Duplicate Duplicate the selected action.
Move Up Move the selected action one position higher in regard to its processing order.
Move Down Move the selected action one position lower in regard to its processing order.

 

Last modified

Tags

Classifications

Public