If the Windows 10 devices just needs to be enrolled and ready for
extradition, Windows AutoPilot self-deploying mode is here. Self-deploying mode is designed to deploy Windows 10 as a kiosk, digital signage device, or a shared device. This is what we can call real zero touch provisioning, without any user interaction.
Notice, limitations and know Erros:
If connected via Ethernet, no network prompt is expected. If no Ethernet connection is available and Wi-fi is built in, the user needs to connect to a wireless network.
The following options are automatically enabled for Autopilot devices in self-deploying mode:
And remember that the device can only be Azure AD joined (Active Directory join is not supported)
For more information on Windows AutoPilot Self-deploying mode -> https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/self-deploying
Give the profile a Name, Description (optional) and click Next:
Note: In this scenario I created a Group called Kiosk Devices and added a dynamic device membership rule that is calling a specific device Model value I use for my Kiosk devices.
Note: Now we are finish with the self-deploying mode configuration. Remember to also create some Device configuration policies for the Windows 10 for example Kiosk mode or Share-devices.
Note: This picture is how it should look like when the devices is turned on. I cannot test the output ATM (Sorry) because I am waiting for my TPM 2.0 test device to arrive. When I get it I will provide the output here. To be continued.