locked
Migrate Management Packs from UAT to Production RRS feed

  • Question

  • Hi

    I have a management pack for our internal applications in our UAT environment. The way the applications work is when there is a problem it will write an event to the event log, and SCOM event monitors will pick these up and process them. Each event monitor is targeted at a specific computer group.

    I would like to be able to migrate this management pack across to the production management group however it seems that I would also need to migrate the computer groups across (where the servers in UAT do not exist in Production). 

    I was thinking a way around this would be to have the event monitors in one management pack (Let's call it "Applications Management Pack") and the computer groups in a separate management pack "Computer Group Management Pack". This would allow me to export just the Applications Management Pack and have two separate Computer Group management packs for each environment. This however doesn't seem to work as it looks like the event monitor targets need to be in the same computer group.

    Is there any other way around this problem? 

    Thanks in advance.

    Tuesday, March 8, 2011 2:17 AM

Answers

  • I think that you have to target your monitor to a specific class (may be a custom class that you have to create to your both environments) and not to a group.

     


    Christopher Keyaert - My OpsMgr/SCOM blog : http://www.vnext.be
    • Proposed as answer by Nicholas Li Wednesday, March 9, 2011 3:27 AM
    • Marked as answer by Nicholas Li Friday, March 11, 2011 9:43 AM
    Tuesday, March 8, 2011 8:47 AM
  • i think you've probably created overrides to enable the rules to for a group (you can't target a group as it would run on the group but not its members) and have targetted the rules/monitors to windows computer or server os or something.

    Like christopher creating a class for the application would probably be best (running a discovery on the os classes, just a simple registry entry to see if the application exists on a machine would do).

    The alternative would be to create want you have done now, without the group override. Seal the mp and override it for the group (now you must override in a different mp). Dont forget to save the key you use :)


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by Nicholas Li Friday, March 11, 2011 9:43 AM
    Wednesday, March 9, 2011 11:02 AM

All replies

  • I think that you have to target your monitor to a specific class (may be a custom class that you have to create to your both environments) and not to a group.

     


    Christopher Keyaert - My OpsMgr/SCOM blog : http://www.vnext.be
    • Proposed as answer by Nicholas Li Wednesday, March 9, 2011 3:27 AM
    • Marked as answer by Nicholas Li Friday, March 11, 2011 9:43 AM
    Tuesday, March 8, 2011 8:47 AM
  • i think you've probably created overrides to enable the rules to for a group (you can't target a group as it would run on the group but not its members) and have targetted the rules/monitors to windows computer or server os or something.

    Like christopher creating a class for the application would probably be best (running a discovery on the os classes, just a simple registry entry to see if the application exists on a machine would do).

    The alternative would be to create want you have done now, without the group override. Seal the mp and override it for the group (now you must override in a different mp). Dont forget to save the key you use :)


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by Nicholas Li Friday, March 11, 2011 9:43 AM
    Wednesday, March 9, 2011 11:02 AM