Management Pack reference/dependency cleanup tool

Has anyone else seen a tool that locates old/stale MP references and removes them? I swore I ran across a tool the other day that did this, however I can't find it now that I actually need it.

Hi,
you could be referring to this
http://blogs.catapultsystems.com/mdowst/archive/2014/05/15/scom-amp-scsm-management-pack-cleanup.aspx
Blog: http://theinfraguys.com
Follow me at Facebook
The Infra Guys Facebook Page
Please remember to click Mark as Answer on the answer if it helps you in anyway
That's the one, thanks!

Similar Messages

A question regarding Management pack dependency.

Hi All,
I am new to SCOM, I have a question regarding management pack dependency.
My question is, Is Dependency is required when New alerts are created in a unsealed MP and the object class selected during alert creation is (i.e Windows server 2012 full operating system) and it is on a Sealed management pack ?
For example i have a Sealed Windows server 2012 monitoring management pack.
I have made a custom one, for windows server 2012, So if it the custom is not dependent on the sealed Windows server 2012 monitoring management pack, Then cant i create any alerts in the custom management pack targeting the class Windows server
2012 full operating system ?

Hi CyrAz,
Thank you for the reply. Now if your's and my understanding is the same, Then look at the below what happened.
I created a Alert monitor targeting a Windows Server 2012 class in my custom management pack which
is not dependent on the Windows server 2012 management pack, But how was i successfully able to create them when the dependency is not there at all, If our understanding is same, then there must be an Error thrown while creating the monitor its self right
? But how was SCOM able to create that ?
Look at the below screenshot.
I was able to create a monitor targeting Windows server 2012 Full operating system and create a alert on the custom management pack which is not at all dependent
on the Windows server 2012 Sealed MP.
Look at the dependency of the management pack where i do not have the Windows server 2012 management as my custom management is not dependent on that.
Then how come this is possible ?

How I know which manageability tools(Oracle Change Management Pack,Oracle C

Dear all,
How I know which manageability tools(Oracle Change Management Pack,Oracle Configuration Management Pack,Oracle Diagnostic Pack,Oracle Tuning Pack, etc.) are installed on my oracle databases? Is there v$view to look at? Thank you in advance for your help.

The usual method is described in http://download.oracle.com/docs/cd/B19306_01/license.102/b14199/options.htm#CIHGFIAF

FIM Rerporting management pack multivalue references

Hi everybody!
We have set up a FIM reporting extension on existing FIM and SCSM solution for our client with some of the custom management packs containing multivalue references (saved as a reference type). Some (but not all) object in FIM were many months old and requests
that set the multivalue attributes were long gone.
The problem we seem to be facing now is that although the new data is visible in reports, the old multivalue attribute data is not transferred to SCSM database neither to any of the data warehouse databases. I am pretty sure we got the bindings and schema
correct (as I said, new data is transferred without any problems), but the old data is just not there.
Best Regards,
Andraž Žagar

Remove SCSM Management Pack with dependencies

I's trying to delete a couple of MP's from Service Manager 2012 R2 that I no longer need. They all show that the MP "Service Manager Configuration Management Configuration Library" is dependent on them.
The MP is unsealed but is an MPB. How do I remove the dependency from an MPB?
Thanks,
Allen

You've stumbled into a tricky situation. (Sorry, Thomas, I'm stepping on your toes yet again! ;) )
MPBs are basically "zip files" that contain an XML management pack and any resources (dlls, images, etc) that are needed for that management pack.
You can export the XML MP, but you don't get the resources. You can export the MPB, but it's not easy to extract the resources and XML.
But it can be done (I had to do it last week and it was annoying..if there's a better way to do it, I sure would love to know what it is.)
There's a second option that I'll describe in a bit, but it's still pretty annoying. There's also a third option that, if you need resources (images) from an SCSM MP, is even easier.
Edit: Go with option 3 if you're modifying an out-of-the-box MP and you have the authoring tool installed. I had to do option 1 for another MP and didn't have its resources anywhere else. Since you're modifying an SCSM MP, I don't think you'll
have to worry about all the option 1 stuff at all..but I'm leaving it here in case anyone's interested.
Option 1) Extract the MP and resources from the MPB. Modify the MP. Re-bundled the MP with its resources. Import that new MPB.
http://technet.microsoft.com/en-us/library/hh519649.aspx
That's only half the story, though. The last sentence of that article describes using the GetStreams() method of the ManagementPacks property. Once you use that, all you have is a big list of Streams. You need to write some powershell to actually convert
those streams into files. I don't even want to show you the powershell I used because it only worked for a very specific set of resources that I knew existed in the management pack I was trying to modify. It would not work for any other management pack
or any other resource. But, Google can show you plenty of examples on how to convert a stream to a file using powershell (I found an example on StackOverflow that I adapted
http://stackoverflow.com/questions/15299544/how-can-i-write-a-binary-stream-object-to-a-file-in-powershell I don't know if there's a better or more elegant way of doing it, I just know I was able to adapt it to work for me)
After all that, you'll have your resources. Now you can export the MP from Service Manager as just an XML file. Make your changes to it. Use New-MPBBundle.ps1
http://blogs.technet.com/b/servicemanager/archive/2009/09/04/introducing-management-pack-bundles.aspx to bundle your xml file with the resources you just extracted. Import your new MPB.
Option 2) Remove unnecessary references using C# (Maybe powershell?)
Using the SDK, retrieve your MP. Remove the reference. "AcceptChanges()". Done.
ManagementPack mp = emg.ManagementPacks.GetManagementPack(new Guid("<My Management Pack Guid>"));
mp.References.Remove("<The alias for the reference I want to remove>");
mp.AcceptChanges();
Option 3) If the MP you want to modify is an out-of-the-box SCSM MP bundle, get the resources from your authoring tool installation..they're all in there. (the png images, not the DLLs)
Then you can just export the MP XML, modify it, then re-bundle it with new-mpbfile.ps1 and re-import it into service manager.
All of these options of course require that _nothing_ in the management pack actually uses that alias/reference you want to remove. So if you still have a view that references that MP, you won't be able to remove the reference. Option 2 would be more
annoying if the reference you want to remove is still being used..you'd have to use the console to remove the views, or templates, or whatever else might be referencing it.
Option 2 gives me an idea for a quick little utility I could write.. "remove unused references from all unsealed MPs"..maybe I'll do that this weekend :)

