Documentation forSolarWinds Platform Self-Hosted

SolarWinds Platform 2025.1 release notes

Release date: February 11, 2025

Here's what's new in SolarWinds Platform 2025.1.

Learn more

New features and improvements in SolarWinds Platform

Last updated:

Modern dashboard improvements

  • NOC Mode: Use the Network Operations Center (NOC) views to see a single-page view of critical statistics to fit on TV screens or mobile devices. Multiple tabs rotate automatically.

  • Dark Theme for NOC views: Display Network Operations Center views in the dark mode.

  • Actions Menu: Access actionable items from a new menu. The menu contains items for easier interaction with dashboards.

  • Pagination in Table widgets: Configure the number of items per page for queries that return a long list of items. See Customize pagination and scrolling.

Intelligent Maps improvements

  • Edit destination when clicking on an object.

  • New default setting page.

  • Improved handling of nested maps in the conversion tool.

WinRM support for polling Windows nodes

Windows servers now support both the modern WinRM protocol and the older WMI (DCOM) protocol. By default, a WinRM connection is attempted first. If that is not possible, the connection falls back to WMI (DCOM). You can choose which protocol to use. See Configure WinRM polling.

Alerting improvements

  • A new widget with a table view of all items affecting an entity status was added to the Active Alert Details view.

  • When editing an alert, the Trigger conditions page displays both all objects and immediate triggers when you click Show list.

  • When editing an alert action, credentials are offered. Only Administrators can create and assign credentials. See Required permissions for setting up alert actions.

Reporting improvements

  • An option to ignore certificate errors when exporting reports into Excel/CSV was added.

  • An option to use regional settings for reports exported in PDF was added.

    See Troubleshoot reports.

DoDIN improvements

  • The mandatory notice on the login page is displayed for users who log in using CAC (MFA).

  • The logout notification was extended to advise users to close the browser.

Other improvements

  • Configure the SNMP version to be automatically selected in your wizards. By default, SNMPv3 is preselected for fresh installs. For upgrades, the default version is SNMPv2. See Set the default SNMP version for wizards.

  • Support for customizing the locale for pdf reports.

  • Support for Windows 2025 both as a platform to install products on and for monitoring.

  • Added peak memory usage (percent) for both Windows and Linux servers.

  • Support for changing the calculation of physical memory volume utilization on Linux nodes polled via SolarWinds Platform Agents was added. See this article for details.

Fixes

Last updated:

Case number Description
01775614, 01797044

If the National Institute of Standards and Technology (NIST) does not include data about a device type in the Common Platform Enumeration (CPE) Dictionary, the missing data no longer prevents SolarWinds Observability Self-Hosted from identifying firmware vulnerabilities that affect the device.

01733199

Searching and filtering on the All Active Alerts page works as expected.

01614539, 01760243

The percent usage (disk, volume, memory) of monitored components no longer shows values over 100%.

01613397

When the delayed trigger condition is used, false positive alerts are no longer triggered after the Alerting Engine service is restarted, and alerts are triggered only when all conditions are met.

01724267

When a dashboard has a limitation defined, the Intelligent Map widget displays the entities as expected.

01726459

After you edit an anomaly-based alert, the Anomaly-based alerts Details page no longer fails to open, and previously selected entities and entity type are displayed as expected.

01496748

The Management resource for Node Details and Volume Details widgets no longer disregards custom LP translations.

01680302

Configuring alert actions no longer requires different permission levels for setting up credentials.

01707822

Intelligent Map highlights the traffic value that exceeds a configured threshold.

01613861

The SNMP fast status poll no longer incorrectly updates the PercentLoss value.

01716485

The out-of-the-box alert Node not polled in last 10 minutes works as expected and the column LastSync is no longer updated if polling does not work.

01682272, 01749347

If a polling engine is upgraded to 2024.4 or later but agents remain on older version, CPU data is not missing for agent-monitored Windows servers.

01720933

Device details for Westermo devices show the correct vendor information.

01688372, 01760260, 01797443

The zoom function in the Intelligent Map works as expected.

