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 Release Notes

Patch Manager 2.1 Release Notes

Created by Meryl Wilk, last modified by MindTouch on Jun 23, 2016

Views: 20 Votes: 0 Revisions: 9

Updated 04/07/2015

These release notes provide additional guidance for SolarWinds Patch Manager  2.1.

New Features and Improvements

SolarWinds Patch Manager  2.1 includes the following new features and improvements:

  • Auto-publishing Third-Party Updates

    Introduced Automated Third-Party Patching and Publishing, which automates the publishing of third-party updates to WSUS servers in the same way that Microsoft updates distribution points. This reduces the amount of manual configuration and the time required to publish third-party updates by allowing the local Microsoft WSUS servers to automatically download third-party patch content on a scheduled basis and publish them automatically. An additional option can be set to automatically approve certain patches based on criteria (typically severity) and provide a scope for automatic approval.

  • Logging Enhancement

    Enhanced the log collection functionality of Patch Manager by centralizing and bundling logs, which assist in troubleshooting. By extending the existing Orion diagnostic tool, administrators can now collect relevant logs and review them or submit to support. This eliminates having to browse through individual directories to gather separate logs.

  • Windows 2012 R2 and Windows 8.1 Support

    Added Windows 2012 R2 and Windows 8.1 operating system as options when selecting computer properties.

  • Notification Bar Enhancement

    Added a banner notification in the Patch Manager Web Console which notifies administrators when new patches are available.

  • Additional Computer Group Scoping Options

    Added three grouping options to allow management and task targeting at subnet, AD organizational unit, and site levels. This provides granular device grouping options depending on the task at hand when creating computer groupings.

Fixed Issues

Issue Case Number
Uninstalling updates using Package Boot Editor with a non-restart option now works correctly. 715023
Scheduled report now works correctly. 699371
Running inventory on a server no longer gives the Unhandled exception InventoryUploader error. 699128, 664049
Catalog downloads through a proxy server now works correctly. 676452
The WSUS Signing Certificate Management utility now works correctly with Windows 2012. 668461
Fixed an issue in the package creation wizard where setting the path to None could result in a File Not Found error. 659475, 577521
Fixed an issue that always showed Java packages as New. 654875
Creating a package no longer fails with the error "Index (zero based) must be greater than or equal to zero and less than the size of the argument list error." 604789
The Web Console no longer shows unknown packages in the Needed Updates. 596732, 503442
Fixed an issue where servers running Windows 2008 or later would incorrectly show Windows Update History warnings in Managed Computers. 591097
Update files and language now work correctly. 571702
Third-party updates no longer show revised and expired packages as new or synchronize every time. 567179
WMI Provider provisioning through the Check and Manage utility now works correctly. 538664
Synchronizing updates now correctly completes the "Patch Manager Package Management" task. 500945
The Computers Needing Updates list no longer contains computers that do not need updates. 492896

Open Issues

Issue Case Number
If you deploy an Acrobat Reader package using SCCM, it may be reported as Failed even though the deployment was successful. 681182
The license count for Managed Computers may be incorrect. 635356
The Patch Manager console may fail to connect to the Application server. 495471

Upgrading to This Version

This version is capable of upgrading Patch Manager from any previous version. However, SolarWinds recommends the following upgrade paths based on the current installed version of Patch Manager:

Recommended upgrade path for Patch Manager Administration Console:

Installed Version Recommended Upgrade Path
1.80 => 2.1
1.85 => 2.1
2.0 => 2.1

Recommended upgrade path for Patch Manager Web Console:

Installed Web Console Version Recommended Upgrade Path
1.80 => 2.0 => 2.1
1.85 => 2.0 => 2.1
2.0 => 2.1

IMPORTANT NOTES:

  • Patch Manager does not support direct upgrade from versions earlier than 1.80. For versions earlier than 1.80, upgrade to Patch Manager 2.0 first and then to Patch Manager 2.1
  • If you have not already installed .NET Framework 4.0 on your systems running Patch Manager, the 1.85 and later upgrade installs it. If the upgrade installs .NET Framework 4.0, the upgrade requires a reboot.
  • As of version 1.85, SCCM 2012 SP1 is supported.

To upgrade to Patch Manager version 2.1:

  1. Download the 2.0 and 2.1 upgrade packages from the SolarWinds Customer Portal.
  2. Upgrade all of your Patch Manager servers and consoles to version 2.0.
  3. After all of your Patch Manager systems are on version 2.0, upgrade your Primary Application Server (PAS) to version 2.1.

If you have additional Patch Manager servers and/or consoles in your publishing environment, upgrade all downstream servers and consoles to version 2.1 after you upgrade your PAS.

 

IMPORTANT NOTE: If you have not already applied Microsoft KB2720211 or KB2734608 to your WSUS and Patch Manager systems, the upgrade to version 2.1 automatically applies KB2734608 to the local WSUS console. To ensure local publishing continues to work in your environment, apply that update to all Patch Manager and WSUS systems, and then regenerate a new 2048-bit publishing certificate.

Upgrading from Patch Manager version 1.80 or later

  1. Download the upgrade packages from SolarWinds Customer Portal.
  2. Upgrade all of your Patch Manager servers and consoles to version 2.1.

Upgrading from Patch Manager versions earlier than 1.80

Patch Manager does not support direct upgrade from versions earlier than 1.80. You should upgrade to Patch Manager 2.0 first and then to Patch Manager 2.1.

NOTE: Upgrading to the current version from a version earlier than 1.72 requires the following:

  • A Windows user account that has Administrator rights on the Patch Manager server.
  • A Patch Manager console account in the Enterprise Administrator security role in Patch Manager.

End of Support Announcements

The following address current or forthcoming changes to the SolarWinds support policy for Patch Manager.

  • Patch Manager v1.73 and earlier

    All versions of Patch Manager prior to 1.73 have entered the End-Of-Life cycle. View the SolarWinds EOL Policy online.

  • SCCM 2007 Patch Manager Snap-in

    For version 1.85 (and later), you must load the CLR4.0 runtime to add the Patch Manager MMC snap-in as a sub-node of the SCCM 2007 console. If you do not change the runtime, the Patch Manager snap-in runs as a separate console on SCCM 2007. 

  • Windows 2000

    As of version 1.80, SolarWinds no longer supports Windows 2000 clients in Patch Manager. This change is due to changes in Microsoft's support for Windows 2000 clients in WSUS. Microsoft does not provide the current Windows Update Agent for Windows 2000 clients, thus those clients are unable to communicate with the latest versions of WSUS.

  • Windows XP

    As of version 1.85 SR2, SolarWinds no longer supports the installation of Patch Manager on Windows XP. However, the patching of Windows XP machines using SolarWinds Patch Manager continues to be fully supported.

Legal

Copyright © 2015 SolarWinds Worldwide, LLC.  All rights reserved worldwide.

No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds.  All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SOLARWINDS and SOLARWINDS & Design marks are the exclusive property of SolarWinds Worldwide, LLC and its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries.  All other SolarWinds trademarks, service marks, and logos may be common law marks, registered or pending registration in the United States or in other countries.  All other trademarks mentioned herein are used for identification purposes only and may be or are trademarks or registered trademarks of their respective companies.

Last modified
01:07, 23 Jun 2016

Tags

Classifications

Public