Changing the Management Pack extensions or items are stored in

I think I know the answer to this but I will ask it anyway. Is it possible to change the Management Pack an extension or an object such as a Queue or Subscription is stored in?
Reason I ask is the person that was maintaining SM before me stored every single form extension, subscription, queue and view etc...in the same Management Pack. I really don't like this particular setup and I am sure its not best practice. I plan to break
out all the above and possibly more into separate newly created Management Packs, like a separate one for Views, a separate one for Subscriptions etc.... Is the only solution to delete the existing item and create a new one with the same details including
the display name?

You can, but not as easily as you would like.
Essentially, what you would need to do is split up the the XML by hand, making sure to sort out the DisplayStrings sections to the correct components. Export out the "main" MP, cut out a section of XML that represents the form extension, paste
it into a new file with a new name, add a reference to the new MP to the main MP, and replace all references to that object with MP Aliases to that object's new home. Import both the new MP and the reduced "main" MP back into the database.
there are two problems thou:
Some objects, like projections (used in form extensions created by the authoring too) and class extensions should only ever be stored in sealed MPs, because removing them causes data that reference them to be invalid, i.e. properties defined in class extensions
are lost if that class extension is removed and re-added, and templates that depend on projections are inaccessable if the projection they are based on is lost.
some atomic SDK objects, like workflows, consist of several non-consecutive XML sections, meaning you would need to trace the references and identify which of many <Rule> and <Action> sections belonged with which workflows, and make sure they
would all end up in the same MP.
now you could do this slowly, pulling sections out of the "main" MP and replacing them with references over various nightly downtimes, exporting the "main" MP and carving out a few objects, then importing the trimmed down "main"
MP and the new single use MP until you had something resembling best practice functional isolation (all Change request notification over here, all service request workflows over there, etc), and the hollowed out husk of your "main" MP as a miscellaneous
container, but i think you'll find that you still have to face and deal with data loss and breakage, potentially a lot more trouble then it's worth.
Given that, i would instead propose that you give up on correcting sins of the past, and start doing it right now. start setting up your new MPs and put new thingss into them, and while you're working, anything that you can easily rebuild. Make a plan to
rebuild your templates and form customization. start identifying class extensions you'll have to rebuild, and work up a plan to export data defined by them somewhere (probably powershell and CSV) so you can restore it when the classes are restored.
Like most data hygine problems, there isn't an easy bulk application answer. you just have to look at everything and clean it up as you go. you can mix salt and sugar quite easily. UNmixing them is a lot more work.