01678985

When you configure an alert to send an email where the variable ${N=SwisEntity;M=NodeStatusRootCauseWithLinks} is used, the Child Entities section in the email notification includes URLs for the detail pages.

01680938

Members of Windows Group Account can change the Hardware Health Sensor temperature units.

01692359, 01716314

Exporting the Orion Group custom property no longer fails with an error Error: One or more errors occurred.

01504511

By default, users with account limitations cannot view a global alert on the Active Alert Details page unless they created the alert. The Centralized Setting HideForeignGlobalAlertsToLimitedAccounts can now be used to change the default behavior.

To allow users with account limitations to view any global alert on the Active Alert Details page, go to Centralized Settings and change the value of HideForeignGlobalAlertsToLimitedAccounts to False.

01581882

Database types are no longer mismatched and causing performance issues.

01598650

When the polling method changes, CPU and memory pollers are automatically imported into the database as expected.

01541887

When you select the WMI protocol as the preferred polling method, SolarWinds Platform no longer tests all SNMP credentials against WMI nodes, causing network discovery to take longer than expected.

01440622, 01573956, 01781557

When adding Nodes with SNMPv3 with an MD5/AES256 configuration, the Test connection no longer fails with an error INFO SolarWinds.Orion.Core.BusinessLayer.CoreBusinessLayerService - (null) SNMP credential test finished. Success: False.

01560929

When installing scalability engines, the Configuration Wizard no longer fails with the following error related to the existence of Rabbit MQ service: Error starting Service (RabbitMQ), Service RabbitMQ was not found on computer '.'.

01528599

Details for value and custom property in Modern Dashboards no longer overlap.

00850506, 00711183, 01122007, 01541102, 01498410, 01512730

List Resources on Agent node show the interface selections as expected.

01527588, 01537151

The Active Diagnostics test no longer calculates the memory size incorrectly for the 64-bit SQL server.

01794548, 01488531, 01582664, 01683005, 01521268, 01735702, 01708561, 01764686, 01788262

When you uninstall an additional polling engine, RabbitMQ queues are deleted as expected.

01330824, 01742235

Existing Intelligent Maps created without a container are available in the Entity Library, and they can be updated, saved, and added to other maps.

00086954, 00636209, 01438471, 01732632

The date and time are formatted correctly in custom reports.

01269370

The Set of objects filter in the Add Alert Wizard works as expected.

01089240, 01639273

When you have groups over entities with the status of Up and Inactive with group status calculation of Best, the status calculation is reflected correctly.

01785463, 01785499, 01786391, 01787163, 01787867, 01790533, 01791274, 01799572

When you open the Deployment Health tab from an additional web server, health checks run correctly.

01787803, 01797738

WMI job issues that caused JobEngine to use too much CPU and memory in environments with heavy WMI polling were addressed by configuring WMI polling jobs to run outside of in-process workers by default.

01791756, 01800049

Upgrading the SolarWinds Platform log database no longer fails with an error similar to the following if the database is contained:

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in the equal to operation.

01761260

Using a date format other than MM/DD/YYYY no longer prevents the discovery of a Power Control Unit (PCU).

01803929

When a subgroup is added to a map, the All Groups widget and Manage Groups page no longer display the subgroup as both a root level group and a subgroup.

01790612, 01795074

The Incident Number column on the All Active Alerts page displays the number of currently active incidents associated with an alert. It no longer includes incidents that occurred in the past and are no longer active.

01788280

When you select the $Name variable under Map name format, you can save the map definition.

01778801

Information that should not be available to a user because of limitations is no longer exposed in certain situations, such as a failed service initialization on an unstable database connection.

01783597, 01787060

Duplicate device types for FortinetFortiManager Orchestrator devices in the SolarWinds Platform database are removed. This situation no longer causes upgrades to fail with the following message:

Database configuration failed: Error while executing script- Violation of PRIMARY KEY constraint 'PK_DeviceTypeViews'. Cannot insert duplicate key in object 'dbo.ViewsByDeviceType'. The duplicate key value is (FortinetFortiManager Orchestrator). The statement has been terminated.

