QuickTricks: Migrating subscriptions between Operations Manager environments (#SCOM, #PowerShell, #SYSCTR)

Recently during an OpsMgr 2007 R2 to OpsMgr 2012 engagement we needed to migrate all subscriptions, subscribers and channels  from the existing OpsMgr 2007 R2 production environment to the newly built OpsMgr 2012 QA and Production environments. The following is the process that we used which worked extremely well (though I’m not sure if it’s supported):

  1. Export the original Microsoft.SystemCenter.Notifications.Internal MP from the original environment (in this case OpsMgr 2007 R2)
  2. Export as a backup the Microsoft.SystemCenter.Notifications.Internal MP from OpsMgr 2012 (just in case anything goes wrong, it’s always good to have a backup).
  3. Edit the OpsMgr 2007 R2 Microsoft.SystemCenter.Notifications.Internal.xml and changed the version to 7.0.8560.1 (the OpsMgr 2012 version default is 7.0.8560.0 so changing it to 7.0.8560.0 allows the MP to be imported).
  4. It is important to disable all subscriptions so that not all of these will fire as soon as the MP has been added. This can be done in two ways:
    1. Before importing the management pack, alter the XML to set the subscriptions to be disabled by changing the subscriptions from: Enable=”true” to Enabled=”false” in the XML file.
    2. Subscriptions can be disabled after the MP is added but it’s much less noisy if this is done beforehand. If needed you can automate the process to disable all subscriptions using PowerShell (Get-SCOMNotificationSubscription | Disable-SCOMNotificationSubscription)  [This may take a while with lots of subscriptions…] [ This is an OpsMgr 2021 updated version of the information provided at  http://jamiebaldanza.org/2010/12/10/enable-or-disable-all-subscriptions-in-scom-2007-r2/]
  5. Import the edited version of the OpsMgr 2007 R2 Microsoft.SystemCenter.Notifications.Internal.xml into the OpsMgr 2012 environment.
  6. The subscriptions, subscribers and channels should now be the same as they were in the original environment.

Warning: Subscriptions defined to specific rules or monitors will not be able to be opened unless the rules and monitors are in the environment.


Special thanks to Blake Wilson for pointing this direction out to me!

2 thoughts on “QuickTricks: Migrating subscriptions between Operations Manager environments (#SCOM, #PowerShell, #SYSCTR)

  1. Pingback: Migrating subscriptions from Operations Manager 2007 to Operations Manager 2012 | Monitoring with SCOM and other interesting stuff (for myself, of course)

  2. Pingback: SCOM Link Collection Basics - Lagler-Gruener - Site Home - MSDN Blogs

Leave a Reply