Planning Orion Migration to new servers - will changing the domain cause any issues?

Hello Thwack -

I have gone over the following for migrating Orion/SW modules to new servers.

Migrate SolarWinds products to a new server with a new IP and hostname - SolarWinds Worldwide, LLC. Help and Support and SolarWinds Upgrade Guide - SolarWinds Worldwide, LLC. Help and Support

I plan on moving everything to a new domain as well for management purposes and wanted to see if that will cause any issues at all? Right now Orion communicates with nodes in different domains and just wanted to check for any odd things that may happen with a domain change. SQL should not care but I wanted to check things. Also if anyone has any other hints or ran into any issues let me know. I plan on doing this probably around the first week of August.

Thanks!

Find more posts tagged with

database performance analyzer

orion migration

domain

Accepted answers

All comments

mbird

I switched to a new domain in a similar fashion and I didn't have any problems.

ekis

A SolarWinds guide video says "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."

Reference SW Article URL : Migrating an Orion Platform Product Installation - Video - SolarWinds Worldwide, LLC. Help and Support

This sounds like the functionality of SW services is not domain-dependent.

mbird

Didn't appear to be, however I found a lot of old stuff that then had to be fully qualified because originally it wasn't. Those were fun to track down but this deployment has been in place for many years so there's always a surprise or two lurking.

d09h

Do you use any domain service accounts? Do you authenticate users via AD?

martian_monster

Yup saw that. I have been over as much of the documentation that I can find and made notes. Hoping to find any gotchas that aren't covered in the documents.

martian_monster

Yup we use AD authentication for SolarWinds and my AD guy said that passing authentication between these domains should not be a problem.

d09h

Will IP addresses change? If so, will monitored devices allow queries from new IPs? Will firewalls along the way allow new IP addresses? Has any duct tape been put in place that can come out once older servers aren't needed? How long will you have access to the old servers? Might have to go back to them to locate stuff or to sanity check. Do you have any host files or persistent routes on the original servers? (One type of duct tape I referred to.) Are you recreating views manually?

martian_monster

The IP will be changing. There are contracts that allow communication between the different domains - right now I do monitoring in the all of the different domains so there is communication but I will be sending over the list of ports that are needed for SolarWinds to work just to make sure everything will work to my team members that control all things routing. The old servers will be up for a bit once I get this move done I need to move the database performance monitor that is also running off this server. I hope there are no hosts files hiding anywhere but I now am going to check for that I love trying to troubleshoot something and you finally realize its a hosts file that is making things work. I have been creating Dashboards for different groups here - SQL servers for DBAs, server groups for Application owners, Exchange servers, etc are those what you are talking about? I also have done some reporting so I know I may have to grab a few folders there too.