Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn More.

 

Home > Success Center > Patch Manager > Patch Manager 2.0 Release Notes

Patch Manager 2.0 Release Notes

Created by Abraham Toribio, last modified by Caroline Juszczak on Mar 30, 2017

Views: 14 Votes: 0 Revisions: 11

Updated 11/26/2013

These release notes provide additional guidance for SolarWinds Patch Manager v2.0.

New Features and Improvements

SolarWinds Patch Manager v2.0 includes the following new features and improvements:

  • Improved Installer

    Simplifies your Patch Manager installation by installing pre-requisites and providing you an Express installation option in addition to the Advanced installation option. The Express option will install both a WSUS server and an SQL Server Express instance to facilitate the configuration of your install.

  • Agents

    Install agents on computers that are difficult to manage with Patch Manager. Agents do not require open WMI connections nor do you need to configure the clients and network for remote Windows Management Instrumentation.

  • First Time Usage Wizard

    This wizard guides you through installing your first updates after Patch Manager 2.0 is installed.

  • Improved licensing

    After you apply your new license key in v2.0, you will be able to upgrade to future licenses by clicking a button in the License Manager instead of reapplying an activation code.

  • Third Party Update Catalogs

    The signed provider is now SolarWinds instead of EminentWare.

  • Additional OS support

    You can install Patch Manager on Windows 8, Windows 8.1, and Windows Server 2012 R2.

  • Improved error messages

    Improved error handling around installation and common issues found when updating.

  • FIPS compatibility

    You can install Patch Manager on FIPS-enabled computers.

Fixed Issues

Issue Case Number
Upgrading the web console fails. 540963, 453061
The initial data is blank after installing. 541732
Package boot does not support MSP files. 433372, 433460
Scheduled task start time is not respected when you select Hourly 333615
Cannot combine Wake on LAN without management tasks. 367190
Cannot create a computer rule when you select a WSUS server. -
Updates with EXE files occasionally fail. 451037
The default inventory receives a datasource exception error when collecting Groups information. 414874, 397250
Cannot create a rule of type "File Creation Date with Registry Value". 469330
Problems downloading Dell and HP updates. 474977
Receive errors when deleting content from a published patch that uses PackageBoot. 480188
Incorrect server information displayed from Managed Computers. 484669
Credentials are overwritten after you configure an Automation Server to write to the Primary Application Server database. 468337

Open Issues

Issue Case Number
Cannot upgrade a Secondary Application Server if the Primary Application Server is not available. -
Agent policies are not updated when the Automation Server routing rules are edited -
You cannot install the web console and WSUS on Windows Server 2003 x64 or on Windows Server 2003 R2 x64. -

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:

Installed Version Recommended Upgrade Path
Pre 1.72 => 1.72 => 2.0
1.72 => 2.0
1.73 => 2.0
1.80 => 2.0

IMPORTANT NOTES:

  • When you upgrade to this version, Patch Manager changes the executable the default shortcut uses to launch the program for the logged-on user. If other users use Patch Manager on a system you are upgrading or you have changed the location of the Start menu or desktop shortcut, manually change the target to MMCLoader.exe for any neglected shortcuts. 
  • If you have not already installed .NET Framework 4.0 on your systems running Patch Manager, the 2.0 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.

Upgrade Procedure (from versions earlier than 1.72)

Due to the security changes included in version 1.72 and all later versions, you cannot use the built-in EminentWare Package Management utility when upgrading from any version lower than 1.72. Instead, use the following procedure to upgrade each of your Patch Manager servers individually.

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, and
  • A Patch Manager console account in the Enterprise Administrator security role in Patch Manager.

 

To upgrade to Patch Manager version 2.0:

  1. Download the 1.72 and 2.0 upgrade packages from the SolarWinds Customer Portal.
  2. Upgrade all of your Patch Manager servers and consoles to version 1.72.
  3. After all of your Patch Manager systems are on version 1.72, upgrade your Primary Application Server (PAS) to version 2.0.
  4. If you have additional Patch Manager servers and/or consoles in your publishing environment, upgrade all downstream servers and consoles to version 2.0 after you upgrade your PAS.

 

If you have not already applied Microsoft KB2720211 or KB2734608 to your WSUS and Patch Manager systems, the upgrade to version 2.0 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.

Upgrade Procedure (from version 1.72 or later)

If you are upgrading from version 1.72 or later, use the updater executable provided in the SolarWinds Customer Portal.

To upgrade to Patch Manager version 2.0:

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

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 1995-2013 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, the SolarWinds & Design, ipMonitor, LANsurveyor, Orion, and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies. Microsoft®, Windows® and SQL Server® are registered trademarks of Microsoft Corporation in the United States and/or other countries.

Last modified
08:22, 30 Mar 2017

Tags

Classifications

Public