Forum Discussion

martin_macf's avatar
martin_macf
Copper Contributor
Apr 30, 2021

Windows Autopilot Error Code 0x800705b4 Preparing device for mobile management

We are implementing a number of Windows Autopilot via Lenovo Thinkbook 15-ITL. These are being deployed to authorised users whether they are at home connected to their home broadband or in the office...
Autopilot
Error
preparing your device
i_ARQ's avatar
i_ARQ
Copper Contributor
May 14, 2021

derekuoft I am also experiencing this. I use the SCCM (MECM) "Deploy autopilot to existing devices" template and it seems to be broken (I'm deploying a 20H2 version of the image).  Same results here. When I disable the steps related to Setup windows and config manager, prepare Config Mgr client and prepare windows for Capture it seems to be fine (because the wim never boots into the OS phase and just remains in the WINPE applying wim stage of OSD).
But if you want to keep all the steps from that template, it seems those steps create something on the image that Intune doesn't agree with and then generates the Error Code 0x800705b4 during the Preparing device for mobile management autopilot step.
Maybe the ccm client isn't removed properly, maybe it isn't sysprepped cleanly. But I've tried letting it boot into the OS and then manually running steps to remove the ccm client and then runnning sysprep /generalize /oobe (various combinations). And yet it still gets the same error in intune.

Maybe a registry key is flagging something that Intune errors out on?



derekuoft's avatar
derekuoft
Copper Contributor
May 14, 2021

i_ARQ Yes this is 100% what I'm seeing. I had a ticket open with Microsoft and they said they would reflect this to the technical team. I tried to make it as clear as possible to my support technician and summarized the problem in one sentence. "Prepare Windows and Configmgr" step in the SCCM task sequence breaks autopilot provisioning, no matter what method is used to remove the client.

 

I've had to move our autopilot for existing devices task sequence to the "faster" V2 method which doesn't install the SCCM client or sysprep the machine, and this involved basically rejigging the entire onboarding infrastructure, which we haven't touched in about two years. Having to cast my mind back and re-implement critical infrastructure from years ago was extremely annoying. I really hope Microsoft will acknowledge that this issue exists and provide some form of response. As it stands, their official docs for existing device flow for autopilot is broken.