Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Archive > 2018Jan2 - Deletes > Reassign SolarWinds nodes

Reassign SolarWinds nodes

Table of contents
Created by Alexander Aguilar, last modified by Kevin.Swinson on Jan 02, 2018

Views: 783 Votes: 0 Revisions: 5

Overview

This article provides steps to re-assign a SolarWinds node from a VM to a physical server. The SolarWinds Database is on a separate physical server already.

Environment

  • All NPM versions 
  • All SAM versions 
  • All NCM versions

Steps

1. Prepare the Server Prior to Maintenance Window.
    a. Configure the Physical Server, different IP.
    b. Configure NPM, SAM, NCM and connect to TEST Database- this will be Trail Version only (install the same     versions).

 Note:  Login to your Main Orion system with the local Administrator account (do NOT use a Domain Admin account) to                 avoid GPOs and any other potential permission issues.

 

2. Deactivate licenses and turn off the production server.

 

3. Go to the SQL server and running this query will reset the Subscriptions used by some of the SolarWinds services:
Note: If the software is migrated or hostname/IP Address is changed on the Orion server orphaned entries can be left           behind and cause issues with the web console.

The following should be run in the order listed below since there are some key constraints:
    a. Stop Solarwinds services.
    b. Run the following query:

delete from dbo.PendingNotifications
delete from dbo.SubscriptionTags
delete from dbo.Subscriptions

     c. Restart the SolarWinds services.
              
You can run this on the Orion Database Manager or SQL Studio.

 

4. Change the IP of the new server to reflect the IP you want to use.

5. Reboot the machine.

6. Run the configuration wizard on the new physical server to attach to the production SQL instance.

Notes:

a. Login to your Main Orion system with the local Administrator account (do NOT use a Domain Admin account) to     avoid GPOs and any other potential permission issues.

b. Exclude the following from AntiVirus software:

  • C:\ProgramData\Microsoft\Crypto folder.
  • C:\Windows\Temp
  • C:\ProgramData\SolarWinds

c. Update DNS entries for show the new information.

d. Update DHCP reservation to show the new MAC address for the retained IP address.
If you need to upgrade your software after the install you can follow the SolarWinds Product Upgrade Advisor.

 

You should be on the new physical box and online.

 

 

 

Last modified

Tags

Classifications

Public