Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Problem With Co-Management

PedFari

New Member
Messages
2
Reaction score
0
Points
1
Hello everyone,
Happy New Year in advance.


I'm currently facing an issue with several devices in Intune. I configured Co-Management correctly through Cloud Attach in SCCM, and all steps appear to be properly applied. However, the devices are reporting a Co-Management compliance error, and I have been unable to identify the root cause aside from the logs below.


Here is an excerpt from the client log:
Report detail: <ClientCoManagementMessage><MDMEnrollment><Enrolled Value="0" /><Provisioned Value="0" /><ServiceUri Value="" /><RegistrationKind Value="0" /><ScheduledEnrollTime Value="12/03/2025 16:03:54" /><ErrorCode Value="0" /><ErrorDetail Value="" /><EnrollmentRequestType Value="0" /></MDMEnrollment><CoMgmtPolicy><Enabled Value="0" /><PolicyReceived Value="1" /><WorkloadFlags Value="8197" /></CoMgmtPolicy></ClientCoManagementMessage> CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Co-management is disabled but expected to be enabled. CoManagementHandler 04/12/2025 09:59:07 24332 (0x5F0C)
Workloads rules are not compliant. CoManagementHandler 04/12/2025 09:59:07 24332 (0x5F0C)
Setting workload info: Allowed = 1, Flags = 12335 CoManagementHandler 04/12/2025 09:59:07 24332 (0x5F0C)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Enrolling device to MDM... Try #1 out of 3 CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Enrolling device with RegisterDeviceWithManagementUsingAADDeviceCredentials CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Device is already enrolled. CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
MDM enrollment succeeded CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Device is not provisioned CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
StateID or report hash is changed. Sending up the report for state 110. CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Report detail: <ClientCoManagementMessage><MDMEnrollment><Enrolled Value="0" /><Provisioned Value="0" /><ServiceUri Value="" /><RegistrationKind Value="0" /><ScheduledEnrollTime Value="12/03/2025 16:03:54" /><ErrorCode Value="1" /><ErrorDetail Value="Função incorreta.
" /><EnrollmentRequestType Value="0" /></MDMEnrollment><CoMgmtPolicy><Enabled Value="0" /><PolicyReceived Value="1" /><WorkloadFlags Value="8197" /></CoMgmtPolicy></ClientCoManagementMessage> CoManagementHandler 04/12/2025 09:59:07 20200 (0x4EE8)
Updating comanagement registry key to 0x302f CoManagementHandler 04/12/2025 09:59:07 24332 (0x5F0C)
CoManagement flags registry key updated. CoManagementHandler 04/12/2025 09:59:07 24332 (0x5F0C)
Setting co-management RS3 flags CoManagementHandler 04/12/2025 09:59:07 24332 (0x5F0C)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 09:59:08 24332 (0x5F0C)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 09:59:08 24332 (0x5F0C)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 09:59:08 24332 (0x5F0C)
Device is not provisioned CoManagementHandler 04/12/2025 09:59:08 24332 (0x5F0C)
StateID or report hash is changed. Sending up the report for state 100. CoManagementHandler 04/12/2025 09:59:08 24332 (0x5F0C)
Report detail: <ClientCoManagementMessage><MDMEnrollment><Enrolled Value="0" /><Provisioned Value="0" /><ServiceUri Value="" /><RegistrationKind Value="0" /><ScheduledEnrollTime Value="12/03/2025 16:03:54" /><ErrorCode Value="0" /><ErrorDetail Value="" /><EnrollmentRequestType Value="0" /></MDMEnrollment><CoMgmtPolicy><Enabled Value="0" /><PolicyReceived Value="1" /><WorkloadFlags Value="8197" /></CoMgmtPolicy></ClientCoManagementMessage> CoManagementHandler 04/12/2025 09:59:08 24332 (0x5F0C)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:47 22212 (0x56C4)
Device is not provisioned CoManagementHandler 04/12/2025 10:05:47 22212 (0x56C4)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:47 22212 (0x56C4)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:48 22212 (0x56C4)
Device is not provisioned CoManagementHandler 04/12/2025 10:05:48 22212 (0x56C4)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:48 22600 (0x5848)
Device is not provisioned CoManagementHandler 04/12/2025 10:05:48 22600 (0x5848)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:48 22212 (0x56C4)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:48 22600 (0x5848)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:48 22600 (0x5848)
Device is not provisioned CoManagementHandler 04/12/2025 10:05:48 22600 (0x5848)
Could not check enrollment url, 0x00000001: CoManagementHandler 04/12/2025 10:05:48 22600 (0x5848)

I have already performed dsregcmd /leave and dsregcmd /join, and I also reinstalled the SCCM client, but the issue persists.


I would like to create a well-structured script to attempt to repair or reset all components involved (AAD registration, MDM enrollment, Co-Management configuration, registry keys, etc.).


Could someone help me with guidance or an example script to automate these recovery steps?


Thank you in advance for any support.


Best regards,
Pedro
 
This is the actual error - Could not check enrollment URL, 0x00000001: CoManagementHandler. I am assuming you have setup the co-management part correctly. What I want you to check is if the entra sync is working correctly. Also, review the MDM event logs on co-managed device to see if you can get more information about this problem.
 

Forum statistics

Threads
7,125
Messages
27,823
Members
18,137
Latest member
jorsjo

Trending content

Back
Top