none
SCOM 2012 Deployment - simple design

    Question

  • I'm fairly new to SCOM so just started researching upgrading our environment from 2007 R2 to 2012.

    We have a single server running SCOM 2007 R2 and its DB and reporting DB are installed on a remote SQL server.

    I have been informed to find a way to upgrade without downtime if possible.

    1)  Can I install SCOM 2012 on a seperate server with a new seperate DB/Reporting instance and then migrate agents to the new SCOM 2012 thus allowing them to continue communicating to 2007 until upgrade of the agent?

    2)  Any good references for my type of environment on step-by-step upgrade procedures?

    I have also taken over a SCCM installation which is located on its own server.  Any thoughts on combining SCOM and SCCM on a single server naturally with remote DB instances.

    Monday, April 09, 2012 9:07 PM

Answers

  • Hi,

    You can introduce new management server if your existing server does not meet the minimum requirement stated in the Upgrade Process

    "When your single-server management group does not yet meet the minimum supported configuration requirements for System Center 2012 – Operations Manager, and requires new hardware."

    Single-Server Upgrade (Complex) Process Flow Diagram

    It is worth going through the upgrade process guide...

    -Regarding combining SCOM SCCM generally not recommended (due to perofrmance issue) but can be installed. So it really depends on your infrasturcture what all features are you going to use in these products...

    There are too many considerations from SCCM, SCOM on same server- disk configuration, the number of clients, the schedules for inventory, app  deployments, use of OSD, etc. etc... from SCOM perspective ... MP's, number of agents, web url monitoring, etc..

    So again I would  say both applications can be resource intensive at times, especially to SQL Server so performance would be the issue.. and also single point of failure design

    Depending on your infrastructure you can use capacity planner for both SCCM & SCOM

    SCCM capacity planner

    http://myitforum.com/cs2/files/folders/utilities/entry112970.aspx

    SCOM Design guide
    http://technet.microsoft.com/en-us/library/dd789005.aspx

    Hope that helps....

    Varun

    • Marked as answer by SunkistDavid Tuesday, April 10, 2012 5:17 PM
    Tuesday, April 10, 2012 6:53 AM
  • Dear,

    1-As per technet you can only make Inplace upgrade 

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

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

    I do not recommend at all to combine SCOM and SCCM on the same server

    Thanks

    • Marked as answer by SunkistDavid Tuesday, April 10, 2012 5:17 PM
    Tuesday, April 10, 2012 4:34 AM

All replies

  • Dear,

    1-As per technet you can only make Inplace upgrade 

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

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

    I do not recommend at all to combine SCOM and SCCM on the same server

    Thanks

    • Marked as answer by SunkistDavid Tuesday, April 10, 2012 5:17 PM
    Tuesday, April 10, 2012 4:34 AM
  • Hi,

    You can introduce new management server if your existing server does not meet the minimum requirement stated in the Upgrade Process

    "When your single-server management group does not yet meet the minimum supported configuration requirements for System Center 2012 – Operations Manager, and requires new hardware."

    Single-Server Upgrade (Complex) Process Flow Diagram

    It is worth going through the upgrade process guide...

    -Regarding combining SCOM SCCM generally not recommended (due to perofrmance issue) but can be installed. So it really depends on your infrasturcture what all features are you going to use in these products...

    There are too many considerations from SCCM, SCOM on same server- disk configuration, the number of clients, the schedules for inventory, app  deployments, use of OSD, etc. etc... from SCOM perspective ... MP's, number of agents, web url monitoring, etc..

    So again I would  say both applications can be resource intensive at times, especially to SQL Server so performance would be the issue.. and also single point of failure design

    Depending on your infrastructure you can use capacity planner for both SCCM & SCOM

    SCCM capacity planner

    http://myitforum.com/cs2/files/folders/utilities/entry112970.aspx

    SCOM Design guide
    http://technet.microsoft.com/en-us/library/dd789005.aspx

    Hope that helps....

    Varun

    • Marked as answer by SunkistDavid Tuesday, April 10, 2012 5:17 PM
    Tuesday, April 10, 2012 6:53 AM
  • Thanks for great responses

    Looks like I will have to perform a complex deployment because my SCOM 2007 R2 DB is on SQL 2005.  Will need to move it our SQL 2008 deployment.  Otherwise all looks good.

    Tuesday, April 10, 2012 5:17 PM
  • Another question:  I am running SCOM version 6.1.7221.0 which if I'm reading correctly is the base version.  If I'm moving the SCOM DB's from their 2005 instance to SQL 2008 in advance of the upgrade do I need to upgrade SCOM to CU5?  As a note my SCOM server is installed on Server 2008 Enterprise with SP1 on it.  I understand my server needs to be on R2 SP1 so will need to add another SCOM 2007 install to support the upgrade.
    Tuesday, April 10, 2012 8:52 PM
  • Yes, 6.1.7221.0 is the base version for SCOM 2007 R2 and before upgrading to SCOM 2012 latest CU is must and CU5 is the latest one. You can refer to below link for CU5 installation.. with step by step procedure

    http://blogs.technet.com/b/kevinholman/archive/2011/08/03/opsmgr-2007-r2-cu5-rollup-hotfix-ships-and-my-experience-installing-it.aspx

    For SCOM 2012 minimum OS requirement is Windows 2008 R2 SP1

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

    Thanks,

    Varun

    Wednesday, April 11, 2012 6:20 AM
  • Great replies thank you.

    Another one - in looking at the Database components of this installation I'm only seeing a database called OperationsManager I don't see any DB called OperationsManagerDW.  Could 2007 have been installed without a DW database?  Where in OpsManager can a see what DB's its using?

    Thanks

    Wednesday, April 11, 2012 4:48 PM
  • Because probably you have not installed OperationsManagerDW... In SCOM 2007 R2 DW & Reporting DB component is optional. If you want to install it just run scom setup select Operations Manager 2007 R2 Reporting .. this would install DW & Reporting.

    In SCOM 2012 it is very much part of the installation.

    Thanks,

    Varun

    Thursday, April 12, 2012 6:03 AM