Release date: January 2021
Updated February 10, 2021
These release notes describe new features, improvements, and fixed issues in SolarWinds Server & Application Monitor (SAM) 2020.2.4. They also provide information about installation, upgrades and workarounds for known issues.
SAM 2020.2.4 is a service release. For more information, see documents for the full release:
These release notes provide the following details:
- New features and improvements in SAM
- New customer installation
- How to upgrade
- Fixed issues
- Known issues
- End of life
- Legal notices
- System requirements have not changed. See the SAM 2020.2 System Requirements.
- For details about the latest hotfixes, see SAM hotfixes and Orion Platform hotfixes.
- If you are looking for previous release notes for SAM, see Previous Version documentation.
- To learn about working in the Orion Platform, see the Orion Platform 2020.2 Administrator Guide.
- SAM 2020.2.4 runs on Orion Platform 2020.2.4. See the Orion Platform 2020.2.4 Release Notes.
SAM 2020.2.4 includes security enhancements and is signed with a new digital code-signing certificate.
Use the Orion Installer, available in the Customer Portal, to install SAM. See the Orion Platform Products Installation and Upgrade Guide for details. After installation, see the SAM Getting Started Guide to learn about configuring and customizing SAM.
To prepare for the upgrade:
- Read these Release Notes.
- Confirm that all servers comply with SAM 2020.2 System Requirements.
- (Optional) Back up any custom code, such as modified SolarWinds .css files or added .js files. Click here for tips.
If upgrading from a previous version, note the following details:
- The Orion Log Viewer (OLV) replaces the legacy Syslog and Trap Viewers.
- To collect trust data for Global Catalog (GC) servers, AppInsight for Active Directory uses port 3268. If a GC domain controller uses port 3269 instead, update that setting in the application monitor assigned to the node. See Configure AppInsight for Active Directory on nodes.
- The Application Dependencies feature is disabled during upgrades to prevent performance issues in large environments. To restart polling later, enable the Application Dependencies feature.
- If you exceed recommended cloud monitoring limits and receive a 503 Service Unavailable error when adding Azure accounts, click here for a workaround.
- To monitor Exchange Server 2016 and later, install PowerShell 2.0 or later and provide local Administrator rights. See Using PowerShell in SAM.
- If monitoring containers in your SAM environment:
- If you upgrade to a localized version of SAM, all templates with new versions that support localization will be replaced. Back up any SAM templates and application monitors modified with custom changes. You cannot roll back to English after installing the Orion Platform in another language.
Due to end-of-support by Microsoft for Basic Authentication connections to Exchange Online APIs, the following templates were deprecated in SAM 2020.2. Consider using API poller templates designed for Microsoft 365 instead, as described in the SAM API Poller Template Guide.
- Microsoft Office 365 Exchange Online
- Microsoft Office 365 Mobile Device Management
- Microsoft Office 365 Portal
- Microsoft Office 365 Subscription
- The following Citrix templates were deprecated in SAM 2020.2 but are still available in THWACK. Click here for the latest Citrix templates, including the Citrix Hypervisor template that replaces the Citrix XenServer template.
- Citrix PVS Accelerator for XenServer
- Citrix XenApp 5.0 Core WMI Counters
- Citrix XenApp 5.0 ICA Session WMI Counters
- Citrix XenApp 5.0 Presentation Server WMI Counters
- Citrix XenApp 5.0 Services
- Citrix XenServer
- The following templates were deprecated in SAM 2020.2.1 but are still available in THWACK. Use AppInsight for SQL to monitor the NTA Flow Storage Database instead.
- SolarWinds NetFlow Traffic Analyzer Database
- SolarWinds NetFlow Traffic Analyzer
- The Orion Server 2017.3 and SolarWinds Failover Engine templates were replaced by Orion Server 2020.2 templates. Deprecated templates remain in THWACK and legacy SAM 2017.3 — 2019.4 installations.
SolarWinds recommends checking THWACK periodically for updates to SAM application monitor templates. Apart from AppInsight templates, SAM doesn't update those templates automatically during upgrades to avoid overwriting custom changes. For details, see Import and export SAM templates.
Begin the upgrade
Starting with SAM 6.9, you can upgrade SAM directly from the Orion Web Console (Settings > My Orion Deployment). Downloading the Orion Installer is no longer necessary.
- To upgrade SAM and other Orion Platform products, see the Orion Platform Products Installation and Upgrade Guide.
- Do you need to migrate as part of your upgrade? See the Migration Guide.
- To upgrade your scalability engines (Additional Polling Engines, Additional Web Servers, High Availability servers), see Options for upgrading scalability engines.
|N/A||The SolarWinds.Core.BusinessLayer.dll security vulnerability in Orion Platform 2019.4 Hotfix 5, Orion Platform 2020.2, and Orion Platform 2020.2 Hotfix 1 was addressed. See the SolarWinds Security Advisory for details.|
|Days Remaining in SSL Certificate Expiration and IIS SSL Certificate Expiration report widgets do not update for AppInsight for IIS. Polling only occurs once — when AppInsight for IIS is assigned to a node.||Assign the SSL Certificate Expiration Date Monitor template to the IIS node to update SSL dates daily. Click here for details.|
|Component monitor scripts in the AIX template do not run if "Inherit credentials from node" is enabled. Header issues in Perl script output prevent component monitors from inheriting credentials from nodes, so scripts fail.||This may impact CPU statistic, Paging statistic/sec, Disk operations/sec of system devices, and Top 10 active processes metrics. As a workaround, edit component monitors to provide credentials, or avoid using "Inherit credentials from node" option for affected component monitors. Click here for details.|
|Application Dependency polling fails; dependencies or connections between nodes for Windows Server and other applications may not appear. Rows in the dbo.AgentManagement_Agents table that share a Node ID may cause exceptions.||As a workaround, uninstall agents from nodes, remove duplicate database rows, and then reinstall agents. Click here for details.|
|Some SAM pages and widgets related to features introduced in SAM 2020.2 are not compatible with Internet Explorer (IE) 11.||As a workaround, use a Chrome, Firefox, or Microsoft Edge browser instead of IE.|
|A known Microsoft issue may create inconsistency in SAM SQL tables, as indicated by a Database Integrity Check message.||
As a workaround, back up the Orion database and execute a SQL query provided here.
|Windows Scheduled Tasks Monitor (WSTM) polling fails for Active Directory nodes with UPN-formatted credentials. "Access is denied" errors appear in Windows Scheduled Tasks widgets.||As a workaround, use the down-level logon name format (domain\user) instead of UPN format (user@domain). Click here for details.|
|In SAM 6.9, high memory utilization for SolarWinds.ServiceHost.Process slows Active Directory servers monitored by Orion agents.||The ServiceDirectoryClient component leaks Service Directory client connections if exceptions occur when opening the channel. Upgrade to the latest SAM release or switch polling methods. Click here for details.|
|Microsoft Windows Server 2008 R2-2012 R2 Failover Cluster (Advanced) template fails with errors and node status switches to Down.||If the 64-bit FailoverClusters module conflicts with PowerShell bitness and polling fails, modify scripts in the application monitor assigned to the node. Click here for details.|
|Warranty data does not appear after Asset Inventory polling of HPE Proliant servers.||API changes made by HP interrupt polling. No workaround is currently available. Click here for details.|
|If using the Orion agent for Linux to monitor Wildfly (formerly JBoss) systems, the JMX bridge can be used to monitor WildFly or JBoss targets, but not both types simultaneously.||WildFly, formerly known as JBoss, is an application server developed by Red Hat. For details, see Configure JMX monitoring on WildFly servers.|
|As described here, SAM deploys agent plug-ins to target systems to monitor application connections. Application dependency polling is not supported on target Linux systems that use GNU C Library (glibc) 2.17 or earlier.||Plug-ins deployed by SAM 2020.2 and later include an Nping executable binary that doesn't support distributions based on glibc 2.17 or earlier, such as CentOS and Red Hat Enterprise Linux (RHEL) 6. As a workaround, update Linux distributions on target systems. SolarWinds recommends testing in an experimental OS first.|
|After upgrading to SAM 2020.2 or later, AppInsight for Active Directory polling stops.||If an "Unable to start polling" message appears on the AppInsight for Active Directory Details page, make sure the version of .NET Framework on target nodes matches the version on the Orion server. SAM 2020.2 uses .NET 4.8. Click here for details.|
|AppInsight for IIS polling on Windows Server 2008 nodes may cause WinRMFeatureService errors in logs.||
Starting in SAM 2020.2, WinRM is the default transport method to collect data for WMI-based component monitors. If monitoring Windows Server 2008 nodes with AppInsight for IIS, the following message may appear in application logs:
The default log location is
This message appears because the WinRM Invoke method is not supported by Windows Server 2008. Fallback should occur so polling continues for IIS servers.
|AppInsight for IIS polling fails on Windows Server 2008 R2 SP1 nodes and applications switch to Unknown state.||
Windows Server .NET 4.8 agents expect a later version of PowerShell, so SolarWinds.APM.Probes.CustomWmiProbe- and Microsoft.Management.Infrastructure-related errors appear in logfiles.
As a workaround, install PowerShell 3.0 or later on target servers. Click here for details.
See the End of Life Policy for details about life cycles for SolarWinds products.
|EoL Announcements||EoE Effective Dates||EoL Effective Dates|
June 4, 2020
End-of-Life (EoL) announcement – Customers on SAM 6.6 and SAM 6.7 should begin transitioning to the latest version of SAM.
September 4, 2020
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.6 and SAM 6.7 will no longer be actively supported by SolarWinds.
September 3, 2021
EoL – SolarWinds will no longer provide technical support for SAM 6.6 and SAM 6.7.
July 31, 2019
EoL announcement – Customers on SAM 6.5 should begin transitioning to the latest version of SAM.
December 30, 2019
EoE – Service releases, bug fixes, workarounds, and service packs for SAM 6.5 will no longer be actively supported by SolarWinds.
June 30, 2020
EoL – SolarWinds will no longer provide technical support for SAM 6.5.
See Currently supported software versions for more information.
© 2021 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.