It's one of the MPs that is delivered as part of CU4. They're in
C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2449679\ManagementPacks on any system you did the server update on.
Did you follow Kevin Holman's procedures for applying CU4?
http://blogs.technet.com/b/kevinholman/archive/2011/02/01/opsmgr-2007-r2-cu4-rollup-hotfix-ships-and-my-experience-installing-it.aspx
Yes, i followed this procedure. and on production and on test systems i don't have this management pack in any locations. I can see it only in operations console.
Just a reminder on how management packs work - they get imported into the management group. The management group then determines when and where they get distributed.
Being present in a directory on the file system as noted above is not a sign that they have been imported - but if they are shown in your operations console, then you are good to go.
Hi
But they won't be "good to go" for the Authoring console which is what the question asks.
But "when i export a management pack and try to open it in authoring console, the authoring console promt to locate Microsoft.SystemCenter.Library.mp v 6.1.7221.61"
This is because the MP that is being opened references the Microsoft.SystemCenter.Library.mp v 6.1.7221.61 MP.
If you log on to your RMS, and take a look in the \Program Files\System Center Operations Manager 2007\ folder then you'll see the core set of Management Packs. I'd copy them across to your Authoring Console machine and set the references to them there.
Cheers
Graham
Not a long term solution, but it's unlikely that you actually REQUIRE the patched version of the library. After exporting change the version number to
FROM
<Reference Alias="SystemCenter">
<ID>Microsoft.SystemCenter.Library</ID>
<Version>6.1.7221.61</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
TO
<Reference Alias="SystemCenter">
<ID>Microsoft.SystemCenter.Library</ID>
<Version>6.1.7221.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
Dan,
Any updates on this? We release MP's from a Dev MgmtGrp to a Prd MgmtGrp. We use the authoring console for finetuning the MP's. Now we can't change the MP's using the authoring console. The workaround mentioned by dbabob56 works, but how can we work with the new library if the file is not available?
Best regards,
M
Hi Marc
I'll escalate to see if there is a route to get this prior to CU5. Sadly although the web applications mp was provided as part of the previous cumulative update (it went into the management pack folder), this mp went straight into the database which is causing the issue for everyone.
Regards
Graham
Any updates on this?
This just gives us more ammunition when we see CU5 come out and we decide not to deploy it.
you can get the mp by opening a call to microsoft.
i've just did and got the mp within 4 hours after i made the case. i suppose its free of charge, but i really don't know as my compagny has a premier contract.
Here is the link for the KB article to download the MPs.
http://support.microsoft.com/kb/2590414
- Proposed as answer by JG Giant Thursday, August 04, 2011 10:15 PM
- Marked as answer by Arie de HaanModerator Thursday, August 18, 2011 10:03 AM
Hello,
This link provides a file which is updated in the SCOM Console but not on the physical file on disk as stated earlier.
I have the same problem again with CU5 and over Microsoft.SystemCenter.Library.mp does not have its version changed on disk but only in the console , it is really annoying!!!
Thanks,
Dom
Thanks Bob I think I found the trick
http://www.bictt.com/blogs/bictt.php/2012/02/07/operations-manager-internal-connector
DOm
Thanks worked for me in Authoring when it was asking me for Microsoft.SystemCenter.Library ver 6.1.7221.61Here is the link for the KB article to download the MPs.