Sealing a Management Pack before upgrading to R2

We are planning on upgrading our environment from 2012 SP1 to R2. I read somewhere that Management Packs should be sealed before upgrading. Not sure if the source was talking about a SM upgrade but seems logical it was. We have one particular Management
Pack with about 90% of our structure saved to and the Management Pack is unsealed. Should we seal it before upgrading to R2?
The article I read mentioned something about uninstalling and reinstalling of MP's during an upgrade and there was a potential for data to get lost during this process if the MP is unsealed.

Bit late to the party, but it doesn't make sense to seal things before a version upgrade. the decision on sealed vs unsealed is usually made within minutes of the creation of the management pack: does it contain things that need to stay constant and can
be referenced? then it needs to be sealed. does it contain things that might change with normal organization operations? probably needs to be unsealed.
Classes, Forms, Enum Roots, and other "internal" things, should be in sealed MPs. these are things that NEED to stay consistent. Enum values, offerings, workflows, templates, all could change as the org changes, and those should generally stay
in unsealed MPs. everything else is (as always) a gray area; use your judgement.
That being said, there is an argument for keeping stuff you care about in other MPs then the default "configuration library" MPs. those are provided by microsoft, and technically, a new patch COULD distribute a new version of those MPs that wipe
out your changed, but MS would be HARD PRESSED to justify that after assuring all of us that those are intended for customer data.

Similar Messages

Unable to create a management pack key token to seal a management pack using MPSeal.exe

Hi All,
I am trying to seal a custom made management pack. I refereed Jonathan
Almquist blog to do it. When i do it i get a error message Access is denied while creating a public key token.
Blog link: http://blogs.technet.com/b/jonathanalmquist/archive/2008/08/19/seal-a-management-pack.aspx
I get this error when i run the second command which i have Bolded below
Below are the directories i used.
C:\MP_Seal - To keep the SN.EXE & MPSEAL.exe and the unsealed management pack.
Created 2 folders named output & Pubkey in C:\MP_Seal
Opened command prompt Run as Administrator:
I am a domain admin and i have full access to the whole server
Ran the below commands to generate a Key
Note: I have changed my key name in this article to Mykey.Snk due to privacy issues.
1.C:\MP_Seal\sn -k C:\MP_Seal\Mykey.Snk
2.C:\MP_Seal\sn -p C:\MP_Seal\Mykey.Snk C:\MP_Seal\PubKey
3.C:\MP_Seal\sn -tp C:\MP_Seal\Pubkey
The first command how ever generated me a snk file. The second shows Access is denied
Also created the same setup in the D:\ Drive as well. Still the same issue occurs
Can any one help please.
Gautam.75801

Thank you for the reply Jon,
As i don't have a key generated already for me hence i am creating a new one. What i wanted to know is that is that, The first command however creates me a .SNK file. Is that enough for me to seal a management pack ? If yes what is the use of the second
and third mentioned below ?
1.C:\MP_Seal\sn -k C:\MP_Seal\Mykey.Snk
2.C:\MP_Seal\sn -p C:\MP_Seal\Mykey.Snk C:\MP_Seal\PubKey
3.C:\MP_Seal\sn -tp C:\MP_Seal\Pubkey
Gautam.75801

Management packs and upgrades

I am new to my position and to Service Manager. I can see such great potential of what Service Manager can do and how easy it could be to work with it however my company is afraid to make changes. They have said that not to far in the past
they did some customization and when they did the upgrade to 2012 r2 they lost everything - data included. They couldn't give me quite enough details as those that performed the task are no longer here. It went along the lines of a technician built management
packs that customized the screens. When they did the upgrade the management packs could no longer be used which resulted in them not being able to bring forward the data. They say they worked with Microsoft on the issue. From what I have been reading
this just doesn't sound like something that could happen in this extreme. However, they are now adamant that we cannot customize anything because of this. They want to use the system however people are miserable with it as out of the box just doesn't
fit what they need. How can I convince them that customization is not evil and precautions can be taken when upgrading where everything does not have to be redone?

