Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

← Ideas

Unable Configure Co-Management grayed out on 1802.

Unable Configure Co-Management grayed out on 1802.

22 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Marthinus shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

15 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Sunny commented  ·   ·  Flag as inappropriate

    @M25L1: How did you fix this? I have same issue, Wizard is now available but it doesnt show anything once completed.

  • Matt M commented  ·   ·  Flag as inappropriate

    So MS found & fixed the issue. They can't officially classify it as a bug yet...

    Not sure how deep i can go on this as i need to go over things a few more times but basically.. those with this issue, you're missing the proper record in CI_CategoryInstances table & CI_CICategories

    BACKUP YOUR DB (PROPERLY) before running these SQL commands

    SELECT * FROM CI_ConfigurationItems WHERE CI_UniqueID = 'GLOBAL/CCMSS_CoManagement_Settings' -- Check CI ID
    SELECT * FROM CI_CategoryInstances WHERE CategoryInstance_UniqueID like '%SettingsAndPolicy:2A458DA%' -- Check Parent Category Instance ID
    SELECT * FROM CI_CategoryInstances WHERE CategoryInstance_UniqueID = 'SettingsAndPolicy:SMS_CoManagementSettings' -- Category InstanceID
    *(you will need these above values for the below tasks)

    delete from CI_CategoryInstances where CategoryInstanceID='<YOUROLDCATEGORYINSTANCEID>'

    Insert into CI_CategoryInstances (CategoryInstance_UniqueID, CategoryTypeName, DateLastModified,SourceSite,ParentCategoryInstanceID,IsDeleted,rowversion) values ('SettingsAndPolicy:SMS_CoManagementSettings','SettingsAndPolicy',GETDATE(),'<SITECODE>',<YOURPARENTCATEGORYINSTANCEID>,0,default)
    Insert into CI_CICategories (CI_ID,CategoryInstanceID,rowversion) values (<YOURCIID>,<YOURCATEGORYINSTANCEID>, DEFAULT)

    You will need to adjust the < > values to your own environment.

    Microsoft, if this post is something that should not be posted, please delete.

    MS worked their A$$ off for the past while (little over a month) and i cannot give their lead SCCM techs enough credit.

  • Matt M commented  ·   ·  Flag as inappropriate

    Ya same question to M25L1, nothing in the list after running that query, then re-running the config, MS has been on this issue for weeks now for my install.

  • David Jardim commented  ·   ·  Flag as inappropriate

    I am also unable configure co-management in version 1906. No co-management CIs where found in my instance (not previously set up)

  • M25L1 commented  ·   ·  Flag as inappropriate

    That delete query resolves the greyed out part, but I was unable to create a new one. The wizard starts, but as soon as I click "Done". Nothing appears in the list...

    EDIT: Fixed it.

  • Richard Davis commented  ·   ·  Flag as inappropriate

    This delete query resolves my issue

    delete from CI_CategoryInstances WHERE CategoryInstance_UniqueID = 'SettingsAndPolicy:SMS_CoManagementSettings'

  • Rob commented  ·   ·  Flag as inappropriate

    I can confirm that Full Administrator with ALL security scopes solves this issue. Also in 1806.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Guys, it turns out the SCCM console in build 1802 (with or without the latest KB) has been changed so the the co-management feature is only available (not greyed out) to an 'Full Administrator' with ALL security scopes. The Default security scope is not enough.

    Make this change, restart the console and you should be good to go with enabling co-management.

Ideas: Co-Management

Categories

Feedback and Knowledge Base

(thinking…)