Where do the Management Pack Files go once you import them

Hello
Hopefully this is a simple question, I may just be missing some thing obvious
I have SCOM 2007 R2
When I download and run the MSI to unpack he MP, I understand where it extract the files. I then go to SCOM Console and Import the MP, not problems so far.
However I would expect the MP import process to also place a copy of the MP in the "C:\Program Files\System Center Operations Manager 2007" folder. However on several occasion when I have needed to point/find a Management Pack for various reasons, the
MP or MPs do not appear to be in this folder. I guess I could always go back to the location where the MP is extracted from the MSI and reference them there. However I thought they should all reside in the "C:\Program Files\System
Center Operations Manager 2007" folder as a matter of course.
Any advice, most welcome please
Thanks
AanotherUser

Hi AanotherUser,
It depends on a management pack, some of them place a copy of .mp files to C: drive, some don't.
Useful link:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/7d856549-0be8-4781-9e2b-3fea82c2e377/default-install-location-for-opsmgr-2012-sp1-management-packs?forum=operationsmanagergeneral
Natalya

Unsealed Management Pack

Hello,
We have created a custom config item class and imported the management pack unsealed into our environment. We have had the MP this way for over a month and some of our SR's have the custom config item as an affected Config item. This was one of our first
custom classes and I didn't realize it would be best practice to always import these types of MP's as sealed Management packs. I can not see the class from the DW. My question is, can I just import a sealed version of this MP or do I have to remove the unsealed
MP. Will removing the unsealed MP cause me to lose all data related to it?

ya, Rob has it right, but just to clarify a bit:
you can't upgrade a unsealed MP to a sealed MP. you'll get an error about duplicates
you can't create a MP reference an unsealed mp. unsealed MPs can change in ways that aren't upgrade compatible, so nothing else can depend upon them.
any class you create in an unsealed MP will never get moved to the DW, because the DW MPSync Job only copies sealed MPs, due to versioning considerations.
if you delete the class prototype, all object of that class will be removed from the active service Manager database.
Classes (specifically sealed classes that can be referenced) have certain constraints on what counts as compatible for upgrade, i.e. all properties defined for those classes must stay the same in all future versions.
relationships to objects that are removed (for instance, because their class is removed) will be removed as well.
New objects will get new internal IDs, and not "recover" any information from the old objects. same with classes in different MPs, even if their internal names are the same.
Back to the point at hand, your best way out is exactly what Rob mentioned: Export the data to some other location, like CSV, remove your unsealed class, wait for the active database to clean up, import a sealed version, and reimport the data. be sure to
export any relationships, such as owner, created by, relates to work item, etc.

Exchange 2010 Management Pack Data Warehouse Synchronization Fails

Hi Everyone!
Has anyone had success with importing the Exchange 2010 management pack into Service Manager 2012?
When we try to import it, it fails.
Upon further investigation, the 'System Center Core Monitoring' management pack (which is not included with Service Manager 2012) is a dependency of the Exchange 2010 management pack but
after we import it from the OpsMgr 2012 media, we still get the following warning when we import the Exchange 2010 management into Service Manager 2012...
"The management pack was imported successfully.
Warnings (1):
Override verification failed, cannot find Management Pack Element : : Cannot find ManagementPackElement [Type=ManagementPackRule, ID=Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold] in management pack ManagementPack:[Name=Microsoft.SystemCenter.2007,
KeyToken=31bf3856ad364e35, Version=6.0.6246.0]."
...and, the Exchange 2010 management pack status in the Service Manager 2012 Data Warehouse 'Management Pack' view indicates 'failed' after the MPSyncJob completes.
We have a few 'Business Services' which depend on the Exchange 2010 management pack that we are trying to synchronize from OpsMgr 2012 and we are stuck until we can get the Exchange 2010 management
successfully imported into Service Manager 2012 and have it show a status of 'Completed' the Service Manager 2012 Data Warehouse 'Management Pack' view.
Nothing useful in the
Service Manager 2012 Data Warehouse and Management servers events logs that we could see.
Any help or guidance would be GREATLY appreciated!
Regards,
JJ

