Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion Platform install and upgrade gotchas

Orion Platform install and upgrade gotchas

Updated December 10, 2018

Anytime you install or upgrade Orion Platform products, you should look over the gotchas. These lists provide the latest information based on Orion Platform and product version.

Orion Platform gotchas

Review and consider these gotchas when installing and upgrading Orion Platform products.

Installation gotchas

  • Log Manager for Orion (LM) replaces existing legacy syslog and trap services, but only provides a subset of the legacy functionality. To uninstall LM and restore the legacy syslog and traps services, see this article. For additional information, see the LM release notes.
  • Orion Platform 2018.4 and later no longer supports Windows Server 2012 or 2012 R2 and SQL Server 2012.
  • After Orion Platform 2017.1, future releases will no longer support Windows OS 2008 and 2008 R2 and Microsoft SQL Server 2008 R2. Orion 2017.1 products (NPM 12.1, SAM 6.4, etc) currently supports these versions. SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience.
  • When upgrading to Orion Platform 2017.1 or later, 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 to 2017.1 with custom menus, you can not see the Performance Dashboard link in the menu. For details, see this article.
  • When upgrading Orion 2016.2 products with Dell Carbon Black installed, we recommend stopping or removing Carbon Black. This security product causes issues with MSMQ starting. For details, please see this article.
  • If your Orion Platform 2016.1 product and DPA are installed on the same server, follow this article before upgrading the Orion Platform product. 
  • Orion Platform 2016.1 and later products have new port requirements: 5671 (Rabbit MQ messaging), 17791 (agent communication to 2008 R2 SP1), 17778 (SW Information Service, agent communication to 2012).
  • Orion Platform 2016.1 and later products no longer support Windows Server 2003, 2008, 2008 SP1, or 2008 R2 without SP1.
  • If you have edited resource properties, the All Groups resource may be empty after upgrading Orion Platform 2016.1 products. This includes NPM 12 and SAM 6.2.4.
  • When upgrading Orion Platform 2016.1 products, 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. All regular functionality is unaffected by the issue. Orion Platform 2017.1 products resolve this issue.

Upgrade gotchas

  • If you have written your own code, such as changing SolarWinds .css files or adding .js files, or been directed to make changes by Support, the code may be overwritten during the upgrade. You can learn more about upgrading with custom code here.
  • Always check that you have enough hard drive space for zipped and unzipped installers. One unzipped installer could consume a couple GBs of space.
  • If you are 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, saving or migrating your data. SolarWinds Support can provide the best advice for these upgrade scenarios.
  • If you have 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 server before you can re-enable your HA pools. See instructions in this guide.
  • If upgrading to NTA 4.X, you will need to install a new Flow Storage Database. For details on installing the Flow Storage Database, see this information. If you have questions, see this FAQ for upgrading NTA 4.X.

Need more documentation?

SolarWinds Install Guides by product. These guides are legacy install guides.

Last modified

Tags

Classifications

Public