Install NPM/SAM/WPM on new server and migrate NPM to the new server at a later date?

hqn121

So we have currently have NPM installed on a server and recently purchased SAM and WPM. We are building out a new environment and need SAM/WPM up as quickly as possible. Would there be any issues with installing NPM/SAM/WPM and configuring SAM/WPM first. Then migrating NPM to the new server at a later date? We have separate teams that monitors NPM and SAM and the team that monitors NPM doesnt want their servers touched. I would like to get everything installed correctly so I wont have to go through the pain of re-building the environment when they are ready for NPM to migrate to the new server.

aLTeReGo

Both SAM and WPM can be installed standalone/separate from NPM, though if you install them on a different server than your existing NPM instance you will need to use a different database. This will mean starting anew. Also, when it's time to migrate NPM over to this new SAM/WPM server, none of previous installs configuration or historical data can be migrated. In other words, you can't merge two separate databases together or have multiple Orion servers share the same database. (unless they're additional pollers, additional web servers, or Failover Engines)

Long story short. If you need to maintain your existing NPM's servers configuration and historical data while achieving that single server, single pane of glass view, then you'll have to either install NPM/WPM onto the existing NPM server, or migrate NPM onto the new server before installing SAM/WPM.