Patch Manager 2.1.3 Release Notes
Release date: September 28, 2019
These release notes describe the new features, improvements, and fixed issues in Patch Manager 2.1.3. 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 features and improvements in Patch Manager
Patch Manager 2.1.3 offers new features and improvements compared to previous releases of Patch Manager.
This release of SolarWinds Orion Platform features almost instantaneous, automated failover to a secondary server to ensure continuous monitoring when a component failure occurs. SolarWinds High Availability (HA) provides failover HA for your environment maintained through the Orion web console. Easily create an HA pool, update your secondary server, and activate HA in your current Orion environment.
This feature is part of the Orion Platform for integrated Patch Manager.
Web-based License Manager
Easily add, activate, and manage Orion product licenses through the web-based License Manager. Accessing the License Manager on your main polling engine, you can monitor and update full product and evaluation licenses for your main poller, additional pollers, additional web servers, stackable pollers, and high availability pools all through one page. The License Manager also provides automatic online and offline modes for managing licenses. Add and manage evaluations with ease, including HA.
This feature is part of the Orion Platform for integrated Patch Manager.
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 and Web Console based on the current installed version of Patch Manager.
|Installed Version||Recommended Upgrade Path|
|2.0||2.1 > 2.1.2 > 2.1.3|
|2.1||2.1.2 > 2.1.3|
When you upgrade Patch Manager, use the following conventions:
- For Patch Manager versions 1.80 and 1.85, it is recommended to upgrade first to 2.0 before upgrading to 2.1 and later versions.
- Patch Manager 2.1.3 supports direct update from 2.1.1 and 2.1.2, without the incremental update.
- 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.
- If you are upgrading without internet access, see KB4511 for installation prerequisites.
- SCCM 2012 SP1, SCCM 1511 and SCCM 1602 are supported.
- Windows 10 supported for Evaluation of Patch Manager Server and as Patch Manager Console OS.
- MS SQL Server 2014 express in now included in the installation and MS SQL server 2016 is supported.
Upgrade to Patch Manager 2.1.3
- 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.3.
- If you have additional Patch Manager servers and/or consoles in your publishing environment, upgrade all downstream servers and consoles to version 2.1.3 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 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 Orion Platform 2016.2
|1015439, 1017699, 1017652, 1015588, 1015552, 1015299, 1014989, 1016095, 1015662, 1016127, 1015267, 1016112, 1015219, 1016099, 1016280, 1016927, 1015177, 1015174, 1015614, 1016588, 1016630, 1016609, 1016610, 1015431, 1015014, 1015548, 1015506, 1016500, 1016384, 1016208, 1015385, 1015627, 1015516, 1015412, 1016247, 1016175, 1015390, 1015349, 1015345, 1015306, 1015749, 1015526, 1015466, 1015396, 1015561, 1015783, 1015356, 1015647, 1015661, 1015564, 1015571, 1015595, 1015570, 1015652, 1015606, 1015061, 1015380, 1015424, 1015454, 1015460, 1015364, 1015457, 1015413, 1015016, 1015386, 1014969, 1015261, 1043147, 1016982, 1008932||The Worldwide Map resource displays without the Mapquest notifications.|
|920560, 1013825, 1052808, 1048941, 1020501||Alert actions trigger when you choose to alert only when multiple objects meet the trigger conditions at the same time.|
|1003653, 1011487, 1005787||You can open the Orion Web Console shortcut as a non-administrator.|
|1012549, 1040462, 1042804||You can edit multiple nodes' properties without impacting the saved SNMP v3 credentials.|
|1003918||The Top CPU by Percent resource shows data for Cisco ASR 9010 devices.|
|1005743||Custom SQL filters are not case sensitive.|
|1003655, 1000374||The Configuration Wizard now installs all services and the Orion Web Console loads after an upgrade.|
|1000843||Menu bars are not sent when emailing a report as HTML.|
|990493, 1039347||Duplicate and edit alerts with reset actions.|
|978248||You can view graphs in scheduled reports after you configure the Orion Web Console for SSL.|
|1029471, 1037482||Restrict access to areas of the menu bar and views.|
|956237||You can select Default for Object type in Network Atlas.|
|950265||Filter the "Top XX Volumes by Disk Space Used" resource by caption.|
|873578, 861900||Improved how charts and graphs are displayed in the PDF output of reports.|
|1016211, 1004847, 1009082, 993024, 100588, 1012554||Improved upgrading with saved SNMP v3 credentials.|
|1003240||Top navigation menu in NOC views does not overlap with the view content.|
|992570, 1038932, 1025297||When integrating SolarWinds products with ServiceNow, alerts generate correctly without object reference errors.|
|1045304, 1015785||The Orion Web Console does not hang when managing alerts or alert maintenance.|
|989718, 1000003, 1003398, 1008094, 1015258, 1038560, 994777, 1004330, 843652||Send multiple reports at the same time and send reports that were copied and modified from another report without errors.|
|1028086, 1005787, 1003653, 1011487, 1016920||You can install and open the Orion Web Console from the shortcut without the following error: "The credentials supplied to the package were not recognized."|
|1020916||Web pages sent through the Email A Web Page alert action are sent as a PDF to preserve the same styling and appearance as in your browser.|
|1012349||Use the "Time of Day" and "Hour of Day" options to restrict the report to business hours.|
|1015855||Improved the UI around the Time of Day portion of alert actions.|
|Agent deployment to host without a /tmp directory|
|Issue: Agent deployment may not succeed if Linux host does not have a /tmp directory.|
|Resolution/Work-around: Rerun the agent deployment to properly complete the deployment.|
|Account limitations for Windows group accounts|
|Issue: Accounts that are added as part of a Windows group account do not respect menu or view restrictions.|
|Resolution/Work-around: Individually add accounts.|
End of support
This version of Patch Manager no longer supports the following platforms and features.
|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.|
© 2020 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.