Forum Discussion
Solved
New Versions of Teams Machine-Wide Installer Not Respecting Timezone Redirect
We've been using Teams Machine-Wide Installer on WVD for about 5 months now, and have been stuck using an old version of the installer. Because we have users in multiple parts of the world we use the Time Zone Redirection GPO, but if we update to any version of Teams above 1.3.00.2160 the app stops respecting that and all chat times are based on the VM's time instead of the incoming user's redirected time. Tried out 2160 vs the 4461 on the Teams VDI Installation link I see newer ones are checking TimeZoneKeyName to pick up the time zone code while the older one doesn't appear to. Tried it on a newer 8863 and got the same result (2160 on top and 8863 on bottom):
Changing the timezone code in TimeZoneKeyName does update the chat times for the users, but considering I can have one in Texas and one in Honduras I can't reasonably set them all to EST. I've opened a case with Microsoft, but has anyone else run into anything similar with the Machine-Wide Installer?
- Microsoft confirmed it is a known issue slated to be corrected in the June 20th release.
ScriptingJAK - The Known issues page for Teams on VDI was updated over the weekend to list this.
https://docs.microsoft.com/en-us/azure/virtual-desktop/teams-on-wvd#known-issues-and-limitations
Known issues and limitations
Client deployment, installation, and setup- Teams currently only shows the UTC time zone in chat, channels, and calendar.
Ivan Webb ScriptingJAK
Good day do you have any updates on this issue as we are still having this issue even after using the latest MSI,I've been off on leave for the last two weeks, however, since I've been back I've noticed that my Teams has been updated to v 1.3.00.18160 on my WVD session. Using this version the calendar is displaying the correct date and time for my timezone.
- Microsoft confirmed it is a known issue slated to be corrected in the June 20th release.
