How to Remove Management Pack Dependencies

When you create an override and don’t save it to a custom Management Pack it will by default save to the Microsoft.SystemCenter.OperationsManager.DefaultUser.xml management pack. This will later on bite you in the ass when you want to remove the effected management pack. To avoid this of coarse you should always save changes to a custom management pack…..

 

But if you did not like all the rest of have done at least once, then here is how you can remove the dependencies. But first please backup you management packs.

  1. Download and install Microsoft’s XML Notepad
  2. Export the Default management pack to any folder you like. This will export it into an XML file. Back this file up before making changes to it.
  3. Open the XML file in XML Notepad
  4. Expand the management pack in the left window to \\managmentPack\Manifest\References 

  1. Look in each sub-folder named Reference for the Management pack that you are trying to remove. Once you find it Delete the Reference folder.
  2. Import the Default XML file back into the console.
  3. Try to delete the management pack again.

August 14, 2008 | Filed Under OpsMgr, SCOM, System Center Operations Manager 

Comments

7 Responses to “How to Remove Management Pack Dependencies”

  1. Jason on November 13th, 2008 6:20 pm

    excellent tool. although my problem wasnt in the default, but another MP I created.

    thanks

  2. Mark on January 23rd, 2009 11:47 am

    Great stuff, I found I needed to delete a custom management pack to resolve the issue, then reconfigure everything again. I’ll be more careful next time!

  3. Brad Hearn on February 21st, 2009 4:52 am

    haha, I know what you mean. If I hadnt messed up in the first place myself I wouldnt have been able to post this.

  4. Sealy on February 24th, 2009 7:05 pm

    Excellent write up. I had a problem importing the pack. I went back and realized I had a bunch of Overrides. Under Monitoring all of my overrides were preventing the import from working. I had to delete all references to the management pack in all nodes and then it was finally successful. You saved me a complete reinstall.

  5. Chris on July 7th, 2009 6:43 pm

    Thanks. You have saved me a lot of time. I did try the overrides explorer first and removed all overlapping overrides, but still could not delete the management pack. Then exported the Default MP, removed the reference for the Citrix MP and boom – finally I was able to delete the Citrix MP and import the newer version (5.0.0.0). I knew that the things from the past would somehow come back and haunt me. ha ha

  6. Tom on September 21st, 2009 9:31 pm

    Great stuff, thanks.

    One question: By deleting the “Reference folder”, does that delete any overrides saved in the MP?

    Thanks,
    Tom

  7. Brad Hearn on September 24th, 2009 8:06 pm

    It will remove the override as well. So you will want to keep track of what you are removing. Generally we are following this process because we are removing the management pack but cannot due to these dependencies so it is not an issue. But if you are trying to clean your management packs you will want to take care. Start with an override report focused on the “Default Management Pack” This will help keep you focused.

Got something to say?

You must be logged in to post a comment.