Forum Discussion

Le_Michel's avatar
Le_Michel
Brass Contributor
Sep 12, 2022
Solved

MECM co-management enrollment not working

Hello,   We are trying to enroll devices in intune using MECM Devices are Hybrid azure AD joined. Devices are member of the pilot collection :     CoManagementHandler.log shows the follo...
Intune
mobile device management (mdm)
  • Le_Michel's avatar
    Le_Michel
    Jan 09, 2023

    yannick_sierro Yes, it's solved.

     

    All co-management policies were duplicated in the SCCM database. And the client received the corrupted policies.
    The cause is that the first time we tried to activate the cloud attach, the operation did not complete due to lack of permissions on azure. Some uncomplete policies were left in the database.
    We removed the cloud attach, deleted policies from the DB with help of the escalation engineer and recreated the cloud attach.

KurtBMayer's avatar
KurtBMayer
Iron Contributor
Sep 12, 2022

Le_Michel 

 

Intune Enrollment using Group Policy | Automatic Enrollment AVD VMs 

See this article. Check the MDM User Scope and enable the policy "Enable Automatic MDM enrollment using Default azure AD credentials."

 

Troubleshooting Windows device enrollment errors in Intune 

Otherwise see that article for other possible error conditions reported in the log.

 

HOW TO ENABLE CO-MANAGEMENT IN SCCM 1902 

And per this other article, make sure you've followed all needed co-management setup steps.

 

Please like or mark this thread as answered if it's helpful, thanks!

  • Le_Michel's avatar
    Le_Michel
    Brass Contributor
    Sep 20, 2022
    Hello,

    We have opened a support case with Microsoft. I'll let you know the findings.
    Our intent is to rely on MECM to start the onboarding process.
    • Sorcia25910's avatar
      Sorcia25910
      Copper Contributor
      Oct 12, 2022
      Hi Le_Michel... any news about this issue, we have the same with any devices (another register and enrolled right)...

      <![LOG[Initializing co-management agent...]LOG]!><time="11:19:29.514+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="comgmtagent.cpp:194">
      <![LOG[Loaded EnrollPending=0, UseRandomization=0, LogonRetriesCount=0, ScheduledTime=0, ErrorCode=0x0, ExpectedWorkloadFlags=12543, LastState=100, EnrollmentRequestType=0]LOG]!><time="11:19:30.233+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="comgmtagent.cpp:224">
      <![LOG[Auto enrollment agent is initialized.]LOG]!><time="11:19:30.233+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="comgmtagent.cpp:280">
      <![LOG[Device is enrolled.]LOG]!><time="11:19:30.233+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="comgmtagent.cpp:491">
      <![LOG[Updating comanagement registry key to 0x30ff]LOG]!><time="11:19:30.498+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="ccmcomgmt.cpp:428">
      <![LOG[CoManagement flags registry key updated.]LOG]!><time="11:19:30.498+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="ccmcomgmt.cpp:433">
      <![LOG[Setting co-management RS3 flags]LOG]!><time="11:19:30.498+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="ccmcomgmt.cpp:476">
      <![LOG[Device is not provisioned]LOG]!><time="11:19:30.530+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="mdmreglib.cpp:708">
      <![LOG[State ID and report detail hash are not changed. No need to resend.]LOG]!><time="11:19:30.530+300" date="10-12-2022" component="CoManagementHandler" context="" type="1" thread="1644" file="comgmtagent.cpp:1810">
      • neelamnaidu's avatar
        neelamnaidu
        Copper Contributor
        Nov 15, 2023
        I am encountered with the same error... have you overcome this error can you please let me know please

Resources