Update: I Just tested with CU2 installed for SrvMgr 2012 and OpsMgr 2012 and version 14.3.38.2 of the Exchange 2010 management, but the management pack still fails to deploy to the SrvMgr 2012 data warehouse (the management pack status shows
up as 'failed' and the MPSyncJob shows the management pack as 'pending association'). The only clue I have for this problem is the folllowing warning which occurs when I import the management pack into SrvMgr 2012...
I also get the following 33519 Event ID warning in the Operations Manager event log on the data warehouse server...
~~~~~
Management pack association ignored. This does not require any action. If you continue to frequently see this warning, contact your administrator. This process will continue to retry.
Management pack ID: e2296ed5-ddbc-ebc7-3881-c5288adaa7cf
Management pack name: Microsoft.Exchange.2010
Management pack version: 14.3.38.2
Data source name: SRV
Message: Either the MP has failed deployment Or any of its references has failed deployment
~~~~~
Has anyone had success with getting the Exchange 2010 management pack imported and successfully deployed to the SrvMgr 2012 data warehouse?
The good news is that even though the Exchange 2010 management pack has a status of failed, the distributed applications in OpsMgr 2012 that depend on the Exchange management pack now show up under Configuration Items/Business Services including
all related service component objects which was what I was trying to accomplish in the first place, so for now I'll just leave the Exchange 2010 management pack in the data warehouse with a failed status.
Regards,
JJ

Form customizations and management packs

Is there any way to determine if an out of the box form such as Incident has been modified in any way using the authoring tool and if so, can you determine which management pack the changes were saved in?
I would like to modify a form but I don't know if the person that was maintaining SM before me did anything with it and if so, where the changes are stored.

Just thought I would provide an update since there was so much time put into this thread. I exported the management pack I have been trying to open with the Authoring Tool and using Notepad, found and removed the following:
      <Reference Alias="CustomMicrosoft_SystemCenter_ServiceManager_ChangeRequestActionLog">
        <ID>Microsoft.SystemCenter.ServiceManager.ChangeRequestActionLog</ID>
        <Version>7.5.2017.6</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
Imported the MP back into SM and then exported again and was able to successfully open the MP with the Authoring Tool. Doing this in test of course and have no idea what else references the above or why it's there. It's unfortunate the MP is not available
so you can just point the Authoring Tool at it but it also proves this was the last major road block.
I suppose it could be possible to make your form update and before importing, manually put the above back in the MP before importing but that would be a pain and prone to error at some point.
After making my change to the form and saving the changes, I imported the MP back in and received 54 of the following warnings:
Unsealed management packs should not contain type definitions. The element WorkItemGroup.3bb30997a36a4bd0889515981829573a of type ManagementPackClass found in an unsealed management pack.
I don't think this has anything to do with the change I made. I believe these issues existed before I removed the reference to the MP but you just could not see them because you could never open the MP with the Authoring Tool.

Applications Change Management Pack 3.0 now available

