Importing Active Directory MPs Overrides, Monitors, and Rules from on one SCOM Management to Another Management

Anyone can help me with a step-by-step plan to import Active Directory Management Pack Overrides, Monitors, and Rules from one SCOM 2012 Management Group (Prod) to another SCOM 2012 Management Group (DEV),  and the other way around.
WooBadAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Well, first -- I'm assuming you've been creating your overrides/monitors/rules etc. in separate unsealed management packs, and you never - ever use the default management pack for anything.  (*echo*  Anything... ything...ing *echo*)

Second, I assume you'll have identical imported sealed management packs.  (Or at least you have the same base management packs that you are concerned about...  For example... you won't try to take your overrides for the Active Directory management pack, and load them onto an SCOM instance that doesn't have the Active Directory management packs loaded.)

In the SCOM console then, on the server from which you want to export your management pack... go to the Administration management pane -> Management Packs, find your management pack, right click and export.  That'll create an XML file.  If you're comfortable looking over XML, you can open it up in an editor and peruse it.  You can then take it over to the other system, and load that management pack XML file.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WooBadAuthor Commented:
OMG! First, thank you so much. I really wasn't expecting that someone would reply... and with such a good answer.
Reading your advice, it seems less complex than I thought.
The overrides/monitors/rules etc. were created in separate unsealed management packs.  I don't know for sure if the default management pack was  never - ever use for anything. However, I have reasons to believe they weren't. I can confirm.
0
WooBadAuthor Commented:
OMG! First, thank you so much Rich. I really wasn't expecting that someone would reply... and with such a good answer.
Reading your advice, it seems less complex than I thought.

The overrides/monitors/rules etc. were created in separate unsealed management packs.  I don't know for sure if the default management pack was  never - ever use for anything. However, I have reasons to believe they weren't. I can confirm.

Before reading your response, I was following the steps in this great article (see below) that I found on the net. It seems like that I don't to do all of that if the Default Management was never - ever used.

http://blogs.technet.com/b/pfelatam/archive/2012/03/27/opsmgr-saved-some-overrides-to-default-management-pack-didn-t-you-it-s-easy-to-move-them.aspx

I have attached the file that I exported from the old environment. Since our environment was upgraded to AD 2008 R2, would it be OK to remove all references pointing to AD 2003 as below:


-<Reference Alias="Windows4">

<ID>Microsoft.Windows.Server.AD.2003.Monitoring</ID>

<Version>6.0.8070.0</Version>

<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>

</Reference>

If I understand your advice, next I would Import the sealed AD 2008 Management Pack from Microsoft in the new environment. The import the Overrides from the old environment.

Is there anything else that I may need to do?

Thank you
0
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
I don't see the file attachment.  
And I'm a user of SCOM, not a Guru in it... so take this next bit with that in mind...

I'm assuming the XML you list is in one of your management packs that you have exported.  If that's the case, I'd feel pretty confident removing it, and importing the XML without it.  If it's part of the management packs you've received, I'd be much more careful.  I've run into cases where the packaged management packs rely on discovery and monitoring objects from previous versions that I wouldn't have expected.  (I'm not saying the AD Management pack does... I'm running the discovery components for 2000 to (2008 and above), and monitoring for (2008 and above).  Those components I imported from the sealed management packs though.
(Oh, and in case you haven't received this bit of advise yet... read each management pack guide for every sealed management pack you import BEFORE importing the management pack.)

I like that technet article though.  That's getting a bit more into editing the XML more than you'll (hopefully) need to do because you haven't used the Default Management Pack.  As I recall, it's sorting through the dependencies which get tricky.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IT Administration

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.