How to remove OMS and Advisor management packs

<!--[if lt IE 9]>


Comments (10)
  1. gcodin says:

    Very good article Kevin, as always!

  2. vildauget says:

    Thank you, Kevin! This operation was painful – even with this guide to follow. Without, I wouldn’t be able to remove it. Overrides and references all over, and autodownloaders to add. I also needed to use the following guide as well to kill references that got stuck in the mess:

    Thanks again!

  3. Tina says:

    Please this is urgent. How do I remove multiple management packs from SCOM 2016.

  4. Tina says:

    Please this is urgent. How do I remove multiple management packs from SCOM 2016.

  5. Larry says:

    If we are NOT leveraging any OMS integrations with SCOM, can we simply not delete the following MP files from the Management Group?
    – Microsoft.SystemCenter.Advisor.Internal.mpb
    – Microsoft.SystemCenter.Advisor.mpb
    – Microsoft.SystemCenter.Advisor.Resources.ENU.mpb
    My concern with keeping them around is that new, undesirable, workflows might be included in a future version of these files, and I’ll have to revisit this issue once more, by creating new overrides. Also, if we change our minds in the future, the files are always available in the latest UR.

    1. Kevin Holman says:

      @larry –

      Yes – you can remove these MP’s, especially if a customer doesn’t want to connect SCOM to OMS. Even these MP’s are running workflows on ALL systems in the management group even if you DON’T use OMS, as evidenced by the errors seen on Windows Server 2003 machines.

      1. Dan Arstill says:

        What if I have SCOM and OMS connected and I need to decom or remove a server or bring a new server in, what is the process for that?

  6. Dan Arstill says:

    Do I just uninstall and then install the MP’s on the new server and then connect from the console?

  7. josh says:

    Hey Kevin,

    I ran into an issue where trying to remove the Microsoft System Center Advisor Management Pack. It showed that there was a dependency on the Management Pack Microsoft.SystemCenter.SecureReferenceOverride. Removing this Management Pack cleared out the profile settings for the Data Warehouse Account and the Data Warehouse Report Deployment Account.

    This happened in both my test and production SCOM environments – is this dependency common?

    1. Kevin Holman says:

      DO NOT delete Microsoft.SystemCenter.SecureReferenceOverride. EVER.

      This MP is built in and contains associations to all RunAs account profiles. You NEED it. 🙂 SCOM will break badly without it. In order to clean up your issue – the right way is to ensure there are no longer any Advisor RunAs profiles populated, then export the Microsoft.SystemCenter.SecureReferenceOverride mp, edit it, and remove the reference/dependency from the XML, and reimport. Same process as:

Comments are closed.

Skip to main content