Stuck on Windows Autopilot? Fix Error 806/808 CSV Import Issues Now!

Table of Contents

Stuck on Windows Autopilot? Squashing Those Pesky 806/808 CSV Import Errors!¶

image just illustration

So, you’re trying to set up Windows Autopilot and BAM! You’re hit with error 806 or 808 when importing your CSV file. Super frustrating, right? Don’t worry, we’ve got you covered. This guide will walk you through fixing these annoying import issues and get your Autopilot deployment back on track.

Decoding the Errors: 806 and 808¶

Let’s break down what these error codes actually mean:

• 806 - ZtdDeviceAlreadyAssigned: This basically means the device you’re trying to register is already registered in your tenant. Think of it like trying to join a club you’re already a member of.

• 808 - ZtdDeviceAssignedToOtherTenant: This one’s a bit trickier. It usually means there’s a record of the device hanging out in the Microsoft Store for Business, potentially linked to another tenant. It’s like the device has a phantom membership somewhere else.

Troubleshooting Steps: Let’s Get to Work!¶

Here’s the action plan to tackle these errors:

1. Checking the Microsoft Store for Business¶

Your first stop is the Microsoft Store for Business. This is where many device records live.

• Sign In: Head over to the Microsoft Store for Business.
• Manage Devices: Once you’re in, click on “Manage” and then “Devices.”
• Locate and Remove: Search for the troublesome device. If you find it, select it and click “Remove devices.” This is like cancelling that phantom membership.

After removing the device from the Microsoft Store for Business, try re-importing your CSV file into Intune.

2. Still Stuck? Contacting Microsoft Support¶

If the device isn’t in the Microsoft Store for Business, or you still get the error after removing it, you might need some backup from Microsoft Support. They have the tools to dig deeper and clear out any lingering records.

• Gather Your Intel: Before contacting support, collect the following information. This will help them resolve your issue quickly:

  • Device CSV: A copy of the CSV file that’s causing the error.
  • Proof of Ownership: This is crucial! You’ll need a bill of sale or invoice (PDF format) showing you own the device. Screenshots won’t cut it. The document must clearly show your company’s name and the device’s serial number, chassis ID, or another unique identifier. If it doesn’t, ask your vendor for an updated document. Microsoft Premier Support customers still need to prove possession, but not necessarily ownership.
  • Diagnostic Logs: Grab some logs from the device itself. Log onto the device and run this command in a command prompt or PowerShell: Mdmdiagnosticstool.exe -area Autopilot -cab c:\\out.cab. This creates a file called “out.cab” which contains valuable information about the device and its Autopilot status.

• Create a Service Request: Once you have all the info, follow the steps in How to get support in Microsoft Intune admin center to create a service request.

Understanding the Importance of Proof of Ownership¶

Microsoft takes device ownership seriously. This is why they need proof of ownership before removing device records. Think of it as a security measure to prevent unauthorized removal of devices. Make sure your proof of ownership document is the original (no screenshots!) and includes all the necessary details like your company name and the device’s unique identifiers.

Tips for a Smooth Autopilot Experience¶

Here are a few extra tips to keep your Autopilot deployments running smoothly:

• Double-check your CSV: Before importing, make absolutely sure your CSV file is formatted correctly and contains accurate information. Even a small typo can cause headaches.
• Keep your records organized: Maintaining a well-organized inventory of your devices and their associated information can save you a lot of time and effort when troubleshooting.
• Stay updated: Keep your Windows Autopilot and Intune environments up-to-date with the latest patches and releases. This ensures you have access to the newest features and bug fixes.

Wrapping Up¶

Hopefully, this guide has helped you navigate the sometimes tricky waters of Windows Autopilot CSV import errors. Remember, these errors are usually solvable with a little detective work and the right information. Don’t let a few bumps in the road discourage you from leveraging the power of Autopilot!

We’d love to hear from you! Share your experiences, questions, and tips in the comments below. And if you need more information on other Autopilot-related topics, let us know what you’d like to see covered!