12-12-2019 02:40 AM
12-12-2019 02:40 AM
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:
Any suggestions on how I can configure this, is welcome!
You will be a live saver for me.
12-12-2019 03:33 AM
@Jeroen BurgerhoutHi 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?
12-12-2019 04:34 AM
12-12-2019 05:52 AM
@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."
12-12-2019 06:25 AM
@Jeroen Burgerhout Hmm.. silly question: license? Are you using the Intune device license for this deployment? https://docs.microsoft.com/en-us/intune/fundamentals/licenses#additional-information
This one is required if you are using self-deploy for kiosk mode.
12-12-2019 06:34 AM - edited 12-12-2019 06:40 AM
Intune device license is meant for the 'bulk enrollment user', not for the machine itself. You cannot apply an 'Intune Device License' to a Device. At least it was 6 months ago explained by a Microsoft support guy ;)
12-12-2019 06:51 AM
@HilbertHofsteengeHmm... I don't think so. Device license is especially for Kiosk or public devices. You cannot manage a device without an Azure AD user account with the standard EMS/Microsoft 365 subscription. They are user-based license. This means also that you can not use Autopilot... That is the reason why Microsoft has introduced device-based licenses.
A quote from Micheal Niehaus:
"If you are deploying kiosks or digital signs using Intune, there is an available Intune device-only subscription license that can be used. See the Intune licensing documentation for more around that."
12-15-2019 01:44 AM
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.
01-24-2020 03:28 AM
@Jeroen Burgerhout 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