SolarWinds Platform 2026.2.2
← All SolarWinds releases · Searchable index of all 356 fixed issues
Items fixed
| SolarWinds case # | Product | Description |
|---|---|---|
| 02162683 | Platform | Polling GCP load balancers no longer fails with errors such as the following: Poller execution failed SolarWinds.Orion.Declarative.Contract.Exceptions.MapPropertyException: Failed to pick source values from Path: '$..IPProtocol' |
| 02155584 | Platform | Legacy Custom SQL widgets are now correctly displayed to non-admin users. |
| 02152726 | Platform | When the Configuration Wizard is used to configure a database connection with an Azure AD password authentication on a domain-joined machine, the database configuration step no longer fails. |
| 02148084 | Platform | The default value for the WMI timeout has been increased to 30 seconds to avoid excessive timeouts. The centralized setting WmiExecutionTimeoutInMilliseconds can be used to change the default value. |
| 02159789 | Platform | Maintenance schedules configured to mute alerts or unmanage entities no longer fail to run after the SolarWinds Orion Module Engine service is restarted. |
| 02125486, 02150262 | Platform | Communication between the collector and the job engine on port 17733 no longer leads to port exhaustion. |
| 02149470, 02149782, 02152197 | Platform | When the installer is not able to validate the certificate, it now displays a more informative error message and provides a link to a Support article with instructions for resolving the issue. |
| 02126774 | Platform | Hardware health polling no longer fails because of a directory that was not removed during the upgrade. |
| 02143020 | Platform | When large environments have several nodes with WMI polling issues, additional worker threads are not created, fixing a memory leak with the Job Engine service. |
| 02094544 | Platform | When a node has been unmanaged, the SWIS remanage verb can be used to resume polling. |
| 02100993, 02124078, 02138006 | Platform | The SolarWinds SNMP Walk tool now uses the selected SNMPv3 authentication algorithm. It no longer uses only SHA1, which would cause the walk to fail with the following error on devices that required MD5, SHA256, or SHA512 authentication: Wrong Digests error |
| — | Platform | For new installations, the AdministrationService.Client.log file no longer shows an error related to incorrect installation parameters for the Web Performance Monitor Player. |
| 02096874, 02128157, 02160624 | Platform | Users with the Allow Account to Unmanage Objects & Mute Alerts permission can unmanage nodes even if they do not have the Allow Real-Time Polling permission. |
| — | Platform | An issue that caused entries in the top menu bar under Alerts & Activity and Reports to be reordered when the platform was upgraded to 2026.2 has been fixed. |
| 02104943 | Platform | One-time job creation and assignment now work correctly when URL normalization is performed by load balancers. |
| 01092175 | Platform | When text was copied into a Custom Properties field with hidden ASCII characters, it no longer causes issues with Alert Actions when the Custom Property is referenced. |
| 02119115, 02122152., 02155686 | Platform | The Platform Connect wizard no longer fails when SolarWinds Observability Self-Hosted accesses the internet through a proxy server. |
| 02160113 | Platform | Accessing SW1 from an additional web server no longer fails with the following error: A network error occurred. Please check your connection and try again. |
Deprecations
Windows Server 2016
Windows Server 2016 is deprecated as of 2026.2. It is still available and supported in the current release, but will be removed in a future release.
Unmanage Scheduling Utility
The Unmanage Scheduling Utility (Unmanage Task Editor) is deprecated as of 2026.2 and will be removed in a future release. To ensure continued support, schedule all new tasks using the web console Manage Schedules page. Windows schedules that reside on a standby server in a High Availability pool are not migrated by the Configuration wizard. Recreate them manually on the Manage Schedules page.
Apache Mesos
Apache Mesos container monitoring is deprecated and will no longer be available in a future release. Migrate your monitored environment to Docker or Kubernetes 1.23+.
Kubernetes 1.16 - 1.22
Kubernetes 1.16 - 1.22 container monitoring is deprecated and will be removed in a future release. SolarWinds recommends upgrading your cluster to version 1.23 or later, then re-adding the service in SolarWinds Observability Self-Hosted.
SQLServer 2016
SQL Server 2016 is deprecated as of 2025.2. It is still available and supported in the current release, but will be removed in a future release. Consider using SQL Server 2022 or later.
Network Atlas
Network Atlas is deprecated as of Orion Platform 2020.2. It is still available and supported in the current release, but will be removed in a future release. Deprecation is an indication that you should avoid expanded use of this feature and formulate a plan to discontinue using the feature. SolarWinds recommends that you start using Intelligent Maps in the SolarWinds Platform Web Console to display maps of physical and logical relationships between entities monitored by the SolarWinds Platform products you have installed. Starting with 2024.2, you can import Network Atlas maps to Intelligent Maps. See Import maps.
End of life
End-of-life milestones announced in this release.
| Version | EoL announced | End of engineering | End of life |
|---|---|---|---|
| 2024.2 | June 9, 2026: End-of-Life (EoL) announcement – Customers on SolarWinds Platform version 2024.2 or earlier should begin transitioning to the latest version of SolarWinds Platform. | July 9, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2024.2 or earlier will no longer actively be supported by SolarWinds. | July 9, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform version 2024.2. |
| 2024.1 | February 10, 2026: End-of-Life (EoL) announcement – Customers on SolarWinds Platform version 2024.1 or earlier should begin transitioning to the latest version of SolarWinds Platform. | March 12, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2024.1 or earlier will no longer actively be supported by SolarWinds. | March 12, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform version 2024.1. |
| 2023.4 | October 21, 2025: End-of-Life (EoL) announcement – Customers on SolarWinds Platform version 2023.4 or earlier should begin transitioning to the latest version of SolarWinds Platform. | November 20, 2025: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2023.4 or earlier will no longer actively be supported by SolarWinds. | November 20, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform version 2023.4. |
| 2023.3 | October 21, 2025: End-of-Life (EoL) announcement – Customers on SolarWinds Platform version 2023.3 or earlier should begin transitioning to the latest version of SolarWinds Platform. | November 20, 2025: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2023.3 or earlier will no longer actively be supported by SolarWinds. | November 20, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform version 2023.3. |
Reproduced from the official SolarWinds Platform 2026.2.2 release notes. Last checked 8 Oct 2026, 05:15 UTC.