Windows Autopilot moves customers away from custom imaging and driver management, instead leveraging Microsoft Intune to transform a device into one that is ready for productive use. Intune supports ...
Updated Apr 16, 2019
Version 3.0
Blog Post
This is excellent info, excited about 1903 waiting for win32 and powershell scripts to run at the ESP, that could make things really nice.
On the topic of the time zone, we're trying to find out how to automatically set this based on the location the autopilot process ran at. It's all good setting all machines to a static time zone, but when machines are globally in different time zones, trying to figure out how to set this. I tried enabling the 'Set time zone automatically' feature using a registry edit, and it does enable this but it doesn't seem to process the automatic setting of the time zone until the computer is restarted. It also blocks the user from manually setting the time zone after that registry edit is set.
Could be great if either the actual Windows 10 OOBE would specify a time zone (maybe even automatically select one based on location, show that to the user and let the user change it to what they want during OOBE). Or if there's a way to set the registry entry to enable 'set time zone automatically' followed by some powershell command that forces the finding of the time zone automatically right on the spot.
MDT was a bit easier in this regard, I just had the machine sync its time zone based on the server it used to image from. :)