UR1 contained a fix for a similar issue: http://blogs.technet.com/b/kevinholman/archive/2014/01/29/ur1-for-scom-2012-r2-step-by-step.aspx
I recommend you apply UR6 ASAP. http://blogs.technet.com/b/kevinholman/archive/2015/05/11/ur6-for-scom-2012-r2-step-by-step.aspx From: [email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Friday, June 12, 2015 1:04 PM To: '[email protected]' Subject: [msmom] RE: Modifying Application Name Issue: Yes, SCOM 2012 R2. Just the base release (v7.1.10226.0). From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Friday, June 12, 2015 10:53 AM To: [email protected]<mailto:[email protected]> Subject: [msmom] RE: Modifying Application Name Issue: We had a bug on renaming groups in sealed MP's - and system.service is about the same thing - I am wondering if this is the same issue. SCOM 2012 R2??? What UR are you on? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Friday, June 12, 2015 12:48 PM To: '[email protected]' Subject: [msmom] RE: Modifying Application Name Issue: Sorry, I didn't include this, but this is a sealed MP. I have it sealed via Visual Studio using their key generation command ("sn -k C:\Path\File.snk"). I confirmed the MP version number incremented from the original incorrect version to the version with the correct display name. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Friday, June 12, 2015 10:46 AM To: [email protected]<mailto:[email protected]> Subject: [msmom] RE: Modifying Application Name Issue: I have seen this a lot when importing an unsealed MP over and over... especially when modifying classes, properties, or display stuff. If you change the MP ID, and import - it usually shows up right because it is a "new" mp. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Friday, June 12, 2015 12:25 PM To: '[email protected]' Subject: [msmom] Modifying Application Name Issue: I set a display name incorrectly, loaded the MP into SCOM, then noticed my error. I went back and modified it, then updated the MP in SCOM, but the Display Name is still incorrectly labeled as "Rollups Class" (my initial mistake). It should read "Ascend SmartTouch ECM". Previously, when I made changes to an MP and loaded it into SCOM the changes happen within a couple minutes, but not in this case. I even went so far as deleting the MP entirely, waiting 24hrs, and reimporting it. However, the issue remains. Do I have to clear this from the Ops/DW database(s) manually or something? Relevant MP fragment: <ManagementPackFragment SchemaVersion="2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <TypeDefinitions> <EntityTypes> <ClassTypes> <ClassType ID="CHOMP.Ascend.Application" Base="System!System.Service" Accessibility="Public" Abstract="false" Hosted="false" Singleton="true" /> </ClassTypes> </EntityTypes> </TypeDefinitions> <LanguagePacks> <LanguagePack ID="ENU" IsDefault="true"> <DisplayStrings> <DisplayString ElementID="CHOMP.Ascend.Application"> <Name>Ascend SmartTouch ECM</Name> <Description>Overall view of Ascend TouchSmart ECM application health.</Description> </DisplayString> </DisplayStrings> </LanguagePack> </LanguagePacks> </ManagementPackFragment> What SCOM console shows: [cid:[email protected]] And Details: [cid:[email protected]] I've searched my entire XML output file and there is no "Rollups Class" string anywhere to be found now, but it remains in the console. Any help would be great. I did searches and forums browsing, but no luck. Thank you. -Geoff Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
