Learn How to Set Time Zone for WVD VMs with Endpoint Manager | Intune. There are PowerShell scripts and Group Policies to change the time zone of Windows Virtual Desktop virtual machines. I think it’s better to give us an time zone option in the WVD VM provisioning template.
I have a post where you get all the list of time zone details that Windows support. Learn how to change the time zone of Windows 10 devices manually. Also, learn how to enable daylight saving settings while changing the Windows 10 time zone. More details Latest Updated List of Windows 10 Time Zone | Codes | TZUTIL.
If you are worried about Intune policies and how to take a trial subscription of Endpoint Manager Intune etc…Learn more about Intune from HTMD free Intune training (63+ episodes).
Create Intune Time Zone Policy for WVD using Settings Catalog
Let’s check how to create Intune Time Zone Policy for WVD VMs. I hope you already have access to create Intune policy.
- Login to Endpoint Manager Intune portal https://endpoint.microsoft.com/#home
- Navigate to Devices -> Windows -> Configuration profiles.
- Click on +Create Profile.
- Select Windows 10 and later as the platform from the drop-down menu.
- Select Settings Catalog from Profile type drop-down menu.
- Start from scratch and select settings you want from the library of available settings
- Click on Create button.
- Enter the Name of the policy – Time Zone for WVD.
- Enter the Description – Set the correct Time zone for WVD VM.
- Click on the Next button.
- Click on +Add Settings.
- Settings picker – Use commas “,” among search terms to lookup settings by their keywords.
- Search “Time Zone” from Settings picker.
- Click the Search button.
- Click on Time Language Setting.
- Select check mark – Configure Time Zone.
NOTE! – This is a bit weird that you need to click on cross mark to remove the right-side blade. This could be a bug and go-away once Setting Catalog feature is generally available.
- You need to find out the correct time zone to be applied to WVD devices. This is standard Windows name for the target time zone.
NOTE! – I have a post where you get all the list of time zone details that Windows support. More details Latest Updated List of Windows 10 Time Zone | Codes | TZUTIL.
- I have set the Time Zone “GMT Standard Time” for UK WVD VMs.
- Click on NEXT button.
Assignment Options
- Click on +Add groups and select the Azure AD device Group to deploy the Intune policy for settings time zone.
- Click on Next, and Next (scope page).
- Click on Review + Create to complete the creation and assignment process of Intune Time Zone Policy for WVD.
Event Logs
You can check the Windows 10 MDM event logs to confirm whether this time zone policy to devices or not.
Event Logs :- Microsoft->Windows->DeviceManagement-> Enterprise-Diagnostics-Provider/Admin
Event ID 814 – MDM PolicyManager: Set policy string, Policy: (ConfigureTimeZone), Area: (TimeLanguageSettings), EnrollmentID requesting merge: (3BDA08ED-5D5D-4444-9A8F-586A2E80DAE3), Current User: (Device), String: (GMT Standard Time), Enrollment Type: (0x6), Scope: (0x0).
Troubleshooting Options
The following posts might help you troubleshoot issues related to the Intune Settings catalog (and, in general, Intune troubleshooting).
- How to Start Troubleshooting Intune Issues
- Windows 10 MDM Log Checklist
- MDM Diagnostics Tool – Tips & Tricks
- Learn How to Collect Windows 10 Diagnostics Information from Intune Portal | Endpoint Manager
Results
You can check the results from the Endpoint portal (a.k.a Intune portal). You can open up the Windows 10 configuration profile (setting catalog) policy and check the deployment status of the same.
- You can see that on one WVD VM the policy got successfully deployed.
Frustratingly I’ve done exactly this… and it’s not working. I’ve ensured it’s a device group that’s targeted… yet in Intune on the VM it’s just saying that it’s “Not applicable”, with no errors that I can find in the Enterprise-Diagnostics-Provider log. :-/
That is really strange … Does this mean the device is not getting any policies or only this one?
Very limited amount of policies it seems, mostly just the certificate policies, mostly everything else is “Not applicable”.
Looking at this:
https://docs.microsoft.com/en-us/mem/intune/fundamentals/azure-virtual-desktop-multi-session#to-configure-policies
If you configure is as they say (to only show policies that apply to Enterprise multi-session devices) indeed the Configure Time Zone policy doesn’t seem to be there / supported.
In fact if you scroll that help page up a bit to “Create the device configuration profile” it seems to suggest that “existing device configuration profile templates aren’t supported for Windows 10 Enterprise multi-session VMs, with the exception of (certificates and VPN)”. Weird.
Only just starting out with AVD, but not finding it as fun as I hoped! 🙂
Ah, you are working with multi-session VMs… if so that is entirely a different ball game. The supported scenario for multi-session devices and Intune is only to deploy device-based policies. I have not done a lot of R&D with multi-session WVD/AVD devices yet. it’s a bit weird.
I think Timezone CSP is applied to the device as per CSP doc https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-timelanguagesettings. It’s worth raising a support case to file a bug free of cost 🙂
Argh thanks! That makes sense. I figured everyone uses multi-session as it seemed an obvious thing to do (I guess I was thinking old style RDS farm servers), but you’re right, a bit weird is a good way to put it. 🙂
I tried via CSP as well, but it also didn’t work, so will raise a bug as you suggest (and then abandon multi-session I suspect!).