You're dealing with psychology. Your company had a bad experience and now don't even want to risk that bad experience again.
It would definitely help to know what the heck your previous technicians did that could screw up Service Manager _that_ bad..especially if they were only customizing screens (I assume they were extending or creating forms).
But.. for some general advice on how to keep customizations "safe" and maybe calm your manager's fears, these are the guidelines I follow:
If your customizations include creating your own classes or relationships, always keep them in separate sealed management packs. Data warehouse extensions should also be kept in separate sealed MPs.
Console tasks, custom forms/form extensions, should generally be kept in their own management packs (sealed or unsealed).
Workflow rules, templates, and notification templates should be generally kept in their own unsealed management packs (so they can be easily modified from the console).
Since this is an extensible system, you should be doing regular backups of the Service Manager database. That way if someone messes something up really bad, you can always restore from a backup and lose maybe a day's worth of data.
Lastly, and most importantly, Service Manager is meant to be extended. Microsoft builds platforms. They don't build programs that can do everything. They build programs that can be _made_ to do everything. Every company is different..each has their
own flare for process, their own take on how a program should work. Service Manager is flexible enough to allow you to introduce your own flare and your own take on things. Instead of adapting your processes to Service Manager, you can adapt Service Manager
to your processes.
The downside, of course, is that with flexibility comes risk. Folks who extend these programs should be pretty familiar with how the underlying platform works. But if you take necessary precautions (follow the guidelines, do regular backups, etc) you can
reduce the risk significantly.
That's just my 2 cents :)

Ideas on adding licenses to a 8.X Communications Manager cluster before upgrade to v10.

Hi, hope is all well. This is something I started working with my global Cisco reseller but it takes sometime I wanted to make sure I see different options if possible to present. My company has deployments of collaboration products mainly on v8.x (all three main 8.0.2, 8.5.1 and 8.6.2) going to v10 during this year. Some already run on UCS but some are on MCS and will be late in migration. For those late, there are some growth need in end user/phone deployment but since v8 is end of sale, my provider may not be able to sell licenses.
If this is true, they might offer to buy v10 licenses with software subscription just like new deployment, which is not too bad at all since we will use this added amount on future v10 upgrade, but has anyone ever did that? I am afraid we use v10 PAK (if possible) to generate v8 license file, will render it not upgradable later. Reasoning is, let's say there is 1000 licenses on v8 with UCSS and we buy 15 v10 licenses downgraded to v8. Once we processo v8 to v10 upgrade on PUT, Cisco might see only 1000 original v8 liceses to provide upgrade instead of 1015.
Does it make sense or am I missing something here? Thank you very much for any suggestions.

UCSS and CUCM 8.X licenses have both been EoL. Even the existing UCSS+ ESW has been converted to SWSS.
Ref: CUCM 8.X Device and Licenses EoL notification
http://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/eos-eol-notice-c51-732309.html
Customers may be able to continue to purchase Cisco Unified Communications Manager Version 8.x Phone Units and Device License Units the Cisco Certified Refurbished Equipment program. Refurbished units may be available in limited supply for sale in certain countries on a first-come, first-served basis until the Last Date of Support has been reached. For information about the Cisco Certified Refurbished Equipment program, go to: http://www.cisco.com/go/eos.
Product Migration Options
Customers are encouraged to migrate to the Cisco Unified Communications Manager v 9.2 or later.
Ref: UCSS EoL
http://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-software-subscription/eos-eol-notice-c51-732026.html
-Terry
Please rate all helpful posts

Replace unsealed management pack with sealed

Hi,
Reaching out for some advise. We have some business services imported from SCOM DA:s via an unsealed management pack and would need (for dwh/reporting purpuses) to seal this management pack so that data is correctly transfered to DWH.
Is there any way to seal the management pack and import it without removing the unsealed management pack? If we export the unsealed mp - seal it - remove unsealed mp from SCSM - import the sealed MP - we loose all information about the business services.
Any suggestions?
Kind Regards,
Ezequiel
E.O

Hi E.O,
You cannot replace the unsealed MP with sealed one. What you can try is to export/import operations using csv files.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard:

Need Management packs for mpseal

