locked
Migration from SCOM 2007R2 to SCOM 2012R2 RRS feed

  • Question

  •    Hello to all. I have a SCOM 2007R2 environment with 3 servers:

       1- SRV #1 has RMS and WebConsole roles.

       2- SRV #2 has Gateway role.

       3- SRV #3 is Shared SQL Server with SCOM DB + Reporting roles.

       This deplyoment monitors ~600 and I´m planning to take it to SCOM 2012 R2.

       Question 1:

       I already read several articles but for me is not clear if I can just insert SCOM 2012 R2 Management Server and Gateway on a existing 2007R2 Management Group (of course that it already has a RMS), begin migrating agents to it and at the end  decomission SCOM 2007 R2 Servers. All articles that I read mention just two options: a) Side-by-Side migration (install SCOM 2012R2 on a NEW Management Group and begin agent migration to this NEW Management Group) and b) Upgrade (run in-place upgrade to SCOM 2012 R2 if current SCOM 2007R2 attend SCOM 2012 R2 requirements - if not, install new SCOM 2007R2 servers with supported requirements and run upgrade in-place). Considering this info., is it possible to run SCOM 2007 R2 --> 2012 R2 migration as I previously mentioned?

       Question 2:

       Does SCOM 2007R2 agent reports to SCOM 2012R2 Management Servers?

       Question 3:

       Is it possible to run direct migration (not pass through SCOM 2012 - withouy R2) using the path SCOM 2007 R2 --> SCOM 2012 R2 path?

       Regards, EEOC.

    Thursday, September 11, 2014 5:10 PM

Answers

  • Hi,

    From my point of view, as SCOM 2007 agents cannot communicate with SCOM 2012, so we cannot add SCOM 2012 server to SCOM 2007 management group.

    So I would like to suggest you follow those supported two ways to migrate to SCOM 2012.

    Regards,

    Yan Li


    Regards, Yan Li

    • Marked as answer by EEOC Tuesday, September 16, 2014 12:51 PM
    Monday, September 15, 2014 5:30 AM

All replies

  • Hi,

    Q1:

    It is suggested to do side by side migration, and for upgrading from System Center Operations Manager 2007 R2, please refer to the below link:

    http://technet.microsoft.com/en-us/library/hh476934.aspx

    Q2:

    You can multi-home the clients to both SCOM 2007R2 & 2012, but 2007 agent can’t communicate with a SCOM2012 MS.

    Q3:

    If we use side by side migration, then we don't need to pass through SCOM 2012, but if we use in-place-upgrade, then we must follow the below path:

    SCOM 2007R2 CU4+ > SCOM 2012 RTM > SCOM 2012 SP1 > SCOM 2012 R2

    More details:

    http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx

    Regards,

    Yan Li


    Regards, Yan Li

    Friday, September 12, 2014 5:48 AM
  •    Hello Yan, thanks for your reply.

       On Q1, I understand that MS recommends to do side-by-side as described on several articles. My question is if it's possible to "...just insert SCOM 2012 R2 Management Server and Gateway on a existing 2007R2 Management Group (of course that it already has a RMS), begin migrating agents to it and at the end  decomission SCOM 2007 R2 Servers" and avoid the several in-place upgrades mentioned on all MS articles (they don't mention that my suggestion can not be done). Do you know if is it possible or would generate problems?

       Here follows a Question #4:

       Why upgrade path states that manually installed agents should be upgraded before push-installed ones?

       A last question, #5:

       If SCOM 2007 agents can not communicate with SCOM 2012 Management Servers, why MS states that upgrade path for "Distributed Upgrade (Complex) Process Flow Diagram" begins with SCOM 2007 secondary Management Servers upgrade (agents' upgrade is done later on this process so this strategy should generate problems for several SCOM 2007 agents not communicating with already upgraded Management Servers to SCOM 2012)?

       Regards, EEOC.

    Friday, September 12, 2014 1:46 PM
  • Hi,

    From my point of view, as SCOM 2007 agents cannot communicate with SCOM 2012, so we cannot add SCOM 2012 server to SCOM 2007 management group.

    So I would like to suggest you follow those supported two ways to migrate to SCOM 2012.

    Regards,

    Yan Li


    Regards, Yan Li

    • Marked as answer by EEOC Tuesday, September 16, 2014 12:51 PM
    Monday, September 15, 2014 5:30 AM