01798044, 01802014

When the SolarWinds Platform database is an Azure SQL instance, you can authenticate with a Microsoft Entra ID (previously Azure AD). The Configuration Wizard no longer fails with a message such as:

Services configuration failed: Status(StatusCode="Unavailable". Detail="Error starting gRPC call. HttpRequestException: An error occurred while sending the request. WebException: Unable to connect to the remote server SocketException: No connection could be made because the target machine actively refused it". DebugException="System.Net.Http.HttpRequestException: An error occurred while sending the request.")

01570173

The custom Trap rule action Change the status of an interface changes the status as expected when the trap is received.

01591806, 01761103

When the certificate store contains more than one SWI-Orion-Agent certificate that can be used by the Job Engine to encrypt WCF communications, the Job Engine no longer fails with the following error: 

FATAL SolarWinds.JobEngine.ServiceProcess.SolarWindsService - (null) An error happened in Start System.ArgumentException: It is likely that certificate 'CN=SWI-Orion-Agent (22409EE3-F4B9-4B88-8957-677BA409422C)' may not have a private key that is capable of key exchange or the process may not have access rights for the private key. Please see inner exception for detail.

01790326

When a device with a removable disk (floppy or compact disk) is polled and no disk is inserted, a warning is not logged. In addition, the Volume Space Used, Volume Space Used, and Volume Space Available are shown as 0 instead of -2.

01735730, 01761103, 01848027

When the Job Engine starts, it ensures that multiple SWI-Agent-JobEngineService certificate do not exist. If multiple certificates exist, they are deleted and a new self-signed certificate is generated. Multiple certificates can cause issues such as metrics not being collected.

01237858, 01353411, 01738302

A condition that caused the following exception no longer occurs:

