Devices no longer enrolling into co-management

amhof1 1 Reputation point
2021-07-22T13:29:27.76+00:00

We have recently started having an issue with Windows 10 devices (20H2) having the Configuration Manager client take a long time to completely install on devices after imaging completes and then are not enrolling into co-management. The CoMGMTSettingsProd configuration is showing as Non-Compliant. Everything was working fine up until the end of last month. No changes have been made in SCCM or Intune. We have been testing Autopilot and if I run Autopilot on a device it will enable co-management with no issues. Anyone have any ideas as to why the client install and co-management config would not be working properly only on Configuration Manager (current version) imaged devices???

Microsoft Configuration Manager
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Amandayou-MSFT 11,136 Reputation points
    2021-07-23T03:24:27.063+00:00

    Hi @amhof1 ,

    Could we know Windows 10 devices (20H2) is the new device which have not been enrolled into intune and just been CM agent? If so, kindly check if configure upload is all the device managed by sccm or specific collection. If specific collection, the new client may not be recognized as the co-managed device.

    Here is the screenshot, please refer it:

    117237-723.png


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.