Forum Discussion
Disable post OOBE screens Windows AutoPilot
Goodmorning all,
I'm building a new workplace concept with Windows AutoPilot. Everything is working fine, but I want to get rid of the post OOBE screens automatically and set the correct value for it.
The screens which I'm talking about are:
- Do more with your voice
- Let Microsoft and apps use your location
- Find my device
- Send diagnostic data to Microsoft
- Improving inking & typing
- Get tailored experiences with diagnostic data
- Let's apps using advertising ID
Any suggestions on how I can configure this, is welcome!
You will be a live saver for me.
Greetings,
Jeroen
JeroenBurgerhout In my environment I got it fixed. Support sent me a message that there was an issue solved in Windows Autopilot on 18 December 2019. But only for new autopilot profiles, not for existing profiles.
So I created new autopilot profiles and assigned them, after I didn't get any privacy questions anymore.
This issue solved the self-deploy (azuread only) and the user-driven (hybrid join) scenarion for me.cc: Albert Neef
Hello Hilbert Hofsteenge, Hi all,
I'm currently facing the same issue with the Windows 10 1909. As far as I remember it works a few month ago. Anyway... I tried to create a new Windows Autopilot profile but it doesn't change anything. after device deployment I still have the screens (Do more with your voice, etc...) displayed.
DId you change anything else to remove them?Thanks in advance for your feedback!
Can the the "Dutch Intune support group" help out here please?
JeroenBurgerhout Roel Everink Albert Neef Hilbert Hofsteenge
JeroenBurgerhoutHi Jeroen, I saw your message on LinkedIn.
How far are you with configuring Autopilot? If you have it correctly configured, you shouldn't see the (post) OOBE screens. I presume you have disabled OOBE in the Autopilot profile. ?
It looks like your device is not add into Autopilot. Did you added the device into Autopilot based on a Powershell or did the manufacturer that for you? Did you assigned the profile to the group with Autopilot enabled devices? And do you see the device as an assigned device in the Autopilot profile?Albert Neef I have this in the AutoPilot Profile. It's a self-deploying kiosk device.
JeroenBurgerhout Ah oke.. Which version Windows are you using? Self-deploying is supported in 1903 and later.. Did you also enabled Enrollment Status Page (ESP) for this?
Hi Jeroen,
Got the exact same issue with a self-deploying machine. But I also see it with a hybrid joined machine, I raised a support call for it last week.
HilbertHofsteenge Hybrid is still not supported and Self-deploying is in preview..
"Self-deploying mode does not support Active Directory Join or Hybrid Azure AD Join. All devices will be joined to Azure Active Directory."
https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/self-deploying
Albert Neef
I know Albert 😉
But I use hybrid in user-driven mode.
I'm having the exact same problem. Autopilot config is the same as yours. And it does work. Autopilot comes up during OOBE, device gets joined to Intune and AzureAD, Apps get installed.
But when it should present the logon screen, or login for a kiosk device (according to https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/self-deploying#validation)
It shows all the privacy settings that we have to configure.
It also auto signs in to the device after I make the privacy settings selection, which also shouldn't happen as it is NOT a kiosk device (its just a shared user device)
I'm also using Windows 10 1909, but I'm using the Dutch version. Are you using the English version or also Dutch?
The device based license should only be for Kiosk or digital sign machines. As you can also use self-deploying mode with shared user devices, or even personal devices if you wanted to (not sure why you would want that, but it could) it shouldn't have any impact on the autopilot experience.
I'm using the English 1909 version, but with the Dutch region and language selected during OOBE.
