Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Patch Manager > Unable to deploy revised publishing package with SolarWinds customization

Unable to deploy revised publishing package with SolarWinds customization

Updated: July 4, 2017

Overview

This article describes an issue where edited updates are not applied to clients when a package is edited or republished.

Environment

  • All Patch Manager versions
  • All Windows Server Update Services (WSUS) versions

Cause

The Windows Update Agent caches updated binaries and metadata. When the new revision of an update was available, only the metadata was updated and this caused the update installation to fail because the checksum was incorrect.

Resolution

When editing the package metadata (title, description, detection rules, and so on), edit the previously published package and republish it.

Note: The package revision number will change to a later version.

If there is a change in the binaries (installer and package content), publish the package as new a package. When making a change to a binary in a package:

  1. Create a duplicate of the previously published package.
    Note: The duplicate package name will not be visible to end users.
  2. Edit the binary content of the duplicated package.
  3. Set the previously published package in WSUS to Expire.
  4. Publish the new update.

 

Last modified

Tags

Classifications

Public