E-Business Suite Applications Technology Group recently released a new product, the Application Change Management Pack (ACMP), and a new version of their Application Management Pack (AMP).
The Application Change Management Pack is noteworthy because it provides three new tools for automating updates to multiple E-Business Suite instances:
Customization Manager automates the packaging of your customizations into AD-compliant packages that can be deployed across multiple E-Business Suite instances. Before packaging, the Customization Manager validates your customizations against Oracle's software coding best practices.
Patch Manager integrates with Oracle Metalink and automatically downloads and deploys different types of patches across multiple (single or multi-node) E-Business Suite instances.
Setup Manager helps manage functional setups that need to be duplicated across multiple E-Business Suite instances.
Licencing
Application Management Pack for Oracle E-Business Suite and Application Change Management Pack for Oracle E-Business Suite are separately licensed products. Application Management Pack for Oracle E-Business Suite Version 3.0 is a mandatory prerequisite for Application Change Management Pack for Oracle E-Business Suite Version 3.0 and should be licenced separately.
Downloads
The Application Management Pack and Application Change Management Pack are available as a single install using Oracle Universal Installer. They can be downloaded via:
[Application Management Pack and Application Change Management Pack for Oracle E-Business Suite Version 3.0 (Patch 8333939)|http://updates.oracle.com/ARULink/PatchSearch/process_form?bug=8333939#uage=0&process=Submit]
References
[Getting Started with Oracle Application Management Pack and Application Change Management Pack for Oracle E-Business Suite Version 3.0 (Metalink Note 812315.1)|https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=812315.1]
[Oracle Enterprise Manager Application Change Management Pack for Oracle E-Business Suite (PDF, 260K)|http://www.oracle.com/technology/products/oem/pdf/ds_appl_chg_mgmt.pdf]
[Application Management Pack for Oracle E-Business Suite Data Sheet (PDF, 80K)|http://blogs.oracle.com/stevenChan/2009/06/www.oracle.com/technology/products/oem/pdf/apps_mgmt_ebiz.pdf]
Related Articles
[Comparing OEM Data Masking and AMP Data Scrambling Features|http://blogs.oracle.com/stevenChan/2008/04/comparing_oem_data_masking_and.html]
[Certified Oracle RAC Scenarios for Oracle E-Business Suite Cloning|http://blogs.oracle.com/stevenChan/2009/03/certified_rac_scenarios_for_ebs_cloning.html]

There are many enhancements in Setup Manager compared to iSetup. To list a few:
1) ability to create a project which groups extracts, loads and reports and orchestrate these tasks as per your requirements.
2) Ability to migrate data between point releases of EBS. Example, you can move data from 12.0.4 to 12.0.6 or 12.1.1.
3) Ability to share the projects with other users.
4) You can do extraction and loading to multiple instances in a single execution.

Error showing while adding a management pack to 2007R2 authoring console

Hi Every one,
While trying to add an unsealed management pack to 2007 authoring console we are getting error
XSD Verification failed for management pack[line: 1, "color:#222222;font-family:arial,sans-serif;font-size:13px;line-height:normal;">
system.xml.schema.xmlschemavalidationException:The schemaversion atribute is not declared
any help will be thank full
Regards,
Nikhil

The Authoring Console has not been updated and does not understand the OpsMgr 2007R2 MP Schema version. It can still be used to produce MP that will work on OpsMgr 2007 R2, but you need to reference the old versions of the libraries.
You can check this link , it will help you in your issue
http://blogs.inframon.com/post/2012/06/12/Choosing-the-correct-Management-Pack-Solution-with-Visual-Studio-Authoring-Extensions.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

Management pack version difference in System Center - Operations Manager 2012 R2 - Help us.

Hi,
I have SC Operation manager 2012 r2 in my environment. It has managed with multiple management servers.
I have import some unsealed MPs through Ops SDK code and by manually using Operation manager console.
Here with i tried to install higher version of MPs and upgrade its version from 1.1.0.0 to 6.0.0.0.
case 1:
After successful installation of some MPs and check Operation manager console, it showing newly upgraded version(6.0.0.0).
Then i have import that MP and checked its version inside it showing 1.1.0.0(older version).
Here the imported MP has 1.1.0.0 version and console showing its version as 6.0.0.0.
Why it showing different versions in imported MP(inside xml) and Operations manager console view?
case 2:
After that i tried to import other MPs using console. But it showing below error;
Verification failed with 1 errors:
Error 1:
Found error in 2|Monitoring.ActiveDirectory_server|6.0.0.0|Monitoring.ActiveDirectory_server|| with message:
Could not load management pack [ID=Monitoring.Base, KeyToken=9e875220a3987e0b, Version=6.0.0.0]. The management pack was not found in the store.
: Version mismatch. The management pack ([Monitoring.Base, 9e875220a3987e0b, 1.1.0.0]) requested from the database was version 6.0.0.0 but the actual version available is 1.1.0.0.
Its happened in multiple management servers scenario. So Is any possibility to happen because of multiple management servers scenario?. There is no issues in this same MPs while i tried in single management server. These same MPs are imported and working
fine in single management server scenario.
Help me to solve these 2 issues!!
Thanks,
satheesh

1) At first, you should make sure that the imported MP has correct version. I will open the XML of the imported MP and check its current version e.g.
When you open the xml file of imported MP, the version number is shown as
<Manifest>
    <Identity>
        <ID>Microsoft.SystemCenter.Visualization.Component.Library.Resources</ID>
        <Version>1.0.0.2</Version>
    <Identity>
    <Name>Resources library</Name>
    <References>
        <Reference Alias="System">
        <ID>System.Library</ID>
        <Version>1.0.0.1</Version>
From the above sample, the imported MP version number is 1.0.0.2.
2) I am using operation console to import the management pack and check the version number in operations console whether it is updated to new version 1.0.0.2
3) Using operations console to export the MP which has imported in step 1) and open it to check what is the version number of MP. Make sure that the version is 1.0.0.2
4) If the above procedure provide a prefer match of version number, re-import all problematic MP.
5) At last, you may use the following SQL to check whether the correct version number of MP is stored in DB successful
select version, friendlyname from managementpackview where friendlyname like 'Microsoft.SystemCenter.Visualizatio%'
Roger

