I don't want to be angry right now, because I am aware that people can and do change their minds at the drop of a hat. But a part of me would really enjoy breaking something right now.
Anyways, after lengthy discussions with management, customers, and all of the in-between of setting a plan to build a new environment in a different domain and making sure that none of the old rubbish that we currently have has been long gone, it was decided that we would be better migrating the old environment on a new server. I have argued the complexities and difficulties that will occur, but obviously those that hold the purse strings are final.
So I have some questions about this and how to implement this. I say I have a few questions because we are also in the process of moving and will be moving within the next 7 ish weeks.
Anyways, do I do the following:
- Upgrade all of our old environment so it's on new applications.
- a number of changes so that all of our servers point to the next server first. (eg SNMP changes)
- Migrate all of our environment as required and advised by solarwinds (link I think can be found here - https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/Migrate_SolarWinds_products_to_a_new_server_with_a_new_IP_and_hostname)
- Then patch and spend time fixing the environment.
or
- Fix all of the environment up until the last minute,
- Do an change so SNMP and just get it done without consent of clients/customers. In theory it's a change that requires no downtime or reboot so this could be done as a large GPO change.
- Migrate everything across
- Upgrade all of our old environment so it's on new applications.
- Go back to fixing everything.
How would be the best way to approach this?