SOLVED

Teams Time Issues

%3CLINGO-SUB%20id%3D%22lingo-sub-1424189%22%20slang%3D%22en-US%22%3ETeams%20Time%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1424189%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20users%20in%20Azure%20hosted%20RDS%20farm%20and%20Azure%20hosted%20WVD%2C%20all%20using%20Teams.%20For%20every%20user%2C%20Teams%20is%20using%20the%20host%20server%20time%20zone%20(UTC)%20rather%20than%20the%20user's%20time%20zone.%26nbsp%3B%20This%20is%20occurring%20whether%20the%20host%20server%20has%20Teams%20installed%20per%20user%20or%20with%20machine%20wide%20install.%26nbsp%3B%20I've%20also%20tested%20with%20a%20azure%20VM%20not%20attached%20to%20RDS%20or%20WVD%20and%20have%20the%20same%20results%2C%20it%20will%20not%20use%20the%20correct%20timestamps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20open%20Teams%20in%20a%20web%20browser%20and%20all%20the%20timestamps%20are%20correct.%20I%20also%20did%20a%20test%20post%20in%20the%20browser%20and%20the%20post%20shows%20correct%20time%20in%20the%20browser%2C%20and%20incorrect%20time%20in%20the%20desktop%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20found%20lots%20of%20posts%20about%20Teams%20timestamp%20issues%2C%20but%20most%20revolve%20around%20users%20on%20a%20dedicated%20computer%20and%20not%20RDS%2FWVD.%20None%20of%20the%20suggested%20ideas%20have%20helped%20my%20situation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1424189%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1430129%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Time%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1430129%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446531%22%20target%3D%22_blank%22%3E%40Marc_WSS%3C%2FA%3E%26nbsp%3B%2C%3CBR%20%2F%3EThe%20'known%20issues'%20page%20for%20Teams%20on%20VDI%20was%20updated%20over%20the%20weekend%20to%20list%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fteams-on-wvd%23known-issues-and-limitations%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fteams-on-wvd%23known-issues-and-limitations%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CU%3E%3CSTRONG%3EKnown%20issues%20and%20limitations%3C%2FSTRONG%3E%3C%2FU%3E%3CBR%20%2F%3E%3CSTRONG%3EClient%20deployment%2C%20installation%2C%20and%20setup%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3ETeams%20currently%20only%20shows%20the%20UTC%20time%20zone%20in%20chat%2C%20channels%2C%20and%20calendar.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1430133%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Time%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1430133%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446531%22%20target%3D%22_blank%22%3E%40Marc_WSS%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EThere%20is%20another%20post%20about%20this%20issue%20(see%20link%20below)%20where%20they%20advise%20that%20there%20is%20a%20new%20client%20coming%20on%20June%2020%20that%20will%20address%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20also%20posted%20in%20there%20about%20the%20known%20issue%20page%20being%20updated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams%2Fnew-versions-of-teams-machine-wide-installer-not-respecting%2Fm-p%2F1369553%2Fhighlight%2Ffalse%23M57256%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams%2Fnew-versions-of-teams-machine-wide-installer-not-respecting%2Fm-p%2F1369553%2Fhighlight%2Ffalse%23M57256%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We have users in Azure hosted RDS farm and Azure hosted WVD, all using Teams. For every user, Teams is using the host server time zone (UTC) rather than the user's time zone.  This is occurring whether the host server has Teams installed per user or with machine wide install.  I've also tested with a azure VM not attached to RDS or WVD and have the same results, it will not use the correct timestamps.

 

I can open Teams in a web browser and all the timestamps are correct. I also did a test post in the browser and the post shows correct time in the browser, and incorrect time in the desktop client.

 

I've found lots of posts about Teams timestamp issues, but most revolve around users on a dedicated computer and not RDS/WVD. None of the suggested ideas have helped my situation.

2 Replies
Highlighted

Hi @Marc_WSS ,
The 'known issues' page for Teams on VDI was updated over the weekend to list this issue.

 

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.
Highlighted
Solution

@Marc_WSS 
There is another post about this issue (see link below) where they advise that there is a new client coming on June 20 that will address it.

 

Have also posted in there about the known issue page being updated.

 

https://techcommunity.microsoft.com/t5/microsoft-teams/new-versions-of-teams-machine-wide-installer-...