Answered by:
SCOM 2007 R2 migration 2012 R2 questions

Question
-
We have a SCOM 2007 R2 CU4 environment which consists of a single server running Windows 2008 Enterprise (non-R2) SP2 32 bit. The SCOM database runs locally on this server as well, which is SQL 2008 R2 standard.
I understand our environment is not a candidate for in-place upgrade which is fine, so I started researching the migration steps but am a bit confused since our existing server is 32 bit. I'd like to just spin up a new 2012 R2 server running SQL 2012 R2 to host the new SCOM 2012 R2 environment and just move everything over, but I'm not sure what the correct order of operations would be since our existing environment is 32 bit. Do I need to build up a new secondary server in our existing 2007 environment as well as a new SQL server and move clients/operational DB there before I can migrate to 2012 R2? Can I go straight from 2007 R2 CU4 to 2012 R2?
I'm also considering just starting over from scratch with a fresh 2012 R2 SCOM environment. Does anyone have a guide for this process or is it just literally rip/replace agents on the endpoints and uninstall 2007
Monday, January 5, 2015 7:29 PM
Answers
-
Deleted
- Proposed as answer by Xin GuoMicrosoft contingent staff Tuesday, January 6, 2015 5:37 AM
- Marked as answer by Xin GuoMicrosoft contingent staff Monday, January 12, 2015 6:20 AM
Tuesday, January 6, 2015 3:59 AM -
SCOM 2012 R2 supported configuration
1) Windows OS at least windows 2008 R2 SP1
2) SQL 2012 R2
Current Environment
1) Windows 2008 SP2 32-bit(not support on new SCOM environment)
2) SQL 2008 R2( at least SP1 is need)
My recommendations:
built-up a new SCOM environment and do side-by-side migrations
Advantage:
1) no need to upgrade SQL server and moving operations manager DB across different DB server
For detail on how to doing SCOM side -by-side migration, pls. refer tohttp://www.systemcentercentral.com/scom-2012-rc-side-by-side-migration-phase-1-preparations/
Roger
- Proposed as answer by Xin GuoMicrosoft contingent staff Tuesday, January 6, 2015 5:37 AM
- Marked as answer by Xin GuoMicrosoft contingent staff Monday, January 12, 2015 6:20 AM
Tuesday, January 6, 2015 4:11 AM
All replies
-
Deleted
- Proposed as answer by Xin GuoMicrosoft contingent staff Tuesday, January 6, 2015 5:37 AM
- Marked as answer by Xin GuoMicrosoft contingent staff Monday, January 12, 2015 6:20 AM
Tuesday, January 6, 2015 3:59 AM -
SCOM 2012 R2 supported configuration
1) Windows OS at least windows 2008 R2 SP1
2) SQL 2012 R2
Current Environment
1) Windows 2008 SP2 32-bit(not support on new SCOM environment)
2) SQL 2008 R2( at least SP1 is need)
My recommendations:
built-up a new SCOM environment and do side-by-side migrations
Advantage:
1) no need to upgrade SQL server and moving operations manager DB across different DB server
For detail on how to doing SCOM side -by-side migration, pls. refer tohttp://www.systemcentercentral.com/scom-2012-rc-side-by-side-migration-phase-1-preparations/
Roger
- Proposed as answer by Xin GuoMicrosoft contingent staff Tuesday, January 6, 2015 5:37 AM
- Marked as answer by Xin GuoMicrosoft contingent staff Monday, January 12, 2015 6:20 AM
Tuesday, January 6, 2015 4:11 AM -
Thanks, the multi homed approach is what I want. This link is very helpful. http://blogs.catapultsystems.com/cfuller/archive/2014/04/02/multihomed-migrations-in-operations-manager-lessons-from-the-field.aspx
Tuesday, January 6, 2015 4:39 PM