locked
Exchange 2013 MP–Trying to understand why reimports do not recreate schema/dataset structure RRS feed

  • Question

  • I have a tier 3 SR open for this, and not getting much help. I am hoping someone out there is willing to explain the behavior of the DataWarehouseDataSets section of the Microsoft.Exchange.15 management pack XML. Specifically, why the SQL statements within the <Install> section only execute the very first time the MP is imported in a management group, and why the SQL statements within the <Uninstall> section never execute when the MP is deleted (using the console). I’m sure some of you have wondered the same thing.

    When you delete the MP, you will start getting standarddataset workflow errors (presumably because the <Uninstall> statements do not execute). This was first reported with the Exchange 2010 MP. Manually executing the SQL statements contained within <Uninstall> seems to have cleanly deleted the Exchange 2013 schema within the DW. I thought this was required before the Exchange 2013 dataset structure would be recreated, yet it is not with subsequent reimports of the MP. There are no DW errors at all.

    If someone knows why <Install> only executes on the very first import, that would be great. Is it necessary to force this MP to groom itself out after deletion?

    Thanks–Drew

    Wednesday, January 7, 2015 3:40 AM

Answers

  • Thank you for replying.

    The first issue investigated was what can happen after deleting the Exchange MP from your management group: DW StandardDataSet workflow errors pointing to Exchange datasets. These would only stop after deleting the Exchange StandardDataSet entries.

    Let's say you for some reason you later reimport the Exchange MP and need to collect that data once again. The StandardDataSet entries are not recreated. The Exchange MP <Install> and <Uninstall> sections contain SQL statements that create and remove the StandardDataSet structure. <Install> only runs the very first time the MP is imported, and the <Uninstall> statements never execute, which they should when the MP is deleted--otherwise why would you have an <Uninstall> block of code..

    We figured out what must be manually deleted to 'clean out' the StandardDataSet structure so a) no errors after the MP is deleted and b) the <Install> statements execute when the MP is reimported. Internal tickets have been filed to correct <Uninstall> so it triggers.

    There will be a KB article published about this so customers no longer needing Exchange 2010 or 2013 monitoring won't have to keep those MP's imported.

    Sunday, January 18, 2015 9:08 PM

All replies

  • Hi Drew,

    As we know, deleting an MP will delete the data in SCOM / SCSM that it defines.  For instance deleting the SQL 2008 MP from SCOM will delete all SQL 2008 databases that are being monitored from SCOM.  Deleting an MP defining a custom class in SCSM (a customized incident class for example) will remove all instances of that customized class.

    Do you mean that when you delete the Exchange MP, you are getting errors, would you please share out the error message for troubleshoot.

    In addition, here is a blog for management pack best practices.

    http://blogs.technet.com/b/antoni/archive/2013/10/09/system-center-service-manager-operations-manager-management-pack-and-naming-convention-best-practices.aspx

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Proposed as answer by Yan Li_ Wednesday, January 14, 2015 1:55 AM
    Thursday, January 8, 2015 5:59 AM
  • Thank you for replying.

    The first issue investigated was what can happen after deleting the Exchange MP from your management group: DW StandardDataSet workflow errors pointing to Exchange datasets. These would only stop after deleting the Exchange StandardDataSet entries.

    Let's say you for some reason you later reimport the Exchange MP and need to collect that data once again. The StandardDataSet entries are not recreated. The Exchange MP <Install> and <Uninstall> sections contain SQL statements that create and remove the StandardDataSet structure. <Install> only runs the very first time the MP is imported, and the <Uninstall> statements never execute, which they should when the MP is deleted--otherwise why would you have an <Uninstall> block of code..

    We figured out what must be manually deleted to 'clean out' the StandardDataSet structure so a) no errors after the MP is deleted and b) the <Install> statements execute when the MP is reimported. Internal tickets have been filed to correct <Uninstall> so it triggers.

    There will be a KB article published about this so customers no longer needing Exchange 2010 or 2013 monitoring won't have to keep those MP's imported.

    Sunday, January 18, 2015 9:08 PM