I've tried deleting this, and the autopilot device,Īnd reenrolling it with the CSV, then putting that new Azure object into groups, and it still fails. The only differences I can tell would be that because I'm testing Autopilot on the Surface Laptop, the Azure AD object exists already so it can be put into groups to get Intune policy once it connects. (though I still had to put in the address). I actually tried a full, non-connected install to bypass autopilot, no domain connect or anything and attach to MDM which failed with the same error upon manually putting in the enterpriseenrollment.X. and signingįurthermore, I tried an MDM connect on a fresh out of box Dell set up with no network and local accounts and MDM worked on that one. The test machine having issues is a Surface Laptop which I've been able to connect successfully once, but when resetting (using WinRE) to test Autopilot, the reset process failed, so I used the media creation tool to build an 1809 boot disk and get a freshĬopy of Windows on a wiped drive. I've been testing and can report some more information
It seems to throw this error after the call to our institution's SSO page, and I'll get a positive enrollment within Intune that I have to delete for the next To our AD and added it to SCCM thinking it might get certificates the other would have. For reference, it's 1809, and I have another machine with 1809 that was built through SCCM and it will add the MDM fine. I can't for the life of me figure out why this happens only on the machine that was built through Autopilot. When attempting to bind the public cert/private key, the public cert was not found either: when attempting to bind the public cert/private key, or when looking into provisioning payload (perhaps targeting the wrong store). One I want to use for Azure, It will complete autopilot, not get any policies (expected if auto-enroll doesn't work as above), but when I try to manually enroll, I get a 0x80180024 error, which resolves to
On a hybrid joined machine, I can use "Enroll only in device management", go through the steps, (I still have to manually enter the MDM URL because the auto-enroll doesn't seem to work) and have a co-managed machine. My original goal is to set up Autopilot and have new devices join as pure AzureĪD joins, not Hybrid. All of our devices are joined as Hybrid AD - part of a migration that happened beforehand with O365. I'm trying out Intune within an environment that is on prem AD + SCCM.
0 kommentar(er)
