Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Migrating an Orion Platform Product Installation - Video

Migrating an Orion Platform Product Installation - Video

Updated July 18th, 2016


This video demonstrates the steps to successfully migrate your Orion installation. Additional walk-through guides with prep information and checklist instructions are in the Related Resources section.



  • Orion Platform 2016 and above including NPM v12 and SAM v6.2.4.


Video Transcription

Today we'll be walking through the steps required to successfully complete a software migration. These steps apply to all SolarWinds products on the Orion® Platform, including Network Performance Monitor, Server & Application Monitor, Network Traffic Analyzer, and Network Configuration Manager. We'll also touch on some tips and common gotchas.

These steps yield the best results for a single product migration. If you have multiple products installed, more advanced migration processes are documented at


Before you begin a migration, there are a few steps you should take to prepare. 

First, gather the SQL Server® details and credentials for where your Orion Platform database is stored. You will need them later.
If you don't know your SQL credentials, a useful workaround is to first back up the Program File: x86\solarwinds\orion\SWNetPerform.db
Next, migrate this to the new install folder and it will auto populate SQL Server, the Orion Platform database, and credentials once the configuration wizard runs.

Where possible, install products before you join your server to your domain. This may yield better results where some environment's GPOs heavily lock down a server once it has joined the domain.

You'll also want to take note of the version of Orion Platform you are currently running on your existing server. Download this same version to the new server from your customer portal. If you plan to upgrade as well as migrate,upgrade the software on your existing server before proceeding with the migration where possible.

The latest Orion Platform product versions store reports and scheduled tasks directly in the Orion Platform database. To simplify the migration, first upgrade your old server before migrating.

Otherwise, if migrating old versions of the Orion Platform, you will have to manually migrate any customized reports using the Report Writer Tool and any Windows® Task Scheduler jobs to the new server. To do this,open Program Files\Solarwinds\Orion. Make a backup of the  \Reports Folder, and any folder structure beneath this.

It is especially important to upgrade software to the latest version if you own both Network Performance Monitor and Network Configuration Manager. The reason for this is these products now utilize the same database and the same job scheduler. This means you won't have to migrate Windows Task Scheduler jobs since all jobs are now on the Orion Platform database.

You'll find more information about upgrading your server at 

Now it's time to get started with the migration!

First, park the license from your old server, so that it will be ready for you to use later on your new server.
To do this, you'll need to use the License Manager Tool. This can be set up on your server from the start menu. Run the SolarWinds® License Manager Setup tool. If you're asked to update license manager when you run it, please do so.

The License Manager tool makes parking your license very easy. Simply select the license, and click Deactivate. The license will automatically reappear on your customer portal. If you have any trouble with this step, please contact our Customer Service team who can assist you further.

Next, uninstall the Orion Platform from your old server. It's important to do this now, since it's not recommended to allow two main polling engines to write to the same database at the same time.

Some users choose to keep their old and new servers running concurrently for a few days before uninstalling the old server. This provides the added benefit of zero downtime. Please contact SolarWinds Support for instructions on how to do this.

Now that the old server is gone, it's time to get your new server up and running.

Install the Orion Platform on your new server using the same version of the product that you were running on your old server. As mentioned previously, it's not recommended to migrate and upgrade in the same action.

This process will take some time; just be patient and follow the prompts when necessary.

You will be prompted to license the product during the installation. This will pull your newly parked license back from your customer portal and install it on your new server. Enter your details, including the license key for your product. You can find this on the customer portal, under License Management.

If you are prompted to install missing IIS components, click Yes and the Configuration Wizard will install them for you.

Run the configuration wizard on the new server, connecting to the database using the SQL Server credentials you noted during your preparation phase.

You will see this error telling you to select an existing database rather than create a new one. This error is expected during a migration because you are using the database from the previous instance. Just click Okay.

Now click the drop down menu and select your existing database and click Next. Continue to click Yes or Okay through the next few dialog boxes.

Enter your existing account credentials for the database you are using and click next.

Again, click Yes through the next few dialog boxes.


You're almost there!
Just a few configuration steps left to finalize your migration.

If you have any customized reports or a custom logo for your website, you'll need to copy these back into place on your new server.

Also, if the IP address of your new server does not match the IP address of your old server, you will need to remove the previous polling engine from the database.

 And finally, if you changed the IP Address of your server, you may need to reconfigure your network devices to send syslogs, traps and NetFlow data to the new IP address.

First, open Orion Service Manager. Next, stop all SolarWinds services except the SQL Service and close the Orion Service Manager.

Next, open the database manager, click Add Default Server and expand and locate the SQL Server in the tree.

Expand the SQL Server, scroll down to the engines table, right click, and then select Query Table. Click Execute Query to display the table entries and then select Enable Table Editing. Locate the rows of the polling engines you are removing and adding, and make note of the engine ID and the IP address of your old and new primary polling engines.

Right click the top left cell in the old polling engine row and click Delete the Selected Row. Click Yes when prompted to confirm.

Execute the query again to display the table entries to verify the old polling engine has been removed.

Then, restart services. You'll want to keep the Database Manager open for the next step.

With the Database Manager open, right click your database and click New Query. Enter this query and click Execute Query to reassign the nodes.To avoid any errors, you should type in this query rather than copying and pasting it.

For all additional polling engines and website engines, you may want to verify the engine ID or IP address correctly updates with the new server for the these tables.

Click Execute Query to update all nodes. To verify, open the Web console and click Settings and Manage Nodes. Click Group By and select the polling engine. Then you'll select the new polling engine to see all the assigned nodes.

Wait 10-15 minutes to allow a full polling cycle to complete, then check the graphs and charts in your nodes to confirm your newly migrated polling engine is now polling successfully.

If you'd like to know more about migrating your software, or more information or assistance with any of our products, visit the Success Center at


Last modified