Migrating OpsMgr 2012 RTM to OpsMgr 2012 SP1

Written by Tao Yang

Over the Christmas / New Year break, I spent some time to upgrade the OpsMgr 2012 RTM environment in my test lab to SP1. Since System Center 2012 SP1 fully supports Windows Server 2012 and SQL 2012, I have decided not only to upgrade OpsMgr 2012 to SP1, but I’d also want all management servers, web server, database server to run on Windows Server 2012 and SQL server 2012.

My OpsMgr 2012 test environment consists 3 management servers, 1 database server (SQL 2008 R2, hosts both Operational and DW database, it is also the OpsMgr reporting server running SQL SSRS), and 1 web console server. All of these servers were running Windows Serer 2008 R2 SP1.

Below are the high level steps I have taken to upgrade this environment to OpsMgr 2012 SP1 and also migrate to Windows Server 2012 and SQL Server 2012 SP1:

  1. Update the existing OpsMgr 2012 RTM environment to SP1
  2. Build a new SQL 2012 SP1 database server running on Windows Server 2012 and Migrate both databases and reporting server role to this server.
  3. Move agents off each management server and rebuild them one by one running Windows Server 2012 and then install OpsMgr 2012 SP1 management server to join the existing management group.
  4. Rebuild Web console server to Windows Server 2012 and then install OpsMgr 2012 web console using OpsMgr 2012 SP1 install media.

Alone the process, I have documented some detailed steps and I want to share with the community as I assume I’m not the only one who also wants to upgrade the underlying OS for SCOM servers to Windows Server 2012. Here’s what I have documented:

Disclaimer: below are the step I’ve taken specific to my test environment. They are essentially combination of multiple guides from TechNet. Please only use it only as a reference, I hold no responsibilities for any damages it may occur to anyone else’s OpsMgr environment.

  1. Created Windows Server 2012 instance (named OpsMgrSQL01)
  2. Install SQL 2012 Enterprise With SP1 (Database Engine, Full-Text and Semantic Extractions for Search, SSRS, client tools etc)
  3. Upgrade existing OpsMgr 2012 RTM to SP1 (http://technet.microsoft.com/en-us/library/jj899854.aspx)
    1. Backup OperationsManager and OperationsManagerDW databases.
    2. run SP1 setup on all management servers
  4. Migrate SCOM Operational Database to new SQL 2012 server
    1. Poweroff all management servers
    2. Backup OperationsManager database on the original SQL 2008 R2 server
    3. Copy OperationsManager.bak to new SQL 2012 server
    4. Restore OperationsManager database from OperationsManager.bak on SQL 2012 server
    5. On the original SQL 2008 server, take OperationsManager database offline
    6. Startup all management servers
    7. Stop System Center Data Access Service, System Center Management service and System Center Management Configuration service on all management servers
    8. Follow instruction from http://technet.microsoft.com/en-us/library/hh278848.aspx to migrate the operational database
  5. make sure all management servers are functional
  6. Migrate SCOM Data Warehouse database and reporting server role to new SQL server
    1. Backup OperationsManagerDW database on the original SQL 2008 R2 server
    2. Copy OperationsManagerDW.bak to new SQL 2012 server
    3. Restore OperationsManagerDW database on the new SQL 2012 server
    4. Follow instruction to finish moving DW database: http://technet.microsoft.com/en-us/library/hh268492.aspx
    5. Configure SSRS on new SQL 2012 server
    6. Remove OpsMgr reporting server role from the old SQL 2008 server
    7. Install OpsMgr Reporting Server on new SQL 2012 server
    8. Follow instruction: http://technet.microsoft.com/en-us/library/hh457588.aspx to move the Reporting server
    9. On new SQL 2012 server, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting, change DWDBInstance to the new SQL 2012 server.
    10. On new SQL 2012 server, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\Reporting, change DWDBInstance to the new SQL 2012 server.
    11. On the new SQL 2012 server hosting the operational database, update the OperationsManager database table.
      1. Open SQL Server Management Studio.
      2. Expand Databases , OperationsManager , and Tables.
      3. Right-click dbo. MT_Microsoft$SystemCenter$DataWarehouse , and then click Edit Top 200 Rows .
      4. Change the value in the MainDatabaseServerName_2C77AA48_DB0A_5D69_F8FF_20E48F3AED0F column to reflect the name of the new SQL Server
      5. Close SQL Server Management Studio.
    12. In new SQL 2012 server, go to SSRS web page http://localhost/reports, edit “Data Warehouse Main” data source to point to the new SQL 2012 server.
  7. Turn off old SQL 2008 server
  8. Reboot new SQL 2012 server
  9. Reboot all management servers
  10. Move all agents from management server A to another management server
  11. If management server A is the RMS emulator, move the RMSE role to another management server by using Powershell Cmdlet: Get-SCOMManagementServer -Name “NewRMSE” | Set-SCOMRMSEmulator
  12. If the Reporting server is pointing to this management server, configure the reporting server to use another MS by editing the registry key on the reporting server
    1. Go to HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting, edit DefaultSDKServiceMachine to another management server.
    2. Go to HKLM\SOFTWARE\Microsoft\System Center Operations Manager\12\Reporting, edit DefaultSDKServiceMachine to another management server.
    3. Edit “<SQL Install Dir>\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config” file, locate 2 instances of <ServerName> tag and update the management server name
    4. Restart SSRS service on the new SQL 2012 server running SSRS
    5. Shut down management server A and make sure reporting still works
    6. Power up management server A
  13. Uninstall OpsMgr management server on management server A from control panel.
  14. Delete management server A from OpsMgr console (Administration–>Management Servers)
  15. Rebuild management server A with Windows Server 2012.
  16. Install Microsoft Report Viewer 2010
  17. Install OpsMgr 2012 Service Pack 1 on the newly built Windows Server 2012 and join it to the existing management group.
  18. Repeat step 10-17 for each management server that to be migrated to Windows Server 2012.
  19. Uninstall Web Console from Web Console server
  20. Rebuild Web Console server to Windows Server 2012
  21. Install Microsoft Report Viewer 2010 on the Web Console server
  22. Configure IIS and .NET prerequisites for OpsMgr 2012 web console
  23. Install OpsMgr 2012 Web Console on the newly built web console server
  24. Connect to the Web console server from a client computer and make sure the web console is functional.

Now, I have migrated everything but 1 management server to Windows Server 2012 and SQL server 2012. I have decided to keep one management server running Windows Server 2008 R2 just in case I need to test any different scenarios in the future.

I didn’t have chance to build a Gateway server in the RTM environment so I didn’t have a Gateway server to migrate.