Patch Manager 2.1.6 Release Notes
Release date: December 4, 2018
Last updated: July 9, 2019
These release notes describe the new features, improvements, and fixed issues in Patch Manager 2.1.6. 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 in Patch Manager
Patch Manager 2.1.6 offers new features and improvements compared to previous releases of Patch Manager.
Support for Windows PowerShell scripts
Windows PowerShell scripts can now be executed as part of an Update task, both before and after the task completes. This new functionality provides additional flexibility to your Update tasks to perform tasks such as snapshotting a VM prior to an update task and reverting to the snapshot if an issue occurs, stopping services in a particular order, failing over machines and muting alerts from Orion nodes during an Update task.
Patch Manager supports remote PowerShell only for WMI clients. Agents do not support remote PowerShell.
Updated cryptographic protocol support
This release now supports Transport Layer Security (TLS) 1.2 for improved security and ensures that Patch Manager no longer requires TLS 1.0 or 1.1 to be enabled on the Patch Manager server.
Updated Microsoft product support
This release supports the following Microsoft products:
- Microsoft SCCM 1806
- Microsoft SQL Server 2016 Express Service Pack 1 (SP1)
- Microsoft SQL Server 2017
- Microsoft Windows Server 2019
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.6 system requirements.
- Always use the Product Upgrade Advisor to build your upgrade path. When downloading the installations, please use the Customer Portal. For details, see Upgrade Adviser showing Orion Platform (Core) 2017 as Maintenance Expired.
- If you have written your own code, such as changing SolarWinds .css files or adding .js files, it may be overwritten with the upgrade. You can learn more about custom code in this article.
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 SolarWinds 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 SolarWinds Customer Portal.
Patch Manager 2.1.6 fixes the following issues.
Patch Manager now uses the SHA2 (SHA-256) cryptographic hash algorithm to create the following certificates:
|The Discovery task now includes an additional WMI request that retrieves MAC addresses from computers in other subnets.|
|The Windows Firewall tab now functions correctly when you connect to remote systems running Microsoft Windows Server 2016.|
|You can now synchronize with the SolarWinds Update Catalog using Transport Layer Security (TLS) 1.2, which is now supported in this release.|
|You can now process email messages that include a domain extension longer than four letters.|
|A spelling error in the Patch Manager Web Console Server Health and Desktop Health resources is resolved.|
|The Update Management Wizard now allows you to include approved updates from previous months.|
|You can now access the Windows Update History on remote systems running Microsoft Windows 10.|
This version of Patch Manager deprecates the following platforms and features.
For information about supported version of SolarWinds products, see Currently supported software versions.
|Patch Manager Orion web user interface||
Beginning in 2.1.7, the Patch Manager Orion web user interface will not support an Orion server running Microsoft Windows Server 2012 or Windows Server 2012 R2. If you are integrating Patch Manager with the Orion platform, consider upgrading your Orion server to Windows Server 2016 or later.
See the Orion Platform documentation for the latest Orion Platform server requirements.
|Cryptographic protocol||Transport Layer Security 1.0 (TLS 1.0)|
|Cryptographic protocol||Secure Socket Layer (SSL) 3.0|
© 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.