Hello,
I need this MP to seeal another MP, can somone tell me from where to dld them?
Could not load management pack [ID=Microsoft.SystemCenter.Library, KeyToken=31bf3856ad364e35, Version=7.0.8433.0].
I found http://systemcentercore.com/?Get-ManagementPack=Microsoft.SystemCenter.Library&Version=7.0.8433.0
Nut this is the MPB not MP, how do i unpack it?
Br,
Adrian

No management pack for MPSeal. Management packs are sealed by using the MPSeal tool that is located in the SupportTools folder of the Operations Manager 2007 R2 distribution media. This is a command-line tool that creates a sealed .mp file from an unsealed
.xml file. After performing the sealing process, you can install the sealed management pack in your management group.
For Seal Management pack, you can check below link
http://blog.coretech.dk/msk/opsmgr-seal-a-management-pack-step-by-step/
For above issue, you can refer below link
http://www.systemcentercentral.com/forums-archive/topic/mpseal-fails-with-the-management-pack-was-not-found-in-the-store/
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"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

How to change management pack in incident template in scsm

We have created customized incident management pack and import that to scsm.Created templates using the this managementpack now i got request to edit or delete some Class properties in the customized managment pack.I have exported the management pack and
trying to edit the Class properties but those are Grey out.
Please let me know that how can i Edit or Delete the Class Properties in Customized management pack.
And Also let me know that i have created Templates using Customized management pack if i delete that mp and import a new mp in to SCSM how can i update the template with new mp.I tied to chnage the management pack in template but it is greyout.
Regards, H@ri

In which management pack are your class extension stored? Is this a sealed management pack (did you seal the management pack)? If it is a sealed MP than you have to modify the unsealed MP and seal it again with the same key.
If you export a sealed MP from SCSM it will be an unsealed copy of the MP but it doesn't work to modify this exported MP. So this is not an option.
If you want to delete custom properties in a MP you have to make sure that these properties aren't in use in the templates or work items.
Andreas Baumgarten | H&D International Group

Imported sealed Management Pack and its not showing up in Data Warehouse Job MPSyncJob

Hello,
When i try to Import a sealed Management Pack (with defined new Dimensions for Data Warehouse) it works fine, and it shows up under Management Packs under the Administration Pane. But its not showing up in the Data Warehouse Job "MPSyncJob".
No errors in the Eventlog on the DW Management Server and cant see any errors in failed Data Warehouse Jobs either.
I imported the MP three Days ago and still nothing.
Now what?
/Maekee

I have a smaller SCSM Lab that i can import this MP in and the classes are created in the DW. Now is the question why its not working in my PreProd env and why i dont get any errors in the Event Log? Anyone that can Point me in the right direction for
this?
/Maekee

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.

SCOM 2012 Disabling Sealed Management Packs

Hi, I need to disable some default MP in scom 2012 as part of testing and its a sealed MP. Could someone pls help me out to share a powershell script for executing the same.
Also I want to know, if I disable this MP, will it allow me to enable in future.
Pls advise..
Regards, Rajeev Parambil

There is no easy way of disabling all alerts, but this script could be used:
http://www.systemcentercentral.com/disabling-all-the-rulesmonitors-of-a-management-pack-in-scom-2012/
I don't know your situation, but I would recommend implementing the management pack in a demo environment, tune the alerts to a new management pack, and then import that custom mp into a production environment.

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.

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

Exported SCSM Default ServiceManager.RunbookActivity.Configuration Sealed management pack but unable to import later

Hi,
I exported SCSM default ServiceManager.RunbookActivity.Configuration Sealed management pack and remove it from SCSM. Later when I tried to import back the xml file it shows me this error.
Is there anyway to reinstate the original Sealed management pack?
Thanks
Jeron@Microsoft Technet

This error message is often related to missing the tag ManagementPublicKeyToken within the category tag. If you seal a MP but without defined the token then Service Manager will complain like this. And obviously the token and key must match.
What happens if you insert your keytoken value into the MP, seal it with your own key and then import it?
Somewhat like below:
<Categories>
<Category>
<ManagementPackVersion>xxx</ManagementPackVersion>
<ManagementPublicKeyToken>tokenhere</ManagementPublicKeyToken>
</Category>
http://codebeaver.blogspot.dk/

SCOM management packs upgrade