Exception Info: System.NullReferenceException
   at SolarWinds.Orion.Feature.Client.NonBlockingFeatureClient.RefreshCacheOnTimer()
   at SolarWinds.Orion.Feature.Client.NonBlockingFeatureClient.<.ctor>b__8_0(System.Object)
   at System.Threading.TimerQueueTimer.CallCallbackInContext(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, 
      System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, 
      System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()
   at System.Threading.TimerQueue.AppDomainTimerCallback(Int32)
01799539, 01800546

Forwarding a significant number of syslog and trap messages per second with spoofing no longer results in some messages not being sent, high CPU and RAM usage, and errors such as the following in logs:

ERROR SolarWinds.Orion.LogMgmt.RuleProcessing.LogRuleTester - Failed action result
ERROR SolarWinds.Orion.LogMgmt.LogServices.Common.Util.UdpPacketPcapSender - Failed to forward spoofed packet using destination ip xx.xxx.xx.xx and spoofed source ip xx.xxx.xx.xx

01787586

If the language for the browser is changed, reports with a relative time period selected (for example, Last Week) show data from the correct date range whether you view them in the browser or export the report to a PDF document.

01599016, 01790390

Locking issues that could result in macros not being parsed correctly or other alert failures have been resolved.

01729405, 01756161

The Event log no longer includes erroneous audit event messages saying that a user changed an account.

01783820, 01790058

Running the SolarWinds Platform installer for versions 2024.3 and earlier no longer returns the error Object reference not set to an instance of an object.

01777747

The Node Details widget is no longer blank when the node category is null.

01800472

Exporting a modern dashboard no longer fails with the following message:

Invalid object name 'DashboardGroupItem'.

01807543

When you edit an Intelligent Map, the points connect to the correct locations.

00742942, 00771373, 00827562, 00833592, 00834704, 01468796

If a map is added to a group and a user account has a limitation associated with that group, the user is no longer prevented from viewing the map or from seeing it in the list of available maps.

01072152, 01801035

When a custom property has a value of Unknown, adding a limitation that uses the custom property no longer fails.

N/A

For subscription licenses, the License Details page shows the correct number of days left in the subscription.

CVEs

Last updated: 2/7/2025

SolarWinds would like to thank the security researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.

SolarWinds CVEs

CVE-ID Vulnerability Title Description Severity Credit
CVE-2024-52612 SolarWinds Platform Reflected Cross-Site Scripting Vulnerability The SolarWinds Platform is vulnerable to a reflected cross-site scripting vulnerability. This was caused by an insufficient sanitation of input parameters. This vulnerability requires authentication by a high- privileged account to be exploitable. 6.8 High Anonymous
CVE-2024-52606 SolarWinds Platform Server-Side Request Forgery Vulnerability The SolarWinds Platform is affected by server-side request forgery vulnerability. Proper input sanitation was not applied allowing for the possibility of a malicious web request. 3.5 Low Anonymous working with Trend Micro Zero Day Initiative
CVE-2024-52611 SolarWinds Platform Information Disclosure Vulnerability The SolarWinds Platform is vulnerable to an information disclosure vulnerability through an error message. While the data does not provide anything sensitive, the information could assist an attacker in other malicious actions. 3.5 Low Vicky Malekar, Ravi Khanchani and Techsa SolarWinds Team.

Third Party CVEs

CVE-ID Vulnerability Title Description Severity
CVE-2024-6119 OpenSSL Denial of Service Vulnerability Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process. Impact summary: Abnormal termination of an application can a cause a denial of service. Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an `otherName` subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program. Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address. TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. 7.5 High
CVE-2024-5535 OpenSSL Buffer Overread Information Disclosure Vulnerability Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available. 9.1 Critical

Installation or upgrade

Last updated:

For new SolarWinds Platform deployments, download the installation file from the SolarWinds Platform product page on https://www.solarwinds.com or from the Customer Portal. For more information, see Get the installer.

To activate SolarWinds Platform in an existing SolarWinds Platform deployment, use the License Manager.

For upgrades, go to Settings > My Deployment to initiate the upgrade. The SolarWinds Installer upgrades your entire deployment (all SolarWinds Platform products and any scalability engines).

For more information, see the SolarWinds Platform Product Installation and Upgrade Guide.

For supported upgrade paths to 2025.1, see Upgrade an existing deployment.

Known issues

Last updated:

Recent search results are missing

When you click the search icon in the top right corner of the SolarWinds Platform Web Console, the search bar works as expected but recent search items are not available.

Resolution or workaround: Recent searches will be added in a future release.

End of life

Last updated:

Version EoL announcement EoE effective date EoL effective date
2023.1

February 11, 2025: End-of-Life (EoL) announcement – Customers on SolarWinds Platform 2023.1 should begin transitioning to the latest version of SolarWinds Platform.

March 13, 2025: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform 2023.1 will no longer be actively supported by SolarWinds. March 13, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform 2023.1.
2022.4 June 4, 2024: End-of-Life (EoL) announcement – Customers on SolarWinds Platform 2022.4 should begin transitioning to the latest version of SolarWinds Platform. July 4, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform 2022.4 will no longer be actively supported by SolarWinds. July 4, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform 2022.4.
2022.3 February 6, 2024: End-of-Life (EoL) announcement – Customers on SolarWinds Platform 2022.3 should begin transitioning to the latest version of SolarWinds Platform. March 7, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform 2022.3 will no longer be actively supported by SolarWinds. March 7, 2025: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform 2022.3.

SolarWinds Platform 2025.1 supports upgrades from version 2022.3 and later. For more information, see Supported upgrade paths.

See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier SolarWinds Platform versions, see SolarWinds Platform release history.

End of support

Last updated:

This version of SolarWinds Platform no longer supports the following platforms and features.

Type Details
  • Centos 6
  • Red Hat Enterprise Linux 6, 7
  • SuSE Linux Enterprise Server 11
  • Ubuntu 14.04
These operating systems reached End of Life and are no longer supported by SolarWinds Platform Agents.

Deprecation notice

Last updated:

The following platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features.

Type Details
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.4, you can import Network Atlas maps to Intelligent Maps. See Import maps.

Legal notices

© 2025 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.