How do I set the correct clock for VDI for an individual user?

Question

Hello,

I have a user whose VDI clock keeps setting back to CST when we change to EST. The server and VDI pool is set to the correct clock but this user is not able to retain the correct time zone. Any help would be appreciated.

Thanks.

Answer 1

@Smita Medhi Thanks for posting your query on Microsoft Q&A.

I have suggested few solutions but it would help if you could share exactly what service it is related to, Azure virtual desktop, Azure VM, or VMware. Let me know.

Check the time zone settings on the user’s VDI, on the user’s local machine (If the user is connecting to the VDI from a local machine) as well as on the server hosting the VDI: Ensure that the user’s VDI is set to the correct time zone. You can do this by right-clicking on the clock in the taskbar and selecting “Adjust date/time”. Then, click on “Change time zone” and select the correct time zone

Ensure that the Group Policy settings for time zone are configured correctly. You can do this by opening the Group Policy Management Console and navigating to Computer Configuration > Administrative Templates > System > Locale Services. Then, double-click on “Turn off auto-update of time zone” and select “Disabled”

Answer 2

Hi Smita,

I had a similar issue few months ago, here's my recommendations:

Check the User’s Azure Virtual Desktop Session Host Settings:

• Connect to the session host that the user is accessing.
• Verify and set the correct time zone on the Azure Virtual Desktop session host. You can do this by navigating to the Control Panel, selecting "Clock and Region," then "Date and Time," and finally adjusting the time zone.

1. Group Policy for Time Zone:
   • Ensure the Group Policy settings are not overriding the time zone settings. This can be done by opening the Group Policy Management Console and navigating to Computer Configuration > Administrative Templates > System > Windows Time Service > Time Providers. Make sure the policies here do not enforce an incorrect time zone.
2. Azure Virtual Desktop Client Settings:
   • Check if the Azure Virtual Desktop client settings on the user’s local machine are set to redirect the local time zone to the VDI session. This is often the default setting, which might cause issues if the local machine's time zone is different.
3. FSLogix Profile Containers (if used):
   • If FSLogix Profile Containers are used, ensure the user's profile does not contain incorrect time zone information. Sometimes, a corrupted profile can cause such issues. Resetting or recreating the user's FSLogix profile might help.
4. User Account Configuration:
   • Check the user account configuration in Azure Active Directory to ensure there are no settings that might enforce a specific time zone.

Hope this answer can help you with your issue.