This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 63%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Hello,
Preparing device for mobile management (0x800705b4)
Please let me know how to start troubleshooting of the issue?
What are the step by step instructions to be checked from MDMDiagReport.cab? Kindly help
What is the provisioning method? Is it affecting all devices or a handful? Is there a pattern? Have you checked the logs yet?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 96%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EX%3C/text%3E%3C/svg%3E)
@Boopathi Subramaniam To avoid any misunderstanding, please tell us if this device is a virtual machine. I have seen this error occurred in virtual machines.
To get more information about this error, please refer to the following article to collect logs.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 35%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZM%3C/text%3E%3C/svg%3E)
@Boopathi Subramaniam,Thanks for posting in Q&A.
To clarify this issue, please tell us what kind of Deployment mode you use and how many devices were being affected.
Based on my research, the error message normally due to a TPM error, and here is some information you can refer to fix the issue.
1.Upgrade TPM Chip. Ensure that the TPM chip in the device is version 2.0 or higher.
2.Check Assigned Groups. check whether the same device is assigned to multiple groups with different Autopilot profiles.
3.Clear TPM. Nuke the entries for the device everywhere, wipe clean, and then clear the TPM in BIOS, try to re-enroll.
4.Event Viewer Logs. Please try Michael Niehaus's script to see the information about what went on during our Autopilot provisioning process. check the event in the process to see if there's any finding.
https://oofhours.com/2020/07/12/windows-autopilot-diagnostics-digging-deeper/
5.If you are using Virtual machine, please be sure that you configure your virtual machine with a minimum of 2 processors and 4 GB of memory.
If there is any unclear, feel free to let me know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@Boopathi Subramaniam,Hope things going well.
May I know the above information is helpful? If there is any update, feel free to contact us.
@Boopathi Subramaniam,Hope you are doing well.
If the answer is helpful, please click "Accept Answer" and kindly upvote it to help others with the same problem as soon as possible.
@Boopathi Subramaniam,Hope you have a good day.
I am writing as a courtesy to follow up on this ticket. May I know the status from your side please? Please feel free to let me know if you have any concerns.