Hi,
When we upgrade a management pack in SCOM e.g. the OS management packs, Does it retains the overrides applied on rules and monitors in the previous version or we had to apply the overrides again on the latest imported management pack? Please advice.
Thanks
Daya Ram

Just keep in mind when you upgrade a management pack to read the management pack guide which is bundled with it.
Your overrides will be kept in a different management pack so no worries there but the creator of the MP can change the standard overrides in it's pack which could have an impact on your monitoring.
When upgrading an MP always check the MP guide and especially the "What's new" section to get a quick overview of the different changes in the MP.
It's doing common things uncommonly well that brings succes. Check out my SCOM link blog:
SCOM link blog

The Management Pack Import Failed - Upgrading to R2 and SCVMM 2012

Just finished applying UR4 to my Service Manager 2012 R2 environment. One of the final steps has you copy these MPs from your Virtual Machine Manager server to the Service Manager box.
Microsoft.SystemCenter.VirtualMachineManager.PRO.Library (3.2.7510.0)
Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library (3.2.7510.0)
Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library (3.2.7510.0)
Microsoft.SystemCenter.VirtualMachineManager.Library (3.2.7510.0)
Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery (3.2.7510.0)
I was able to import three of them, two failed with errors that appear to say specific MPs were not found. Do I need to import these additional MPs into Service Manager? This is one of the errors.
The management pack import failed.
Errors (8):
Could not load management pack [ID=Microsoft.SystemCenter.DataWarehouse.Library, KeyToken=31bf3856ad364e35, Version=7.0.8427.0]. The management pack was not found in the store.
: An error occurred while loading management pack c183c241-e7b5-a06f-d6d9-2d573485b91e from the database
Could not load management pack [ID=Microsoft.Windows.InternetInformationServices.2008, KeyToken=31bf3856ad364e35, Version=6.0.6539.0]. The management pack was not found in the store.
: An error occurred while loading management pack 1784bf83-89c5-68e5-2220-44d2c1715753 from the database
Could not load management pack [ID=Microsoft.Windows.InternetInformationServices.CommonLibrary, KeyToken=31bf3856ad364e35, Version=6.0.5000.0]. The management pack was not found in the store.
: An error occurred while loading management pack b739b9de-7c04-f1b9-fc56-4a118a6316ec from the database
Could not load management pack [ID=Microsoft.SQLServer.Library, KeyToken=31bf3856ad364e35, Version=6.0.5000.0]. The management pack was not found in the store.
: An error occurred while loading management pack bcd6dccf-c46c-a1f5-3c8d-bb4e99e2a6a3 from the database
Could not load management pack [ID=Microsoft.Windows.InternetInformationServices.2003, KeyToken=31bf3856ad364e35, Version=6.0.5000.0]. The management pack was not found in the store.
: An error occurred while loading management pack 7a920be5-d53c-fa2d-07a8-b415265e95b0 from the database
Could not load management pack [ID=System.Virtualization.Library, KeyToken=31bf3856ad364e35, Version=7.0.8430.0]. The management pack was not found in the store.
: An error occurred while loading management pack 474758fc-8648-c776-09f5-4033ee51efee from the database
Could not load management pack [ID=System.NetworkManagement.Library, KeyToken=31bf3856ad364e35, Version=7.0.8560.0]. The management pack was not found in the store.
: An error occurred while loading management pack dc6f8cbc-d89c-00bd-58eb-49a6d98d42b2 from the database
Could not load management pack [ID=Microsoft.SystemCenter.VirtualMachineManager.Library, KeyToken=31bf3856ad364e35, Version=3.2.7672.0]. The management pack was not found in the store.
: An error occurred while loading management pack 30113716-8134-9c58-5203-358d89357d74 from the database
Orange County District Attorney

Hi,
Those prerequisite management packs should be imported manually.
Here is a similar thread for your reference:
How to import VMM2012 Discovery Management Pack into System Center Service Manager
https://social.technet.microsoft.com/Forums/systemcenter/en-US/2d505f89-f7d5-4e3f-bd22-0ba80451e04d/how-to-import-vmm2012-discovery-management-pack-into-system-center-service-manager?forum=systemcenterservicemanager
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Sealing a Management Pack before upgrading to R2

Similar Messages

Maybe you are looking for