Prepare your environment to Operations Manager 2012 – Part I Actions Plan
January 14, 2012 at 8:16 pm in Uncategorized by Christopher Keyaert
Hi all,
I will start this new series of posts about Operations Manager 2012 by explaining how to prepare your SCOM2007 environment to move to SCOM2012. The very first step to do before updating OM itself is to update the existing environment configuration, OS and DB, to be compliant with the OM2012 requirements.
Hopefully for us, you will see that there is several OS and DB configurations supported by bot Operations Manager releases, OM2007 and OM2012.
I invite you to take a look to the information available on Microsoft TechNet :
Operations Manager 2007 R2 Supported Configurations
http://technet.microsoft.com/en-us/library/bb309428.aspx
Operations Manager 2012 Supported Configurations
http://technet.microsoft.com/en-us/library/hh205990.aspx
I did a summary of he OS and DB configurations information in the tables below :
Supported Configuration for OM2007 and OM2012
Management Server supported configuration :
OS Configuration |
SCOM 2007 R2 |
SCOM 2012 |
Windows Server 2003 SP2 X86 |
Supported |
Not Supported |
Windows Server 2003 SP2 X64 |
Supported |
Not Supported |
Windows Server 2003 R2 SP2 X32 |
Supported |
Not Supported |
Windows Server 2003 R2 SP2 X64 |
Supported |
Not Supported |
Windows Server 2008 SP2 X86 |
Supported |
Not Supported |
Windows Server 2008 SP2 X64 |
Supported |
Not Supported |
Windows Server 2008 R2 SP1 |
Supported |
Supported |
DB Server supported configuration :
OS Configuration |
SCOM 2007 R2 |
SCOM 2012 |
Windows Server 2003 SP2 X86 |
Supported |
|
Windows Server 2003 SP2 X64 |
Supported |
Not Supported |
Windows Server 2003 R2 SP2 X32 |
Supported |
Not Supported |
Windows Server 2003 R2 SP2 X64 |
Supported |
Not Supported |
Windows Server 2008 SP2 X86 |
Supported |
Not Supported |
Windows Server 2008 SP2 X64 |
Supported |
Supported |
Windows Server 2008 R2 SP1 |
Supported |
Supported |
DB Configuration |
SCOM 2007 R2 |
SCOM 2012 |
SQL Server 2005 SP1/SP2/SP3/SP4 |
Supported |
Not Supported |
SQL Server 2008 SP1 |
Supported |
Supported |
SQL Server 2008 SP2 |
Supported |
Not Supported |
SQL Server 2008 R2 RTM/SP1 |
Supported |
Supported |
As you can see, several configurations are supported by OM2007 and OM2012.
The actions plan – Theory Part
In this posts series, we will work on a really small SCOM 2007 R2 infrastructure. We just have, one DB server and one Root Management Server. Concerning the configuration, both are running Windows Server 2003 R2 SP2 X64 and the Operations Manager DBs are hosted on SQL Server 2005 SP3.
As we could conclude from the tables above, our current Operations Manager 2007 infrastructure is not eligible for Operations Manager 2012. We have to update the Operating Systems on both servers and the SQL Server version must be also updated.
Updating the DB server
As we have to move from SQL Server 2005 to SQL Server 2008 R2 SP1, we will install a brand new server which will run Windows Server 2008 R2 SP1 and SQL Server 2008 R2 SP1.
We will move the Operations Manager 2007 DBs from the old SQL Server 2005 to the new SQL Server 2008 R2 SP1. Don’t worry too much about this part, the second post of this series will explain in detail how to move the Operations Manager DBs from SQL 2005 to SQL 2008.
Once done, we will remove the old SQL Server from our infrastruture.
Updating the RMS server
Now that our Operations Manager is running on the new SQL Server 2008, we will update the RMS. Our Root Management Server is currently running Windows Server 2003 R2 SP2 X64. To be compliant to SCOM2012, we will have to update it to Windows Server 2008 R2 SP1.
For doing this update, we will first install a brand new server running Windows Server 2008 R2 SP1 and install it as a new Management Server in our current SCOM 2007 R2 infrastructure.
Once done, we have to promote our brand new Management Server as Root Management Server of our OM infrastructure. The old RMS will be retrograded to a Management Server role.
and finally, we will remove the Management Server which is running Windows Server 2003 R2 SP2 X64.
We have now an environment eligible to Operations Manager 2012.
Conclusion
As we noticed, there is several step to accomplish. This first post was the actions plan, the theory, in my next posts, we will do it in practice.
Stay tune for the next post, in which I will explain in detail how to move the Operations Manager DBs from SQL Server 2005 to SQL Server 2008 R2 SP1.
Resources
Microsoft System Center Operations Manager 2007 R2 download
http://technet.microsoft.com/en-us/evalcenter/bb738014.aspx
Microsoft System Center Operations Manager 2012 RC download
http://www.microsoft.com/download/en/details.aspx?id=27974
Operations Manager TechNet Forums
http://social.technet.microsoft.com/Forums/en-US/category/systemcenteroperationsmanager
kikononto said on January 30, 2013
i feel blessed with your documentation.
thanks man.
David said on March 29, 2013
Hi Christopher,
Can you let me know how to move the SCOM 2007 r2 ACS collector server role from windows 2003 OS to windows 2008 as part of pre upgradation process
Manythanks
David