From UDT 3.3, UDT no longer supports Windows OS 2008 and 2008 R2 and Microsoft SQL Server 2008 R2. For more information, see End of support notices.
Users with UDT 3.2.3 must first upgrade to UDT 3.2.4 before being able to upgrade to UDT 3.3.
When upgrading, if you added a site binding to a host name before you upgrade, you must bind the Orion Web Console to a fully qualified domain name (FQDN). See this article.
When upgrading with custom menus, you cannot see the Performance Dashboard link in the menu. For details, see this article.
From UDT 3.3, the Alert Manager application has been deprecated and removed. Please use the web-based Alert Manager through the Orion Web Console to create and manage alerts. For more information, see End of support notices.
When upgrading an Additional Poller, you may receive this error :"The license we have for Orion Scalability Engine is outdated". See this article for details to resolve.
If you have edited resource properties, the All Groups resource may be empty after upgrading.
When upgrading, using the group by feature for custom properties may return no results, and the data loading may hang or not complete. All regular functionality is unaffected by the issue.
Always upgrade NPM first if you have it installed. NPM includes platform features to support all Orion products.
If you have SAM without NPM, upgrade SAM first. SAM includes platform features to support all Orion products.
Orion Platform 2018.4 products are no longer compatible with Windows Server 2012 and 2012 R2.
Orion Platform 2018.4 products are no longer compatible with any version of SQL Server 2012.
If you wrote your own code, by changing SolarWinds .css files or adding .js files, or were directed to make changes by SolarWinds Support, the code may be overwritten during the upgrade. See Upgrading if you have custom code.
Always check that you have enough hard drive space for zipped and unzipped installers. One unzipped installer can consume several GBs of space.
During your upgrade, use the Scalability Engine Installer. If you use downloaded installers or the installer bundle, you must install one product and version at a time. The versions must match between the main and additional polling engines or you will receive a Database Configuration Failure Error.
If upgrading from a very early or End of Life SolarWinds product version, you may want to install a new product instead of performing an upgrade or migrating data. SolarWinds Support can provide the best advice for these upgrade scenarios.
If you enabled SolarWinds High Availability, you must disable High Availability before you can upgrade. You must have the same versions of SolarWinds products on your primary and secondary servers before you can re-enable your HA pools. See Upgrade with HA.