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 > Patch Manager 2.1.4 Administrator Guide > Using the Patch Manager Administration Console > Publishing Software Packages

Publishing Software Packages

 Updated July 8th, 2016

Use the Patch Manager Publishing Wizard to publish one or more packages to a WSUS server. When publishing packages, you have the option to publish any of the following:

  • Entire packages, which include all metadata and installers.
  • Metadata-only packages, which you can use to determine whether or not a package is installed or needed on target computers.
  • Revision-only packages, which update an existing package's metadata, but not its installation file.

Completing the Patch Manager Publishing Wizard

Complete the following procedure to publish packages to a WSUS server to be deployed to applicable clients.

The wizard in this procedure provides the following additional options:

Verify WSUS version compatibility and required signing certificate is distributed

Checks the versions and certificates throughout the publishing environment to verify publishing will be successful. WSUS requires that all components in the publishing environment are running the same WSUS version and have the same publishing certificate installed. We recommend you use this option to verify these requirements prior to large publishing jobs to avoid wasted publishing time.

Re-sign existing selected packages

Re-signs the selected packages with the current publishing certificate. Use this option when republishing packages that were previously signed with an earlier publishing certificate.

Delete package if it exists (select this if binaries have changed)

Replaces the existing binary files for the selected packages with new ones. Most often, you will accomplish this goal by publishing an entirely new package, but this option allows you to reuse an existing package definition.

Re-download packages that have already been downloaded

Downloads the binary content for all packages, even if the content is already on the SolarWinds Patch Manager server. Use this option to ensure the content you publish to the WSUS server is exactly the same as the content available from the vendor's update publishing site.

To publish packages to a WSUS server:

  1. Expand Administration and Reporting > Software Publishing, and then select the container that contains the package(s) you want to publish.
  2. In the Actions pane, click Publish Packages.
  3. On the Packages to Publish screen, select the WSUS server to which you want to publish the packages. Note: This wizard cannot publish packages to replica servers.
  4. Select one of the following options as your initial selection method:​
    • Publish selected packages to the WSUS server: Select this option to start with only the packages you selected before launching the wizard.
    • Publish all packages to the WSUS server: Select this option to start with all available packages selected. You can clear or modify these selections in the following step.
  5. In the pane that lists the available packages, select the check box next to the packages you want to publish. Clear the check box next to the packages you do not want to publish.
  6. In the Content column for each package you selected, specify whether you want to publish the Full, Metadata Only, or Revision Only version.
  7. Above the package selection pane, select any of the additional options described previously.
  8. Click Next.
  9. If you need to download any additional content:
    1. If any packages do not include direct download links, use Package Download Assistant to download and import the content. For additional information, see "Using Package Download Assistant".
    2. After the wizard finishes downloading the required content, select each of the packages you want to publish.
    3. Click Next.
  10. Review the publishing results, and then click Finish.

Using Package Download Assistant

Complete the Package Download Assistant wizard to publish packages for which vendors do not include direct download links. Common examples of such packages include the Adobe Flash Player and Sun Java Runtime Environment packages.

To complete the Package Download Assistant wizard:

  1. Prepare to publish the package(s) just like any other. For additional information, see "Completing the Patch Manager Publishing Wizard".
  2. On the Package Download Assistant window, select a package, and then double-click the link provided below the package list.
  3. On the vendor's download page, download the file or archive for the package you selected.
  4. Back on the Package Download Assistant window, complete any additional steps listed in the Package download description and instructions section. For example, extract the contents of the vendor's archive.
  5. Click Import Source.
  6. Browse to the folder that contains the downloaded file, and then click Open.

Note: The wizard pre-populates the Select the downloaded package file dialog with the necessary filename, so you do not need to select or specify a file during this step, just the folder.

  1. Repeat Steps 2-6 for any other packages listed in the wizard.
  2. Click OK.
  3. Complete the publishing wizard as you would for any other package.
Last modified
13:29, 24 Feb 2017

Tags

Classifications

Public