locked
Overrides & Custom Monitor and Rules Migration RRS feed

  • Question

  • We have SCOM 2012 R2 UR 14 we wanted to migrate to SCOM 1801 and the biggest challenge is we have lots of overrides and custom rule and monitors created. Need suggestion how to handle this migration and replicating all the overrides and custom monitoring without export and import of these custom management packs. As the overrides are not well managed and one object has many overrides which might be super-seeding each other.

    Amanpreet Singh Bansal

    Wednesday, May 6, 2020 5:50 AM

Answers

  • Hi,

    If you are not willing to export/import the custom management packs, then you'll have to re-create all overrides, custom rules and custom monitors in your SCOM 1801 environment.

    Re-creating these would be the best option as if the overrides are indeed not well configured in the SCOM 2012 R2 environment, now you'll have the chance to create them correctly, and then also remember to document them down.

    Also note that SCOM 1801 & 1807 is no longer supported, I would strongly suggest you to migrate to either SCOM 2016 or SCOM 2019 instead, preferably the latest version, depending on what systems you're currently monitoring and what is supported by the newer versions of SCOM.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 6, 2020 7:29 AM

All replies

  • Hi,

    If you are not willing to export/import the custom management packs, then you'll have to re-create all overrides, custom rules and custom monitors in your SCOM 1801 environment.

    Re-creating these would be the best option as if the overrides are indeed not well configured in the SCOM 2012 R2 environment, now you'll have the chance to create them correctly, and then also remember to document them down.

    Also note that SCOM 1801 & 1807 is no longer supported, I would strongly suggest you to migrate to either SCOM 2016 or SCOM 2019 instead, preferably the latest version, depending on what systems you're currently monitoring and what is supported by the newer versions of SCOM.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 6, 2020 7:29 AM
  • Hello Aman, Custom rules & monitors are ofcourse a challenge while migration. Replicating the overrides would need the MP's to be exported n then imported. If the overrides are not well managed, you'd certainly need to identify them individually in the new SCOM environment. Also, as suggested by Leon, SCOM 2012 R2 should be upgraded to 2019 which is the latest environment. You can create a new SCOM 2019 environment & then migrate all those agents there. Migrating 2012R2 agents require 2016 agent first & then 2019. MS doesn't support direct upgrading 2012 agents to 2019. SCOM 2019 however do have a limitation of not supporting agents OS below 2012. Thanks, Amit
    Wednesday, May 6, 2020 12:14 PM
  • Agreed with the two replies above : migrating overrides is easy in itself (export/import), but if they are not currently managed properly, you should take the time to analyze them and recreate them properly in the new environment.

    It's going to be a tedious task, but hugely beneficial in the long run.

    • Edited by CyrAz Wednesday, May 6, 2020 12:24 PM
    Wednesday, May 6, 2020 12:21 PM
  • Thanks for the inputs, we are monitoring few Windows 2008 OS. It will check the supported agents OS before deciding which SCOM version to choose from.

    Do we have any tools to manage the overrides or custom monitors etc, does importing the CSV to Splunk or any other tools will help ? 


    Amanpreet Singh Bansal

    Tuesday, May 12, 2020 7:36 PM
  • Do we have any tools to manage the overrides or custom monitors etc, does importing the CSV to Splunk or any other tools will help ? 

    Amanpreet Singh Bansal

    Tuesday, May 12, 2020 7:36 PM
  • Tuesday, May 12, 2020 8:22 PM