Distributed Application group relationships not displaying in health view (VSAE created management pack)

Hi there,
I am working through my first complex Distributed Application which I have been creating using VSAE. I have followed Brian Wren's training, but the result does not match what I am expecting.
I have created a single DA (based on the System.Service class) with four groups (base on System.Group) which will be populated with the core components of the application. Each of the groups (and the DA) is configured as a Public, Non-Abstract, Non-Hosted
Singleton, as per the MPAuthor.Stores example. Each of the four groups is linked via an Internal, Non-Abstract System.Containment relationship to the DA.
When I open the DA diagram view, I only get the DA class visible. Each of the four groups shows in the Groups node in the Operations Console. Based on the experience with importing the MPAuthor.Stores MP, I was not expecting to see the groups in the Groups
node, but linked in the DA diagram node.
I have configured dependency monitors for each of the groups, and these display in the Health Explorer but there is no health rolls up.
The only difference between the MPAuthor.Stores module and mine (that I am aware of) is MPAuthors.Stores is a 2007 R2 MP, and I have created a 2012 MP as I will be deploying to 2012 SP1 and there is no need for backwards compatibility.

Hi Vladimir,
Thanks again for your response. I'm not quite sure what you mean with your last post. My current DA model is:
| Dist App |
| System.Service |
|
| | | |
| Group 1 | | Group 2 | | Group 3 | | Group 4 |
| System.Group | | System.Group | | System.Group | | System.Group |
Where all the groups have discoveries for membership. Are you saying that I need another level of groups below these to house the objects?
I thought that the point of System.Group as a base class was that it did not appear in the console, but gave an automatic health rollup (as per TechNet). Interestingly I am not getting
the automated health rollup for the Groups for their members and it is displaying in the Groups list in the console.
I have also tried creating a new DA with a single group in an 07 MP, and have the same issue. The sample MPAuthor.Stores management pack works as expected.

Script to get all the alerts from SCCM Management Pack

Hi Team,
I need a script/tool to generate all the default alerts from a Management Pack.
Thanks and Regards, Mohd Zaid www.techforcast.com

You may use the following SQL statement
select displayname as MPname, b.monitorname, b.alert from(
select displayname as monitorname, alert, a.managementpackid from (select monitorid, displayname as alert,
monitor.managementpackid from monitor inner join displaystringview on monitor.alertmessage=ltstringid
where languageCode='ENU') a inner join displaystringview on a.monitorid=ltstringid
where languageCode='ENU') b inner join displaystringview on b.ManagementPackid=ltstringid
where languageCode='ENU' where displayname ='SCCM Management Pack'
Roger

Management Pack reference/dependency cleanup tool

Similar Messages

Maybe you are looking for