Forum Discussion
Truly Remote Wiping and Setup
I think we all were (incorrectly) assuming you were using Autopilot. At least I was
.The ESP will only start through OOBE with AAD-join or during the Autopilot process (see https://docs.microsoft.com/en-us/mem/intune/enrollment/windows-enrollment-status). That probably explains why you need to sign in before anything happens. With Autopilot, the device configuration is applied before the first sign-in.
Few questions:
So when you go there, do you see the device waiting for user to sign in?
Do you have Enrollment Status Page enabled? This might be the problem, Enrollment Status Page restricts users from accessing the desktop until all their apps and settings are installed.
Moe
Thanks Moe.
So the Enrollment Status Page looks like https://www.ironstoneit.com/hs-fs/hubfs/Enrollment%20status%20page.png?width=900&name=Enrollment%20status%20page.png and yes, it's set up to allow the user to bypass it and go to the desktop.
My frustration is the loss of remote access during the process. If I do a format and clean install, the computer will start at the https://gtrusted.com/uploads/81439/large-81439-37.jpg, then proceed to the Enrollment Status Page after the user first signs in. So remote access is lost until someone either sits down at the machine and installs my remote agent, or sits down at the machine and logs in to get the Intune deployments going. Either way, someone needs to sit down at the machine.
If I initiate a device wipe from Intune, the computer will start with a default https://mcdn.wallpapersafari.com/medium/40/68/Ny5TMh.png, and again, proceed to the desktop after the user first signs in. And again, my remote access is lost until someone sits down at the machine to re-install my remote access agent, or sits down at the machine to log in and get the Intune deployments started. Again, someone has to sit down at the machine either way, which is the step I'm trying to eliminate.
Surely there is a way around this. ?