PENDING This device is enrolled to an unexpected vendor, it will be set in co-existence mode.

[Marek Belan]

Hi all we have problem on 1/5 of PC they not enroll to MDM so SCCM cast they to co-existence mode. In this mode no deployment install.
from logs :
This device is enrolled to an unexpected vendor, it will be set in co-existence mode. CoManagementHandler 31.03.2020 7:31:26 7192 (0x1C18)
Current workloads should be set to co-existence CoManagementHandler 31.03.2020 7:31:26 7192 (0x1C18)
Workload settings is different with CCM registry. Current value is 4294967295, expected value is 3 CoManagementHandler 31.03.2020 7:31:26 7192 (0x1C18)
Current workload settings is not compliant. Setting enabled = 1, workload = 3. CoManagementHandler 31.03.2020 7:31:26 7192 (0x1C18)

PC is in Azure-HybridAD and we have set comanagement to SCCM


But problem is there is no task in task scheduler to enroll to MDM.

 

[Prajwal Desai]

At this point I don't know why this happens. I will try my best to find the answers for you.

 

[kingskawn]

Did you manage to find a solution to this? We are still seeing some devices (2%) on 4500 which have this issue
Errors in event viewer (DeviceManagment-Enterprise-Diagnostics-Provider):
Auto MDM Enroll: Device Credential (0x0), Failed (Unknown Win32 Error code: 0x80192ee2)

In CoManagementHandler.log:
This device is enrolled to an unexpected vendor, it will be set in co-existence mode.
Workload settings is different with CCM registry. Current value is 4294967295, expected value is 1

Result is that those devices aren't receiving updates or data sources in general