How to remove custom attributes created in Windows Core LIbrary Management Pack from System Center Operations Manager 1807?

Keith Langley 21 Reputation points
2020-11-03T15:29:03.85+00:00

A custom attribute was mistakenly created in Windows Core Library MP. This attribute is causing WMI errors on all of my servers. How can I remove the attribute from Windows Core LIbrary?

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,420 questions
0 comments No comments
{count} votes

Accepted answer
  1. CyrAz 5,181 Reputation points
    2020-11-04T18:21:15.24+00:00

    So, the discovery causing your issue is called "Group - SEC_SRVADMIN_SERVER_SUPPORTDiscovery" and is stored in the Management Pack called "AD.Partner.Management.Pack"
    (try Get-SCOMManagementPack -Name "AD.Partner.Management.Pack" to find its displayname)

    If I were you, I would export that MP and check in the XML code what that discovery does precisely before savagely deleting it.

    0 comments No comments

13 additional answers

Sort by: Most helpful
  1. CyrAz 5,181 Reputation points
    2020-11-04T17:34:24.513+00:00

    Try running the following powershell command, it should give you details about the discovery that contains the wmi query :

    Get-SCOMDiscovery -Name "AttributeDiscoveryGeneratedByUIedec1a0ad2994c53bf4f6ede5ffee9b8"

    0 comments No comments

  2. Keith Langley 21 Reputation points
    2020-11-04T18:06:36.587+00:00

    That's not returning any results

    PS C:\WINDOWS\system32> Get-SCOMDiscovery -Name "AttributeDiscoveryGeneratedByUI"
    PS C:\WINDOWS\system32>


  3. Keith Langley 21 Reputation points
    2020-11-04T18:10:08.253+00:00

    PS C:\WINDOWS\system32> Get-SCOMDiscovery -Name "AttributeDiscoveryGeneratedByUIedec1a0ad2994c53bf4f6ede5ffee9b8"

    HasNonCategoryOverride : False
    Enabled : true
    Target : ManagementPackElementUniqueIdentifier=e817d034-02e8-294c-3509-01ca25481689
    ConfirmDelivery : False
    Remotable : True
    Priority : Normal
    Category : PerformanceCollection
    DataSource : AttributeDiscoveryGeneratedByUI6c40a35c6a5a42d38afd8d1259e34fe2
    DiscoveryClassCollection : {ManagementPackElementUniqueIdentifier=45700ea9-d077-e184-cfa8-b43c5323e5e0}
    DiscoveryRelationshipCollection : {}
    XmlTag : Discovery
    ManagementGroup : ***********
    ManagementGroupId : 6a9062d8-aa21-9add-d84f-8d2baccc6747
    Identifier : 1|AD.Partner.Management.Pack|1.0.0.0|AttributeDiscoveryGeneratedByUIedec1a0ad2994c53b
    f4f6ede5ffee9b8||
    Name : AttributeDiscoveryGeneratedByUIedec1a0ad2994c53bf4f6ede5ffee9b8
    Id : 2ad0a8df-eacc-41b2-40ad-c55216396aa0
    DisplayName : Group - SEC_SRVADMIN_SERVER_SUPPORTDiscovery
    Description :
    LanguageCode : ENU
    Comment :
    Status : Unchanged
    LastModified : 10/23/20 7:10:38 PM
    TimeAdded : 10/23/20 7:10:38 PM
    InstanceName :

    0 comments No comments

  4. Keith Langley 21 Reputation points
    2020-11-04T18:22:25.317+00:00

    Removing AD.Partner.Management.Pack corrected the issue.

    Thank you very much for your help