06-04-2019 02:56 PM
06-04-2019 02:56 PM
Upon testing of white glove with Windows 10 1903 builds , we are seeing that second time around on the ESP page the device is sitting at "registering your device for mobile management". This is despite deleting the device from Intune and resetting the TPM chip in the BIOS.
Any ideas ?
06-05-2019 07:46 PM
Did you first use "Wipe" without retain enrollment
06-11-2019 01:40 AM - edited 06-14-2019 03:41 AM
@Darren_Bradley I didnt know we were already able to use the White Glove deployment options.
I have the same issue with a Windows 10 version, created last friday with the Media Creation tool 1903.
And will try the Wipe option as mentioned by @Consult-a null and come back in a hour orso.
<update after 1 hour>
Wipe is not working since it has no Intune device id yet when importing the device.
Tried to reimport it (deleted all stuff related to the device) synced the devices and trying again.
<update after reimport>
Machine failed again, but i am able to wipe it. So waiting for the actions to complete...
<update after wipe>
It looks like it is 1 step further and fails (but says Succes in the Red screen).
That is the Prepare the device for MDM (my own translation, got a dutch win10 here).
Clicked on retry multiple times and after the 3rd time it passed the first part and stopped during the next phase (device phase). No info at all. The Red screen again with the Succes message.
Wiping the device again to see if it makes any difference.
I removed the device from customer tenant and it is now imported in my own tenant.
Removed the Intune company portal in the ESP (guess this one is my issue right now) and waiting now.. But it seems like it never wants to install an app. Even increased the ESP wait time.
So after all kind of checks and tests, i removed all test apps in my test tennant.
Now it will pass the 2nd part, but no Seal option yet (still see a Red screen with a Succes-msg), so my guess is that MS still has to do some things.
07-08-2019 07:45 AM
@Patrick Stalman Couple things... If you are doing Hybrid AD join, the device needs to write back to AD i believe, so try doing a Start-ADSyncSyncCycle on your AADConnect box. Also, you can get logs by turning logging on in the Auto Pilot Profile, then after a failure insert a USB drive click the log button and the logs will be written to the USB drive. Just wait like 30-60 secs for the logs to fully write and take a look. This is not documented to my knowledge but someone posted the info on a thread somewhere.
07-08-2019 07:50 AM
Cheers , the devices are Azure joined only but I am aware of the write back as we are also using Windows Hello for business.
We actually seemed to have "fixed" this now but subscribing the machine to the Semi Annual update channel in intune which "blocks" any updates during the enrolment. If we select the update to be insider the device will reboot prior to reseal.
We have not tested this again with 18362.207 but we will do when I get the chance.
Useful information about the log files though.
07-09-2019 02:43 AM
I see there is some log talk here for AutoPilot.
If you have failures you can also press SHIFT + F10 and in the CMD prompt type:
Mdmdiagnosticstool.exe -area Autopilot -cab c:\Autopilot.cab
and then Xcopy it to a USB.