Set Timezone for Windows 10 from Intune MDMFollowing the "Autopilot" idea I'd like to install MSI application from Intune MDM however
Following the "Autopilot" idea I'd like to install MSI application from Intune MDM via Azure AD joined laptop/surface however by default the Windows Auto timezone service is turned off so new users wont have applications installed from Intune MDM because the date/time on a new device does not match the MDM "as soon as possible" date/time requirements for deployment of Applications i.e. The OOTB Autopilot experience cant work for application deployment unless a new user sets the timezone correctly first!
How can I fix this
Tom Plant commented
If you only need one timezone, the timezone CSP could work. Make sure to use tzutil /L to get the correct timezone string though, because the Microsoft docs don't list all of them.
Andreas Mahler commented
We would like to see a automated time zone configuration based on the Azure Location Services
Kind of sad that this isn't a setting. Only way to fix it is running posh script and that again sadly only targets users.
Should be part of the AutoPilot Profile like Gaetan stated.
Also they should add posh scripts into Enrollment Status Page like they did with Win32 apps.
Gaétan St-Denis commented
The option should be added to the Windows Autopilot deployment profiles to activate the selection of the time zone by the End-User during OOBE
Has this been addressed? I just booted 2 PC's with Enterprise 1809 LTSB and they loaded up 28 hours ahead of real time (CST) here.
I tried this with this powerhsell script:
Set-TimeZone -Name 'Central Standard Time'
But next day it go back to the original time zone, the wrong one.
Is there a way we can do this with Powershell?