Forum Discussion
Kundi215
Feb 16, 2022Copper Contributor
Device Credential (0x0), Failed (A specific platform or version is not supported.)
Hello team, Tried to enroll devices with Intune as GPO enrollment. Most of the device has been enrolled but some of the devices are getting this error. Auto MDM Enroll: Device Credential (0x0), F...
Hi, just wondering but what happens when you use user credentials?
https://call4cloud.nl/2020/05/intune-auto-mdm-enrollment-for-devices-already-azure-ad-joined/
https://call4cloud.nl/2020/05/intune-auto-mdm-enrollment-for-devices-already-azure-ad-joined/
Kundi215
Feb 16, 2022Copper Contributor
Thanks Rudy, Actually GPO is enabled as "User credentials" but still getting this error.
- Feb 16, 2022
And with user credentials the error is the same I presume?
And I assume the user is in the mdm scope
And also no old enrollments like I also showed in the blog?
And does the scheduled task appears at the device? make sure you open the task scheduler with sufficient permisisons
And anything useful in dsregcmd /status
A lots of and 🙂
- Kundi215Feb 16, 2022Copper ContributorYes, with user credentials same results.
User is in MDM scope as set to "All" in Intune.
I checked in enrollments folder in registries, Their is no old registries in there,
Scheduled task is also running and throwing the same error again and again.
with the dsregcmd /status commands, device is showing domain joined, azure joined, azure prt is set to yes and also receiving the MDM url's.- Feb 16, 2022
And what happens when you use a dsregcmd /join (system context)
And the registry values which are normally configured when configuring the gpo are also configured?