Let’s fix the Co-Management Settings Grayed Out Issue. SCCM 1910 version has a known issue with Co-management settings.
Customers reported that ConfigMgr 1910 Co-Management Settings Unexpectedly Grayed out or were available to configure. Let’s see how to FIX Co-Management Settings issues with the 1910 version.
Introduction
With the latest KB4540794 release, Microsoft provided a workaround to FIX the issues of co-management settings in the 1910 version of Configuration Manager.
The Goal of this fix is to remove existing co-management settings information from WMI so that it may be added back from the ConfigMgr console.
NOTE! – Don’t look for the KB454079 in your ConfigMgr console. It won’t be available on the console. From my perspective, this is a temporary workaround available to fix the issues with co-management.
- Issues#1 – Once you delete a setting from the Co-management node in the SCCM console, the Configure co-management option is unexpectedly grayed out and unavailable. This blocks you from re-enabling co-management.
- Issues #2 – In SCCM 1910, changes are not saved in the Properties window of the co-management setting.
Fix Co-Management Settings Issue
If you have co-management issue#1 explained above, the following steps should be followed. If you are experiencing issue#2, you might need to delete the co-management settings from the console and try again.
Issue#1
- Launch WBEMTEST from the server where you have installed SMS Provider
- Click on Connect
- Enter the WMI namespace name ” ROOT\SMS\site_PR3.“
- PR3 is my SCCM site code here. Replace this with your site code.
- Click on Connect
- Click on the Query button
- Enter the following query statement in the query box called Enter Query:
SELECT * FROM SMS_ConfigurationPolicy
WHERE CategoryInstance_UniqueIDs = 'SettingsAndPolicy:SMS_CoManagementSettings'
- Click on Apply
- The Query Result window should return an object list with the format SMS_ConfigurationPolicy.CI_ID={guid}
- Select and delete all objects in the result list, then click the Close button.
- You need to repeat the above step for all the objects
- Click on Query button again from WBEMTEST
- Enter the following query to find out the Co-management settings
SELECT * FROM SMS_ConfigurationPolicyAssignment WHERE AssignmentName = 'E3F913BB-98F4-4301-9032-C6D1D4891E0A'
- Click on APPLY
- As per the above result, there is nothing to delete
- If you have any objects, then you need to Delete all those objects that are returned from the above query
- Click the Close button and exit WBEMTEST
- After the above actions, the Configure co-management button should now be available in the console. Any future property changes will be saved correctly.
Issue#2
- Navigate to \Administration\Overview\Cloud Services\Co-management
- Right-click and Delete
- Recreate the settings as you can see co-management configuration
Results
Once you have gone through the above steps to fix the co-management settings option in SCCM|ConfigMgr 1910, you will be able to config.
Resources
- Co-management settings lost or unavailable after updating to Configuration Manager version 1910 – https://support.microsoft.com/en-us/help/4540794/co-management-settings-lost-or-unavailable-after-updating-to-configura
- SCCM 1910 Known Issues – https://www.anoopcnair.com/configmgr-1910-known-issues-bugs-fixessccm/
- SCCM WMI Configuration Checks using WMI Explorer – https://www.anoopcnair.com/wmi-explorer-sccm-configuration-manager/
Hey Anoop, thanks for this. Any suggestion for the issue I am facing – wizard runs successfully but nothing appears after that in console.
Hey Have you check the WMI entries after completing the wizard? Any clue from sccm log files ?
So I had no previous setting, yet mine is greyed out. I have verified nothing is in WMI, yet nothing has changed. Thoughts?
Anybody got any ideas here? I am still in the same boat. Upgraded to 2002. Everything in fix I have double checked, yet unable to configure co-management still.
Beautiful. Thank you for taking the time to post this. I had option 1 and it worked like a charm. No reboot needed. I demo these and just gave up on this early this year. I cycle through many Intune subscriptions which caused the problem. I already tried purging the data in the SQL table which broke other items. (not your post). Good thing I have SQL backups and system images. (demo only)
Can you pls try to use https://forum.howtomanagedevices.com for quick replies