Teams Timezone issue RDS/Citrix

%3CLINGO-SUB%20id%3D%22lingo-sub-1569301%22%20slang%3D%22en-US%22%3ETeams%20Timezone%20issue%20RDS%2FCitrix%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1569301%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3EHas%20anyone%20heard%20anything%20about%20a%20resolution%20to%20the%20Teams%20client%20Time%20Zone%20issue%20in%20RDS%20or%20Citrix%20environments%3F%26nbsp%3B%20Essentially%2C%20the%20client%20always%20reverts%20to%26nbsp%3B%20to%20system%20time%2C%20not%20the%20user's%20time.%20Issue%20has%20existed%20for%20months%20and%20no%20updates%20that%20I%20have%20seen.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EYou%20can%20read%20more%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F908686-bug-reports%2Fsuggestions%2F40321291-time-zone-not-redirecting-in-citrix-rds-environmen%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1569301%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1571798%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Timezone%20issue%20RDS%2FCitrix%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1571798%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299705%22%20target%3D%22_blank%22%3E%40jab9417%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BDid%20you%20vote%20on%20the%20Uservoice%20item%3F%26nbsp%3B%20When%20you%20do%2C%20you'll%20receive%20updates%20as%20their%20offered.%26nbsp%3B%20With%20only%2059%20votes%20on%20this%2C%20however%2C%20it's%20unlikely%20to%20get%20prioritized%20any%20time%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1571890%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Timezone%20issue%20RDS%2FCitrix%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1571890%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668458%22%20target%3D%22_blank%22%3E%40ThereseSolimeno%3C%2FA%3E%26nbsp%3BYep%2C%20that's%20why%20I%20linked%20the%20Uservoice%20article.%26nbsp%3B%20I've%20also%20have%20submitted%20a%20bug%20report%20through%20the%20desktop%20app%20feedback%20and%20through%20the%20%22%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%23known-issues-and-limitations%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETeams%20for%20Virtualized%20Desktop%20Infrastructure%3C%2FA%3E%22%20%26nbsp%3BDocs%20page.%3CBR%20%2F%3E%3CBR%20%2F%3EConsidering%20this%20issue%20is%20present%20not%20only%20in%20Citrix%2C%20but%20in%20RDS%20and%20Window%20Virtual%20Desktop%20environments%20as%20well%20you%20think%20this%20would%20be%20a%20bit%20more%20pressing%20of%20an%20issue.%26nbsp%3B%20%26nbsp%3BThis%20bugs%20makes%20Teams%20useless%20in%20VDI%20scenarios%20--which%20are%20increasingly%20common%20as%20more%20and%20more%20people%20are%20working%20from%20home.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1572250%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Timezone%20issue%20RDS%2FCitrix%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1572250%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668458%22%20target%3D%22_blank%22%3E%40ThereseSolimeno%3C%2FA%3E%26nbsp%3B%3CSPAN%3EYep%2C%20that's%20why%20I%20linked%20the%20Uservoice%20article.%26nbsp%3B%20I've%20also%20have%20submitted%20a%20bug%20report%20through%20the%20desktop%20app%20feedback%20and%20through%20the%20%22%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%23known-issues-and-limitations%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETeams%20for%20Virtualized%20Desktop%20Infrastructure%3C%2FA%3E%3CSPAN%3E%22%20%26nbsp%3BDocs%20page.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EConsidering%20this%20issue%20is%20present%20not%20only%20in%20Citrix%2C%20but%20in%20RDS%20and%20Window%20Virtual%20Desktop%20environments%20as%20well%20you%20think%20this%20would%20be%20a%20bit%20more%20pressing%20of%20an%20issue.%26nbsp%3B%20%26nbsp%3BThis%20bugs%20makes%20Teams%20useless%20in%20VDI%20scenarios%20--which%20are%20increasingly%20common%20as%20more%20and%20more%20people%20are%20working%20from%20home.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Has anyone heard anything about a resolution to the Teams client Time Zone issue in RDS or Citrix environments?  Essentially, the client always reverts to  to system time, not the user's time. Issue has existed for months and no updates that I have seen.

 

You can read more here

2 Replies
Highlighted

Hello @jab9417   Did you vote on the Uservoice item?  When you do, you'll receive updates as their offered.  With only 59 votes on this, however, it's unlikely to get prioritized any time soon.

Highlighted

@ThereseSolimeno Yep, that's why I linked the Uservoice article.  I've also have submitted a bug report through the desktop app feedback and through the "Teams for Virtualized Desktop Infrastructure"  Docs page.

Considering this issue is present not only in Citrix, but in RDS and Window Virtual Desktop environments as well you think this would be a bit more pressing of an issue.   This bugs makes Teams useless in VDI scenarios --which are increasingly common as more and more people are working from home.