Forum Discussion
JoelTR
Jan 29, 2021Copper Contributor
Device registration in Co-Management - Error 0x8018002b
Hi All, I am a bit stumped as we have been experiencing issues getting devices into the co-managed state correctly on several of our machines. We did extensive testing on this several months ago ...
JoelTR
Feb 01, 2021Copper Contributor
Responding to a possibly deleted comment received by email, here is a bit more information that may help:
The Co-Management handler logs are as follows:
Two of the errors that stick out to me are:
- Merged value for setting 'CoManagementSettings_AutoEnroll' is 'False' CoManagementHandler 28/01/2021 10:05:26 AM 10380 (0x288C)
- New merged workloadflags value with co-management max capabilities '255' is '1' CoManagementHandler 28/01/2021 10:05:26 AM 10380 (0x288C)
This issue seems to point to the SCCM collection being unable to set new values for Auto-Enrol & Capabilities. Note that I am no expert in SCCM and I am just presenting what i see in the logs.
Non-Compliant Devices (Active)
Unknown Devices (Inactive)
Note that all devices were active before the auto-enrol process was started and 1 of the inactive devices was successfully co-managed before having SCCM removed.
Please feel free to reach out if any other logs or information would help investigate this issue.
fulscher89
Mar 15, 2023Copper Contributor
Was this ever resolved? We just started seeing an almost identical issue, but it mainly impacts our cloud pcs.