Patch Manager 2.1.2 release notes
Release date: June 7, 2016
These release notes describe the new features, improvements, and fixed issues in Patch Manager 2.1.2. They also provide information about upgrades and describe workarounds for known issues.
If you are looking for previous release notes for Patch Manager, see Previous Version documentation.
New customer installation
For information about installing Patch Manager, see the Patch Manager Installation Guide.
How to upgrade
This version is capable of upgrading Patch Manager from any previous version. However, SolarWinds recommends the following upgrade paths for the Patch Manager Administrator Console based on the current installed version of Patch Manager.
| Installed Version | Recommended Upgrade Path |
|---|---|
| 1.80 | > 2.1 > 2.1.2 |
| 1.85 | > 2.1 > 2.1.2 |
| 2.0 | > 2.1 > 2.1.2 |
| 2.1 | > 2.1.2 |
| 2.1.1 | > 2.1.2 |
SolarWinds recommends the following upgrade paths for the Patch Manager Web Console based on the current installed version of Patch Manager.
| Installed Version | Recommended Upgrade Path |
|---|---|
| 1.80 | > 2.0 > 2.1 > 2.1.2 |
| 1.85 | > 2.0 > 2.1 > 2.1.2 |
| 2.0 | > 2.1 > 2.1.2 |
| 2.1 | > 2.1.2 |
When you upgrade Patch Manager, use the following conventions:
- 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.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.
- SCCM 2012 SP1, SCCM 1511 and SCCM 1602 are supported.
- Windows 10 is supported for Evaluation of Patch Manager Server and as Patch Manager Console OS.
- MS SQL Server 2014 express is now included to installation and MS SQL server 2016 is supported.
Upgrade to Patch Manager 2.1.2
- Download the 2.0 and 2.1 upgrade packages from the SolarWinds Customer Portal.
- Upgrade all of your Patch Manager servers and consoles to version 2.0.
- Upgrade your Primary Application Server (PAS) to version 2.1.1.
- Upgrade your Primary Application Server (PAS) to version 2.1.2.
- If you have additional Patch Manager servers and/or consoles in your publishing environment, upgrade all downstream servers and consoles to version 2.1.2 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.1 and higher 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 from Patch Manager version 1.80 or later
- Download the upgrade packages from SolarWinds Customer Portal.
- Upgrade all of your Patch Manager servers and consoles to version 2.1.1.
Upgrade from Patch Manager versions earlier than 1.8
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.
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.
Fixed issues in Patch Manager 2.1.2
| Case Number | Description |
|---|---|
| 567622 | Fixed the issue in the custom updates after the packageboot setting were applied and deployed. |
| 863609, 839652 | Fixed the issue where scheduled tasks did not show all added computers. |
|
923486, 944411, 780879, 950494, 780879 |
Fixed the issue where the FTP connection did not work through a proxy server. |
| 768285 | Fixed the issue where autopublishing could not download packages through a proxy. |
| 786064 | Fixed the issue where the WSUS reports pulled incorrect information. |
| 814300 | Fixed the issue where the publishing wizard was not responding when a package was downloaded manually and the console had not been refreshed. |
| 861555, 808836, 868543, 939056, 854988 | Fixed the issue where adding computers generated the error "X computer(s) with the same name were already added." |
| 829268 | Fixed the issue where you were unable to import installer file using Package Download Assistant. |
| 681182 | Fixed the issue where the ConfigMgr deployment of Acrobat Reader 11.0 worked correctly but reported as Failed instead of Pending reboot. |
| 843472 | Fixed the issue where the local help files of Patch Manager was not available for download. |
| 861556 | Added support for Windows 10 to MMC Configuration Wizard. |
| 870745 | Fixed the issue where the date parameter on scheduled task was incorrect. |
| N/A | Fixed the issue where users assign a User role were able to delete WSUS. |
|
N/A |
Fixed the issue where running the updates for migrated databases checked for configurationwizard.xml instead of the the ConnectionString in the registry. |
| N/A | Fixed the issue where any username with format "domain\\user" was able to log in. |
| 788895 | Fixed the issue where email subject was empty for scheduled tasks after upgrading to version 2.1 |
| 886711 | Fixed the issue where the time was incorrect when scheduling an approval with a deadline. |
| 930554 | Fixed the issue where there was an incorrect display date for months earlier than October (less than 10). |
End of support
This version of Patch Manager no longer supports the following platforms and features.
| Type | Details |
|---|---|
| Patch Manager 1.73 and earlier | All versions of Patch Manager prior to 1.73 have entered the End-Of-Life cycle. |
| 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 2008 | Windows 2008 and Windows 2008 R2 without SP1 are no longer supported as OS starting Patch Manager 2.1.2. |
| 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 notices
© 2016 SolarWinds Worldwide, LLC. All rights reserved.
This document may not 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 prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. 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, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or 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 or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.