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

Similar Messages

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!

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

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.

Adjusting queuestatistics.vbs timeout in MSMQ management pack

Hi all,
I'm running SCOM 2012 R2 and my question is specific to the MSMQ 6.0.6700.88 management pack. I'm seeing a few alerts titled
"Operations Manager failed to start a process", with the alert details saying "Forced to terminate the following process started at x:xx:xx PM because it ran past the configured timeout 300 seconds"
Command executed: "C:\Windows\system32\cscript.exe" /nologo "queuestatistics.vbs" server.domain.local false
One or more workflows were affected by this.
Workflow name: many
Instance name: many
Instance ID: many
etc etc - we've all seen these errors before.
When I run the script manually on the server as local system, the script runs fine, but takes around 4 mins (360 seconds) to finish executing.
I want to adjust the timeout threshold for this script, and I understand that for this script timeout, there is no override available via the SCOM console, and I need to go into the management pack.
I've exported the management pack and I've found the vbs script contained within the management pack, however I was just looking for some guidance on what XML field(s) I should change to adjust the timeout? Searching through the management pack I've
found several areas that might be what I'm after.
I guess I'm just after someone to point me at the right DataSource or Rule ID or something to edit, rather than me just taking a guess and reimporting a busted management pack that I then need to clean up.
Cheers,
Noel.
http://www.dreamension.net

Thanks Michael!
That didn't quite work out for me, but I eventually got it working. At first I did change the <TimeoutSeconds> value under the script as per your diagram, and after reimporting the management pack and flushing the health service cache for good
measure, the script still failed with a 300 second timeout.
However I started looking through the rules in more detail, and I found some rules that reference a datasource with "Queue.Statistics" in the name. I figured that's a close enough match to the VB script that's also running. Here is a screen grab...
There were several rules & datasources that had "Microsoft.MSMQ.2008R2.DataSource.Queue.Statistics" in the name, and I changed the "TimeoutSeconds" value for all of them to 360 seconds. I then reimported the management pack again, and now the script
is completing.
Thanks very much for your assistance with this and giving me a nudge in the right direction.
http://www.dreamension.net

Can any one tell me how to pull out a sealed management pack key token

Hi All,
Can any one tell me how to pull out a sealed management pack key token. I want to add dependencies to a management pointing towards a sealed management pack for which a "management pack key token" is required which i need to add in the XML File
of the management pack. Can any one please tell me how to fetch that information.

Hi Gautam,
If you need to reference one management pack in another management pack, then you will need to know what the public key token is. When referencing a Microsoft management pack, it is easy as Microsoft always have the same key which is 31bf3856ad364e35 but
if you need publickey token for other then MS management pack then you can simply run a SQL querry in your OperationManagerDB.
select * from dbo.ManagementPack where MPName = 'Type your ManagementPackID'
ManagementPackID will be present of the properties of the Management Pack.
In that case the management pack should be imported in your SCOM environment.
And you will get Public key token only for sealed Management packs not for unsealed.

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

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 :)

Cannot import sealed management pack from unsealed management pack

We have unsealed management pack imported to our scsm 2012. It has an additional dropdown list with list. But now we are now going to seal it but when we are going to import it now, it says it cannot be imported because there is already unsealed management
pack with the same name. If we are going to delete that unsealed managmeent pack, we may lost are data for that field. Is there any way for this?

As workaround you can export data to temp location (XML or something like this), remove unsealed, import new sealed and import data back from temp location. This can be easy done with SMLets
SCSMSolutions
email: freemanru (at) gmail (dot) com
I'm having the same issue as the original poster. I foolishly have been working with an unsealed management pack in our SCSM 2012 SP1, UR2 environment that contains a list of "Locations") We need this to be sealed so it will not only sync to
the DW, but also so we can reference it with new templates/workflows.
I'm hoping for an answer from Anton on more detailed instructions for this workaround, to help a newbie to SCSM and SMLets.

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.

Sealed and unsealed management pack in scom ?

