Patch Manager 2.1.7 release notes
Release date: June 6, 2019
Last updated: July 9, 2019
These release notes describe the new features, improvements, and fixed issues in Patch Manager 2.1.7. They also provide information about upgrades and describe workarounds for known issues.
If you are looking for previous release notes for Patch Manager, see the Previous Version documentation.
New features and improvements
Patch Manager 2.1.7 offers the following new features and improvements compared to previous releases.
Install Patch Manager using the SolarWinds Orion Installer
You can now install Patch Manager and your SolarWinds Orion Platform products using the SolarWinds Orion Installer. When the installation is completed, you can access Patch Manager from the SolarWinds Orion Web Console. This installation requires Microsoft Windows Server 2016 or later and Microsoft SQL Server 2014 or later installed on the Orion server.
If you are using Patch Manager as a stand-alone application, you can download the Patch Manager installer from the Customer Portal and run the installer on a supported server. This installation requires Windows Server 2012 or later and SQL Server 2012 or later installed on the Patch Manager server.
Generate Patch Manager reports in the Orion Web Console
You can now generate Patch Manager reports in the Orion Web Console. These reports are available in the console when you integrate Patch Manager with the Orion Platform.
When you configure your Patch Manager settings in the Orion Web Console, make sure that your user account includes login credentials to the SQL database server hosting the Patch Manager database. You can use Microsoft SQL Server Management Studio or SQL Server Configuration Manager to add your login credentials to the database.
>> Learn more about the Orion Web Console reports
Additional improvements
- Integration with Orion Platform 2019.2
- Microsoft Azure support
- Microsoft Windows Server 2019 support
- SCCM 1810 support
New customer installation
For information about installing Patch Manager, see the Patch Manager Installation Guide.
Before you upgrade!
If you are upgrading from a previous version, be aware of the following considerations:
- Make sure your server complies with the Patch Manager 2.1.7 system requirements.
- Back up any custom code, such as changed SolarWinds .css files or added .js files. These files my be overwritten with the upgrade. Learn more.
How to upgrade
If you are upgrading from a previous version, use the following resources to plan and implement your upgrade:
- You can upgrade from Patch Manager 2.1 to the latest version. See the Patch Manager Upgrade Guide for instructions. This guide includes detailed information to help you plan, complete, and troubleshoot your upgrade.
- Use the Product Upgrade Advisor to determine your upgrade path. Based on your current environment and versions, the Product Upgrade Advisor provides an ordered list of how to proceed with the upgrade.
- When you are ready, download the upgrade package from the from the SolarWinds Customer Portal.
Fixed issues
Patch Manager 2.1.7 fixes the following issues.
| Case Number | Description |
|---|---|
|
00014382 00170208 00271905 1188381 1190531 1238729 |
The Patch Manager installer no longer installs the Orion Services when you run the installer on a standalone Patch Manager server. |
|
00183980 |
The Patch Manager Administrator Console displays the correct error message displays when an update task fails. |
|
00154683 |
The ReportNow task no longer hangs when you run the task on remote computers running a Patch Manager agent. |
|
00204127 00217203 00306453 00308650 |
All scheduled tasks run correctly after you upgrade Patch Manager to the latest release. |
Known issues
| 00246939 / Unable to clear caches and view layouts for all users |
|---|
| Issue: When you open the Patch Manager Admin Console, select Administration and Reporting > General Settings > Clear Caches and View Layouts, the application deletes the cache data and view layouts only for the current user. |
| Resolution/Work-around: Log in to Patch Manager using the Eminentware Data Grid Service (EWDGS) account and repeat the procedure. |
End of support
This version of Patch Manager no longer supports the following platforms and features.
| Type | Details |
|---|---|
| Patch Manager Orion web user interface |
The Patch Manager Orion web user interface no longer supports an Orion server running Microsoft Windows Server 2012 or Windows Server 2012 R2. To integrate Patch Manager with the Orion Platform, you must update the Orion server to Windows Server 2016 or later. See the Orion Platform documentation for the latest Orion Platform server requirements. |
Legal notices
© 2024 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.