Let’s walk through the required setup for accomplishing this.
#MDT TIME ZONE WINDOWS 10#
Using these two features and services, I’ve written a PowerShell script that performs a set of tasks with the sole purpose of setting the correct time zone configuration on a Windows 10 device that’s provisioned using Windows Autopilot. The dynamic method consists of combining the following services:īy retrieving the current positioning data from the built-in location services capability of Windows 10, you’re able to call Azure Maps and essentially determine the correct time zone for the device that’s being provisioned. What we’re going to cover in this blog post, is a method that I’ve developed while working for a customer where the goal was to only utilize services available from a single trusted vendor such as Microsoft, since relying on 3rd-party public services was deemed unreliable for this particular customer.
The issue with this method though, is that it’s not really a dynamic solution that’s easy to configure for a multi-national organization that are provisioning devices around the globe with Autopilot. Device/Vendor/MSFT/Policy/Config/TimeLanguageSettings/ConfigureTimeZoneĪ fellow Microsoft MVP, Peter van der Woude, has already covered the topic of setting the time zone using this custom configuration profile, so we won’t go deeper into this method.