Dear all ,
What is Difference between sealed and unsealed management pack in scom?
I know like override alert can not be saved in sealed MP , is there any thing else ?
Sengo.

Hi,
A sealed management pack is a binary file that cannot be edited. An unsealed management pack is an XML file that can be edited. Sealed management packs should have an .mp extension, while unsealed management packs should have an .xml extension.
In general, management packs obtained from an application or hardware device vendor are sealed.
Although you cannot change the settings in a sealed management pack, you can still customize the applied settings of a management pack after it is imported by using overrides or by creating additional settings such as rules, monitors, and tasks that supersede
the management pack's default settings. All customizations that you create are saved to a separate management pack file.
Management packs can only reference another management pack if the management pack that is referenced is sealed
Regards,
Yan Li
Regards, Yan Li

Again - Active Directory Management Pack - AD MP - SCOM 2012R2 - AD 2012R2 - Action / RunAs Account permissions

Hi,
after reading many Posts and Blogs i came to the conclusion that it is still unclear to me what is needed to Monitor Active Directory successfully and what is the securest way configuring the RunAs or Action Account. I hope the experts here can make a clear
Statement to answer the question for all time ;-)
1. Action Account:
Here is described what permissions and rights are needed to use a low-privileged account:
https://technet.microsoft.com/en-us/library/hh212808.aspx
Now you might say: that was asked and answered so many times..you are right, but the answer was from run as "local System" to "you Need local admin". So also the AD MP documentation still says you Need a local Admin account.
here are other references which says you Need local admin rights:
http://micloud.azurewebsites.net//2014/02/26/scom-agent-grayed-out-when-trying-to-monitor-domain-controllers/
Even Kevin Holman says here
https://social.technet.microsoft.com/Forums/systemcenter/en-US/2a0e5a2b-a3d9-42d4-8474-9f690007caa0/opsmgrlatency-cn-gets-auto-created-in-domain-not-configuration:
"Basically - if your domain controllers are running as local system default agent action account, in most cases you will not need to ever set up any replication monitoring run-as accounts.... as local system on a DC has all the rights necessary.
(in most cases).
"Simple questions: Is this really enought to Monitor every aspect of an ActiveDirectory Domain and Domain Controller using a low privilege account the the permissions in the article? Or is using local System better? Is there a difference when
using SCOM2012R2 with the new Agent? Most documentation referes to SCOM2007(except the replication Monitoring where it is clear that other permissions are needed:
http://blogs.technet.com/b/jimmyharper/archive/2009/05/20/configuring-or-disabling-replication-monitoring-in-the-active-directory-management-pack.aspx )

The MP guide is not really clear about it. The only thing they are clear about is whenever you want to use client monitoring. In those situations low privileged will not work.
For each of the client-side monitoring scripts to run successfully, the
Action Account must be a member of the Administrators group on both the computer
on which the client management pack is running and the domain controller that is being monitored. The
Action Account must also be a member of the
Operations Manager Administrators group, which is configured through the Operations console in so that all the scripts that are configured on the Root Management Server can run properly
Both a local system and domain admin are a risk. If someone loads a malicious management pack that makes changes to the AD services you are screwed. The local system has unrestricted access to local resources including domain services.
The only reason I don't want a domain admin account in SCOM is that you have an additional layer where the password potentially could be retrieved. That's not the case with a local system account. But the risks are the same.
See: https://msdn.microsoft.com/en-us/library/ms677973%28v=vs.85%29.aspx
But this not an answer to your question. :-)

Applications Change Management Pack 3.1 is now available

