none
SCOM 2012 - Disadvantage

    Pregunta

  • Hi Experts,

    Can any one list out the disadvantage of new release SCOM 2012.

    This will be helpful for us to plan for migration. Please help me.


    Regards, Pratap

    jueves, 21 de junio de 2012 5:00

Respuestas

  • Hi

    You mention "migrate" - a migration is different from an upgrade. Just to clarify if you are looking for an inplace upgrade or a migration from an existing SCOM 2007 R2 environment to a SCOM 2012 environment?

    Bob's list is very thorough but I would also suggest planning a test upgrade or migration. The following url shows how you can use a production setup to create an isolated test environment and then you can run the upgrade (or test a migration) against that to see what works \ breaks specifically in your environment:

    http://blogs.technet.com/b/servicemanager/archive/2011/11/08/setting-up-a-pre-production-test-environment.aspx

    The link is for SCSM but the process would be the same for SCOM.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    jueves, 21 de junio de 2012 6:42
  • - You'll have to rewrite\redevelop ALL your custom Network Device monitoring MPs. New Network Device model deprecate the old base Network Device so you'll not be able to use an old MPs with a newly discovered network devices.

    http://OpsMgr.ru/

    jueves, 21 de junio de 2012 7:20
  • Hi, thats a bit difficult.

    - Licensing model has changed. This is both advantage and disadvantage. Depending on how many products from system center you are using.

    - Management packs remain working, so no big problems there. Dashboarding is expanded, dont see issues there. network monitoring and cross plat improved.

    - Perhaps Avicode op top of 2007 was in some respects a bit better than APM in SCOM. But in other respects (ease of deployment and such) this has become better. If you didnt run avicode before it is no question and no disadvantage, but just an advantage.

    - Some scripts that have been created by yourself or others might not always run and need to be ported to 2012 formats. This just happens and i dont think its a big problem. Multiple posts on what to think of and how to get around (fix).

    - you might need to change your antivirus exclusions for scom if you already had fixed that for 2007 version. install path has changed. Is a few minutes work and only once.

    - There are less blog posts on 2012 than 2007 in the world... But 2012 is catching up as most community bloggers are coming across more and more 2012 and write about those. But there is a chance you might run into something that few others have come across and wrote about. Thats what I mean. I do not see this as a reason not to upgrade.

    - Windows 2000 is no longer supported for the agent. If you have a lot of those that is a consideration. However it is also that those should not be present anymore by now.

    Those are just some remarks, some are not disadvantages actually (sorry about that).


    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

    jueves, 21 de junio de 2012 6:24

Todas las respuestas

  • Hi, thats a bit difficult.

    - Licensing model has changed. This is both advantage and disadvantage. Depending on how many products from system center you are using.

    - Management packs remain working, so no big problems there. Dashboarding is expanded, dont see issues there. network monitoring and cross plat improved.

    - Perhaps Avicode op top of 2007 was in some respects a bit better than APM in SCOM. But in other respects (ease of deployment and such) this has become better. If you didnt run avicode before it is no question and no disadvantage, but just an advantage.

    - Some scripts that have been created by yourself or others might not always run and need to be ported to 2012 formats. This just happens and i dont think its a big problem. Multiple posts on what to think of and how to get around (fix).

    - you might need to change your antivirus exclusions for scom if you already had fixed that for 2007 version. install path has changed. Is a few minutes work and only once.

    - There are less blog posts on 2012 than 2007 in the world... But 2012 is catching up as most community bloggers are coming across more and more 2012 and write about those. But there is a chance you might run into something that few others have come across and wrote about. Thats what I mean. I do not see this as a reason not to upgrade.

    - Windows 2000 is no longer supported for the agent. If you have a lot of those that is a consideration. However it is also that those should not be present anymore by now.

    Those are just some remarks, some are not disadvantages actually (sorry about that).


    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

    jueves, 21 de junio de 2012 6:24
  • Hi

    You mention "migrate" - a migration is different from an upgrade. Just to clarify if you are looking for an inplace upgrade or a migration from an existing SCOM 2007 R2 environment to a SCOM 2012 environment?

    Bob's list is very thorough but I would also suggest planning a test upgrade or migration. The following url shows how you can use a production setup to create an isolated test environment and then you can run the upgrade (or test a migration) against that to see what works \ breaks specifically in your environment:

    http://blogs.technet.com/b/servicemanager/archive/2011/11/08/setting-up-a-pre-production-test-environment.aspx

    The link is for SCSM but the process would be the same for SCOM.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    jueves, 21 de junio de 2012 6:42
  • - You'll have to rewrite\redevelop ALL your custom Network Device monitoring MPs. New Network Device model deprecate the old base Network Device so you'll not be able to use an old MPs with a newly discovered network devices.

    http://OpsMgr.ru/

    jueves, 21 de junio de 2012 7:20
  • Good one Alexey. I forgot to mention that one :-) For some devices this is an advantage to start over... for some cases and real custom monitoring it is a bit of work to rewrite.

    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

    jueves, 21 de junio de 2012 7:26