Windows 10: Intune - Enrollment status page Black Screen when applying Account Setup during Autopilot

Have been getting a black screen with no cursor or anything after the Autopilot ESP gets to the last stage and starts the Account Setup. I have to hard reboot the machine hold down the power button and then it brings me to a login page. Once I log in it brings me back to the ESP and continues without a hitch.

:)

 

Enrolling Android Device in Intune - Google Account?

After doing my own research it appears this depends on what kind of Android device you want to enroll. Starting with:

• Set up Android Enterprise work profile enrollments
• Set up Android Enterprise dedicated device enrollments
• Set up Android Enterprise fully managed enrollments

In my case, I wanted to enroll a fully-managed device:

Enroll Android Enterprise dedicated, fully managed, or corporate-owned work profile devices in Intune - Microsoft Intune

According to the above documentation:

*Admins or users are to: (5) On the Google sign-in screen, enter afw#setup instead of a Gmail account, and then choose
NEXT.*

The next step is to scan or input the Android enrollment token - Intune blade (Azure portal) > Device enrollment - Android enrollment > Android enrollment (under Manage) > Corporate-owned, fully managed user devices (Preview)

 

Autopilot Profiles: Azure /Intune.

In the Microsoft Partner Center Dashboard I am able to both create and configure Autopilot profiles and (once it’s working) register devices to apply those Autopilot profiles to.



In the Azure Intune Dashboard I am able to do the exact same functions as mentioned above in the Microsoft Partner Center by navigating:

• Open Azure
• Open InTune
• Click Device Enrollment
• Click Windows Enrollment
• In this GUI there are options for Windows Autopilot

The odd thing is that for the same customer I can configure Autopilot in two different places. Additionally, if I create a profile in one location, it does not propagate to the other. I can have two completely different profiles in each place.



How is it determined which is the profile that will be used for Autopilot if I have one in each place? Is one being phased out? Thanks for any information that you can provide.

Also, what would happen if we had a device from a completely different source than Ingram? Like we inherited a client that already had PC’s, and we wanted to onboard them with the Azure/InTune stack? Would we not be able to register
those devices? I don’t think Ingram would interested in taking requests for devices that they didn’t even sell.

Thank you.

 

Autopilot failing at Enrollment Status page- error 0x81036502

We have been using Autopilot deployments for a few months without issue. Lately, however, Autopilot setups have been failing while on Ethernet during the enrollment status page under Device Setup - Apps. Generating error code 0x81036502

If I hit "Continue Anyway" the laptop will load to desktop and everything appears to work fine, but I would like to find out what is causing the ESP to error out, as it is preventing pre-provisioning from working as well.

The Enrollment profile I am using has "Block device until all apps and profiles are installed" set to No. Also I have checked the apps that do install and I do not see any failures. I've collected the logs and used Event Viewer but I can't see anything specific. I can post them here if need be to assist with troubleshooting. Also see attached screenshots.

Any help would be much appreciated. I want to get this resolved as I am trying to work with a vendor to help us use Intune to deploy devices for a zero-touch setup solution.