Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Publishing packages error: Verification of Signature failed for file

Publishing packages error: Verification of Signature failed for file

Updated January 16, 2018

Overview

When you publish third-party updates to your WSUS server, the following error displays: 

Verification of Signature failed for file:

Environment

  • All Patch Manager versions
  • All WSUS versions

Resolution

Solution 1: Run the Provision WSUS Server for Publishing Wizard

This procedure will create or distribute the certificate needed for publishing.

  1. Log in to the Patch Manager Administrator Console as an administrator.
  2. Expand Administration and Reporting and select Software Publishing.
  3. In the Actions pane, click Server Publishing Setup Wizard.
  4. In the wizard, click the WSUS Server drop-down menu and select your WSUS server.
    wizard.png
  5. Complete the remaining fields, and click Next.
  6. Compete the wizard. 

Verification

Run Microsoft MMC and add the snap-in for certificates for the computer account on the WSUS and the Patch Manager servers.
The certificates should be in the following:

  • Trusted Publishers store
  • Trusted Root store

On the WSUS server, the certificates should be in the WSUS certificate store.

Solution 2

If the steps in Solution 1 does not help:

  1. Backup the existing WSUS cert from the MMC snapin.
  2. Delete the WSUS cert from Trusted Root and Trusted Publishers store(s).
  3. Follow steps in Solution 1 and then verify.
  4. Make sure there are no duplicate or old certificates in the Trusted Publishers and Trusted Root and WSUS store.

 

Last modified

Tags

Classifications

Public