Release date: May 24, 2022
These release notes describe the new features, improvements, and fixed issues in SolarWinds Platform 2022.2 They also provide information about upgrades and describe workarounds for known issues.
- For information on latest hotfixes, see SolarWinds Platform Hotfixes.
- For release notes for previous SolarWinds Platform versions, see Previous Version documentation.
- For information about requirements, see SolarWinds Platform 2022.2 System Requirements.
- For information about working with the SolarWinds Platform, see the SolarWinds Platform Administrator Guide.
New features and improvements in SolarWinds Platform
See SolarWinds Hybrid Cloud Observability 2022.2 release notes for information about new features.
New customer installation
For information about installing SolarWinds Platform, see Install [%Core.HCO_no_version%].
How to upgrade
If you are upgrading from an earlier Orion Platform version, see Upgrade SolarWinds Platform products to SolarWinds Hybrid Cloud Observability.
Before you upgrade
Make sure all your legacy reports are migrated. You won't be able to access legacy reports and related tools anymore.
If you are using CAC Authentication, you will need to adjust the CAC Authentication setup after the upgrade to Hybrid Cloud Observability 2022.2 or later. See Enable Smart Card (CAC/PKI) user authentication for Orion Web Console and complete Step 2: Secure the Site for Smart Card Authentication Access.
SolarWinds Platform 2022.2 fixes the following issues.
|980868, 1019746||SolarWinds Platform agent has no longer the TLS fallback issue.|
|961090||The issue where special characters occurred in logs on SolarWinds Platform agent Linux server was addressed.|
|973265, 982354, 983143, 985085, 992107, 999152, 1007205,||The issue where login page timed out when authenticating using a Windows group was addressed.|
|972964||The issue where users were alerted on multiple blocks in the database was addressed.|
|908383||The issue where URL parameters disappeared during CAC login was addressed.|
|988708||The issue where a Meraki device did not show correct status for an Access Point was addressed.|
|968089||The issue where IP SLA nodes were not displayed when grouped by City was addressed.|
|00875466, 00887725, 00889456, 00935188, 00943823, 00980794, 01023124, 01049079||"User changed account (GroupInfo)" audit event is no longer shown in the event log on each Group Member log in occurrence.|
|853813||The issue where DirectLink account didn't work with the Windows pass-through authentication was addressed.|
|997395||The issue where the ingress filter on the Node Details page didn't work correctly when the browser was in Turkish was addressed.|
|890180||The issue where an Infoblox server required FQDN to accept the https certificate was addressed.|
|897765||The issue where a SolarWinds Platform Map didn't refresh in the NOC view was addressed.|
|936494||The KCP vendor name was changed to AKCP.|
|886612||The issue where non-NCM SWIS entities were patched by the NCM limitation check was addressed.|
|916852||The issue where an API poller was parsing polling results incorrectly was addressed.|
|687462, 867247||The issue where LDAP authentication failed with the Could not connect Ldap server message was addressed.|
|903521||The issue with accessing the NTA Settings page because of DNS resolution was addressed.|
|929373||The issue where NTA search did not return any data from vCenter sources was addressed.|
|923990, 992196||The issue of an additional SNMP credential test for SolarWinds Platform agent failing from the Additional polling engine was addressed.|
|935444, 943505, 949212, 949578, 1013605, 1014025||The issue where SolarWinds Platform users were missing in the RabbitMQ for both members in the pool was addressed.|
|862745||Performance issues on the NCM Configuration transfer page related to node limitations were addressed.|
|949327||The issue where only a few widgets could be added to views when the user interface was not in English was addressed.|
|926414||The issue where the option to collect per-node diagnostics was disabled was addressed.|
|914196||The issue where inserted properties were not visible on SolarWinds Platform Maps historical views was addressed.|
|907950, 927873||The issue where objects on Network Atlas maps had corrupt names was addressed.|
|896306||The issue where network utilization was calculated incorrectly for vCenter servers was addressed.|
|874296||The issue where change lines were missing in configuration changes in CCR was addressed.|
|876041||The issue where Windows SolarWinds Platform agents got stuck during the upgrade was addressed.|
|885334||CPU spikes on Module Engine Service caused by the macro parser were addressed.|
|869071, 927783, 992609, 1039968||The issues on Custom Chart Edit page were addressed.|
|847128, 856044||Performance issues on the new Custom Properties Management page were addressed.|
|830021, 852954, 1045446||The issue where FIPS manager didn't update several files was addressed.|
|826584, 872482||Performance issues when executing scripts in Configuration Management were addressed.|
|843846, 844647||The issue where ServiceNow incident updates made simultaneously were not processed at the same time was addressed.|
|779732||The issue where index defragmentation during Database Maintenance fails when an index name contains "space" was addressed.|
|834613||The issue where vendor icons were missing in an IPAM report was addressed.|
|789774||The issue with incorrect URI in PCU indications was addressed.|
|816557||The Custom Table widget issues in EOC were addressed.|
|910267, 990283, 1025186||The issue where Windows 2022 were detected as Windows 2019 when using SNMP, WMI, or SolarWinds Platform agent polling was addressed.|
|796561, 815308, 871751, 886736, 1017228||The issue of duplicated SolarWinds Platform agentnodes was addressed.|
|774629, 799740, 908031, 989224, 1048518||The issue where relational properties were not resolved when using wrapped queries was addressed.|
|779681, 865218, 922991||The issue where the Custom Properties for Nodes widget didn't show external nodes was addressed.|
|600463, 792054||The issue where Log Viewer search didn't take into account the filter selection was addressed.|
|725187, 753989||Users get emails for each triggered log rule.|
|588802, 622165||The issue where users couldn't delete created comparison criteria was addressed.|
|920967||The issue where content-type headers (API poller request with POST method) were set incorrectly was addressed.|
|782842, 787019, 790877, 870455, 876070, 1004030||The issue where running a vulnerability scanner against the SolarWinds Platform caused IIS to stop suddenly was addressed.|
|555480, 801105, 802598, 945531,||The issue where view limitations are copied with views was addressed.|
|Launching the upgrade to SolarWinds Hybrid Cloud Observability 2022.2 on a server with EOC fails and breaks the EOC deployment|
Issue: Upgrading EOC deployments to SolarWinds Hybrid Cloud Observability 2022.2 is not supported. However, the upgrade is not blocked. When you execute the installer on a server with EOC, the EOC deployment is broken and the Hybrid Cloud Observability installation fails.
Work-around: None. Do not start the upgrade to SolarWinds Hybrid Cloud Observability 2022.2 on servers where EOC is deployed.
|Upgrading to SolarWinds Hybrid Cloud Observability 2022.2 RC1 deletes all data in the parent folder|
Issue: When upgrading to SolarWinds Hybrid Cloud Observability 2022.2 RC1, the installer attempts to delete the parent folder. In environments where Orion Platform was not installed in the default folder (
Example: If your installation folder is called
Work-around: Before you start the upgrade, check the installation folder for Orion Platform. If it is called Orion, make sure it is safe to have the entire parent folder deleted. If it is not safe, do not upgrade to RC1.
|NTM maps are not supported in SolarWinds Platform 2022.2|
Issue: After upgrading to SolarWinds Platform 2022.2, Network Atlas does not support NTM maps.
Work-around: Open the NTM map in an older Network Atlas version, convert it to a Network Atlas map. See Export maps in NTM help for details.
|MIB database version not up-to-date after the upgrade to SolarWinds Platform 2022.2|
Issue: After upgrading to SolarWinds Platform 2022.2, your MIB Database might not be up-to-date. During the upgrade, SolarWinds Installer uninstalls all products and re-deploys the MIB Database that was up-to-date on SolarWinds Platform 2022.2 GA date.
Work-around: Update the MIB Database manually.
This version of SolarWinds Platform no longer supports the following platforms and features.
|Legacy Orion Report Writer||
All tools and widgets related to legacy reports are removed in SolarWinds Platform 2022.2.
© 2022 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.