E-Business Suite Applications Technology Group has recently released Application Change Management Pack (ACMP) Release 3.1 and Application Management Pack (AMP) Release 3.1.
As you might be aware, Application Change Management Pack is Oracle's offering for customers to monitor and manage Oracle E-Business Suite changes. Application Change Management Pack provides a centralized view to monitor and orchestrate changes (both functional and technical) across multiple Oracle E-Business Suite systems.
In release 3.1 Application Change Management Pack has been enhanced to provide more control and flexibility in managing Oracle E-Business Suite changes.
Some of the key distinguishing features of the new release include:
* Change Approval Framework: Changes orchestrated through Application Change Management Pack can now be controlled through the new change approval framework in Release 3.1. Users can now be segregated as approvers across Oracle E-Business Suite system(s) and modules (Customization Manager, Patch Manager or Setup Manager). Built in notification capability enables approver(s)/requester to be intimated about the status of relevant change requests. It also provides an implicit audit trail mechanism.
* Integrated Custom Application Management: An integrated custom applications management feature enables users to easily register new custom applications across Oracle E-Business Suite systems and also track and validate existing custom applications in a standard way. This dashboard also helps track custom objects, packages and file meta-data associated with custom applications.
* Pre-requisite Patch Analysis: Oracle E-Business Suite patches can now be analyzed for Pre-requisites prior to deployment in the target system. The analysis also verifies whether the pre-requisites are already available (in the target system) and if not, an option to add them to the patch job.
* Offline Transformation: For the very first time, users have the ability to download Oracle E-Business Suite setup data in Microsoft Excel document. Once downloaded, the Setup Data can be edited or new data can be entered into the worksheets. Data is validated within the Microsoft Excel file and also while uploading into Setup Manager.
* Built-in Intelligence: Release 3.1 has numerous minor enhancements that provide necessary intelligence for a seamless change orchestration. A few examples are:
* Automated file driver meta-data generation for new files and $Header handling
* Customization Package impact analysis report
* Advanced filtering options for setup migration
* Improved Usability: Release 3.1 contains numerous usability and reporting enhancements to ensure better integration with third party systems like source control systems and to foster collaborative development.
Licensing
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.1 is a mandatory prerequisite for Application Change Management Pack for Oracle E-Business Suite Version 3.1 and should be licensed separately.
Upgrade
This pack supersedes the Oracle Application Management Pack for Oracle E-Business Suite 3.0. An upgrade path to Release 3.1 is provided from Release 3.0 only. Therefore it is mandatory for the existing installations to be at the AMP-ACMP Release 3.0 level before upgrading to Release 3.1.
Downloads
[Application Management Pack and Application Change Management Pack for Oracle E-Business Suite Version 3.1 (Patch 8333939) |http://updates.oracle.com/Orion/PatchDetails/handle_rel_change?release=5623100&plat_lang=46P&patch_file=&file_id=&password_required=&password_required_readme=&merged_trans=&aru=11452056&patch_num=8333939&patch_num_id=1103773&default_release=5623100&default_plat_lang=46P&default_compatible_with=&patch_password=&orderby=&direction=&no_header=0]
References
[Getting Started with Oracle Application Management Pack and Application Change Management Pack for Oracle E-Business Suite Version 3.1 (Metalink Note 982302.1)| https://supporthtml.oracle.com/ep/faces/secure/km/DocumentDisplay.jspx?id=982302.1#6 ]
[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://supporthtml.oracle.com/ep/faces/secure/km/DocumentDisplay.jspx?id=812315.1#4]
[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]
[Oracle Enterprise Manager Documentation|http://www.oracle.com/technology/documentation/oem.html]

Srinivas:
AMP/ACP 3.1 is certified and tested on OEM 10.2.0.5 with Linux.
We would like to understand how you were trying to install the pack. Please note that AMP/ACP 3.0 installation is a prerequisite before installing AMP/ACP 3.1. So, did you check that the AMP/ACP 3.0 installation completed without errors.
For details, please refer to the Metalink document ID 982302.1 for more details regarding the same. I would strongly recommend you to follow the 'Oracle Application Management Pack for Oracle E-Business Suite Installation Guide (PDF)' .
If the issues still persists, please log a SR for the same and let us know the SR#.
Thanks,
Lokesh

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

FIM Rerporting management pack multivalue references

Similar Messages

Maybe you are looking for