When DPAIM users with an SRM license attempt to create a relationship between a database and a storage object, they no longer see a message that SRM is not installed, and the relationship can be created.

When custom properties used in alerts are created on a different SolarWinds Platform server, the associated column in the All Active Alerts page in EOC is not blank when viewed by an account that did not add the associated server to EOC.

The method for updating the node mapper cache has been improved to reduce the load on the SolarWinds Platform database in large deployments.

Running a compliance rule remediation script with the Execute Script in Config Mode option selected no longer uploads the config instead of executing the remediation script.

When Real-Time Change Detection sends an email notification, users on domains other than the Google-hosted SMTP domain now receive the emails.

If a SolarWinds Platform user account with an NCM role is part of an AD group, the NCM role is recognized and the user is able to access NCM functionality in the API.

After you remove a policy report, the new Config Summary dashboard shows the correct number of policy violations.

The Last Inventory column on the Last Inventory of each Device report shows the correct time.

The policy cache is no longer refreshed each time services are restarted.

When a firmware upgrade operation is performed for certain types of devices, the password for the SCP server is no longer displayed in plain text in the history log or email notifications.

Adding nodes to a compliance policy by selecting them from a list works correctly, even if the deployment includes a large number of nodes.

In environments that upgraded from versions earlier than 2020.2.1, database maintenance no longer fails with an error similar to:

ERROR SolarWinds.Data.DatabaseMaintenance.StandardTableHandlerDAL - Failed to execute procedure: dbm_InterfaceAvailability_HourlyToDaily System.Data.SqlClient.SqlException (0x80131904): Procedure or function dbm_InterfaceAvailability_HourlyToDaily has too many arguments specified.

False alerts for failovers on SD-WAN Edge devices are no longer issued.

Queries related to thresholds have been optimized to prevent deadlocks in the SolarWinds Platform database.

The new version of the Wireless Summary View page displays the client's name correctly.

When you monitor a Microsoft Azure or AWS Cloud Account with virtual network gateways, the Virtual Network Gateways page displays the virtual network name.

When a related node is added more than once with different polling engines, the Routing Neighbors widget and Routing Table widget display the correct data instead of the following message:

There was an error processing the request.

Editing interfaces on nodes assigned to a polling engine in a different domain is successful and no longer returns an Unexpected Website Error.

It is possible to add a Viptela orchestrator with the IP address when the IP address cannot be resolved to the host name.

Polling a Cisco ACI device via API no longer fails with the following error:

Test failed: Response status code does not indicate success: 401 (Unauthorized).

If topology layer 2 pollers are assigned to a node, Topology Layer 2 is selected on the List Resources page.

There is no longer a substantial delay in detecting a failover on Meraki devices.

Interface polling no longer stops if an interface has a different ObjectSubType than its parent node.

When an interface-to-interface topology connection is available for two nodes on a map, the map displays the connection type correctly.

The Multiple Universal Device Pollers Chart loads faster.

Charts use consistent colors to indicate receiving and transmitting data.

An issue that could result in data being processed with the wrong template is fixed. Using the wrong template could result in invalid data or a disruption to services.

An issue was fixed that, in some environments, caused upgrades to fail with the message NetFlow Website Failed.

When an IIS Server node is monitored by a Remote Collector, a test connection with valid credentials from AppInsight for IIS no longer fails.

When the polling method is changed from WMI to Agent or from Agent to WMI, polling continues and application statuses are correct.

In a large deployment, opening the Assigned Application Monitors tab on the Manage Application Monitor Templates page no longer displays a dialog with the message Page Unresponsive.

Special characters in the SolarWinds Platform database such as a single quote (') no longer cause errors during database configuration that prevent the upgrade from completing.

If a VM tag is removed from an Azure Cloud Account, the VM is no longer displayed on the Cloud Summary page as being monitored.

After an upgrade, PowerShell and AppInsight monitors are functional. Users no longer need to manually update a configuration file to use these monitors.

*Azure Kubernetes Service (AKS) containers can now be monitored.

Asset Inventory correctly parses the date and time. The Firmware widget displays the date correctly, and the log does not contain errors such as Can't parse DateTime value.

The Access Point Details page displays the access point name correctly.

When no ports are available on a node, job processing continues without the error Exception in GetVlansWithFilter.

A large number of VLANs on a node no longer leads to an error.

Deleted nodes no longer cause the Device Inventory page to load with an error.

Nutanix Controller VM (CVM) credentials can be added to Nutanix Clusters.

Nutanix virtual machines are mapped to nodes correctly.

If a VM is renamed, the reported snapshot count and snapshot storage is correct.

When a virtualization entity is added to an additional polling engine, management actions finish successfully.

SolarWinds no longer displays invalid messages saying that the license limit is exceeded. This was caused by attempts to verify licenses before they were loaded.

Polling an Avaya node for VoIP Call Managers information no longer returns errors.

Database maintenance no longer fails with a message similar to the following:

Violation of PRIMARY KEY constraint 'PK_SipTrunkCallActivity_Hourly'. Cannot insert duplicate key in object 'dbo.VoipCCMSipTrunkCallActivity_Hourly'.

CMR data is updated as expected even if all call managers are assigned to additional polling engines.

The number of phones in the CallManager Stats widget matches the number of phones in the Connected Phones widget and the Connected Phones report.

Database tables no longer include non-trusted foreign keys.

When an Avaya Call Manager is added to the SolarWinds Platform and then removed, the VNQM TCP server no longer attempts to poll them, which resulted in messages such as the following in the IpSla.BusinessLayer.log:

ERROR BusinessLayer.TcpServer AcceptClient - [_ctor] Data is not consistent enough to proceed: Call manager (Id: -1, Ip: 172.28.192.152, NodeId: -1, EngineId: 9)

VoIP and Network Quality Manager functionality is not affected when nodes are assigned to an additional polling engine.

*Juniper RPM polling no longer fails for some operations.