Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Network Performance Monitor (NPM) > Network Performance Monitor (NPM) Training > Free SolarWinds Training Videos - NPM > Demonstration on upgrading NPM (v. 10.4 to 12.0) - Video

Demonstration on upgrading NPM (v. 10.4 to 12.0) - Video

Updated December 2nd, 2016


In this video we will show you the steps for upgrading an older version of Network Performance Monitor.  This upgrade walk-through begins with NPM 10.4 and upgrades through to NPM 12.0 following an upgrade path.


The next video in this series is not yet published.


  • Network Performance Monitor 10.4, 11.0.1, 12.0

Video Transcription

In this scenario, we will start from NPM 10.4 and bring it up to the latest version. This will be a stand-alone installation. If you are currently using NPM version 10.3 or earlier, we recommend that you perform a fresh installation. Before you begin, you should perform the following steps to upgrade successfully:

  • Review system requirements
  • Gather credentials
  • Run all Windows updates
  • Back up your database
  • Schedule the upgrade
  • Notify your company


For additional information, we recommend that you check out the “Upgrading the Orion Platform” video. Also, if you are planning to migrate your Orion Platform server, we recommend that you upgrade before going forward with the migration. For more information on this process, please watch “Migrating an Orion Platform Product Installation.” We will start the first upgrade scenario by going to and using the Product Upgrade Advisor to build our upgrade path.


For the purposes of this demonstration, we are using Windows 2008 R2 SP1. Our database is MS SQL Server 2008 R2. The product we are upgrading is Network Performance Monitor, version 10.4.  Because this is a stand-alone upgrade, we don't need to worry about selecting additional products. The two things to note here are:

  • it is compatible to move forward, and
  • these are the steps we need to follow.


In this scenario, we will upgrade to 11.01 first and then to 12. Due to changes in the application and the database, the upgrade path requires this two step process. You must upgrade to NPM 11 before moving on to NPM 12. The Upgrade Advisor provides links to the relevant downloads, so we can do it directly from here. If possible, we recommend that this process be completed from the server you're going to do the upgrades on. However, you do have the option to move the files over your network to the folders on the server.

  1. Before we run the installation, we need to make sure that the maintenance is current. We can check that from the SolarWinds License Manager. As you can see, we have plenty of time. However, if it was expired, we would need to apply the license before completing the upgrade.
  2. The next step is to open the Orion Service Manager and shut down everything. The Service Manager will also be upgraded during this process, so it needs to be closed.
  3. Next, we open the files that we already downloaded from the Upgrade Advisor. In this scenario, we are going to upgrade to 11.01 first.
  4. Right click on the file and select Run as Administrator.
  5. This notification tells us that a new version of .Net Framework is required. In order to continue with our upgrade, we need to click Install.
  6. At this point, a restart is required, so we will click Yes and wait until the installer returns us to the desktop.
  7. Whenever possible, the installer will continue the process right where it left off.
  8. The .Net Framework installation has been completed, and we will pick up from there. Sending usage statistics to SolarWinds is optional. For the purposes of this demonstration, we will un-check the box.
  9. We have already performed a backup of our database, so we can type Yes and click Next.
  10. We accept the license agreement and click Next.
  11. For this installation, we will select Enable QoE Later and click Next. Click Next again to start the installation.
  12. Once the installation is done, click Finish and the Configuration Wizard will launch automatically.
  13. Because we're upgrading, and not performing a fresh installation, the Configuration Wizard already has all the correct connection information.
  14. Just click Next,Next and Next again.
  15. Also, since we are not migrating, all these settings will stay the same.
  16. This message is just a reminder that we will be making upgrades to the existing website. Click Yes.
  17. Leave all the services selected and click Next.
  18. Verify the configuration summary and click Next.
  19. It's important to note that anytime we perform a stepped upgrade, we need to run the Configuration Wizard before upgrading to NPM 12. This is because there will be changes to the database, and these changes need to be completed before moving from version 11 to version 12. Once the Configuration Wizard is finished, we can move to the next step in the upgrade process.


Whenever you perform multiple upgrades, there is a lot of repetition. The steps for upgrading to NPM 12 are the same ones that we just went through for 11.01.

  1. We start by opening the Service Manager,  shutting down all the services, and then closing it.
  2. Next, we go to the downloads folder and run the NPM 12 installer.
  3. Once again, we are required to install the .Net Framework, and then restart the computer. The installer will pick up where it left off.
  4. Sending usage statistics is optional. Our database has been backed up. We accept the license agreement and click Next. And click Next again to start the installation.
  5. When the installation is complete, we click Finish and launch the Configuration Wizard.
  6. Because all our configuration settings are going to stay the same, we can just click Next through all of these and start the configuration.
  7. The configuration wizard is complete. At this point, we will do a quick, post-installation review just to make sure everything is working properly.
  8. We are going to click Finish and allow the Orion web console to launch.  


Once we log in, we see an introduction to the new UI changes. There is also a video tour available to help us take advantage of those changes. On the welcome page, we can see that the elements we need for our environment have been discovered and are being monitored. If we go to the Orion home page, we can see that our resources have been updated. If we click on one of our Cisco devices and go to the Node Details page, we can verify the last time it was updated. We could also check one of our additional polling engines by going to Settings > All Settings > Polling Engines. Here we see that the poller is responding and active, and that it updated just a few seconds ago. So it looks like our upgrade is successful.


This wraps up our demonstration of a stand alone upgrade to NPM 12. If you are planning to upgrade multiple SolarWinds products, please check out the next video in this series.



Last modified