Forum Discussion
New Versions of Teams Machine-Wide Installer Not Respecting Timezone Redirect
- 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.
The latest from the official link of: https://teams.microsoft.com/downloads/desktopurl?env=production&plat=windows&arch=x64&managedInstaller=true&download=true is 1.3.00.13565. You're saying that 1.3.00.18160 is a Machine Wide Installer version?
Replaced the version in the CDN link to download it and confirmed timezones look good now for me as well. No real version log I know of for Machine Wide Teams, so not sure why the large version jump between those two.
- Originally I was told the fix would coincide with the GA release of the Teams AV optimizations. That's still in preview at the moment and it's been taken off the WVD roadmap, so your guess on an ETA is as good as mine.
I see , i guess we have to stick with this version as this is the only one that works for us regarding the calendar Timezone issue
https://statics.teams.cdn.office.net/production-windows-x64/1.3.00.8663/Teams_windows_x64.msiThank you
- 1.3.00.2160 like I mentioned in the post should be the latest I know of before the UAT breaking changes, but I'm not sure how much you'd get out of the update from what you're using.