Making Changes to an Operations Manager Environment
Updated: May 13, 2016
Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager
After the initial deployment of System Center 2012 – Operations Manager, you might need to make changes or upgrades to the original deployment for reasons such as the following:
You need to replace hardware that is experiencing problems and that is no longer considered reliable.
You need to replace hardware as part of the upgrade process from System Center Operations Manager 2007 R2.
You need to add additional hardware to improve scalability and performance.
You need to move a database and log file to a different volume because of space or performance reasons.
You need to change hardware that is leased and is due to expire soon.
You need to change or upgrade hardware to comply with new hardware standards.
You initially installed multiple Operations Manager features on a single server and you need to distribute some components to other servers.
You need to restore functionality in a failure scenario.
Operations Manager supports changes to your Operations Manager infrastructure as listed below. Be cautious when performing these operations because they can result in data loss if not performed correctly.