"New Teams" in Windows 2019 RDSH environment with FSLogix profiles

Question

Recently Microsoft released FSLogix hotfix 4 to address critical issues with "New Teams" in RDSH environments. This was super important to those of us that are affected by the upcoming June 30th deadline to implement "New Teams".

I've noted some real issues that have yet to be resolved, and I have an open support case where I have clearly documented the issues we are facing. However, the support folks at LTIMindtree have for the past 6 weeks been 'escalating' the issue and 'waiting for a resource to be assigned' to the ticket. I keep telling them that we have a June 30th deadline, but they don't seem able to help despite the looming deadline.

I'm curious as to whether or not Microsoft has been made aware of the ongoing issues with deploying "New Teams" on Windows 2019 using FSLogix profiles?

Noting that we are battling:

Teams occasionally does not start automatically, and in that circumstance Teams can't be started by the user. The only resolution is to sign out, then sign in. This has become noticeably better with FSLogix hotfix 4, but it is not 100% yet. We are still affected by this although much less frequently than before hotfix 4 was released.
Some user preferences are not captured and stored in the user's FSLogix profile container. One specific example is the "Links open preference". If a user selects a specific browser, that setting is not captured and stored in the profile. It is therefore reverted to default during the next session login. This is just a single example to demonstrate the issue, not a complete list.

I'm wondering whether or not anyone in the Microsoft Teams group is aware of the fact that there are MSP's out there that have real, legit technical issues and are facing a Microsoft imposed deadline without any real 'fixes' or solutions.

At this point, we've been forced to communicate to our customers basically saying "Sorry, but Microsoft is forcing this upgrade and hasn't yet addressed these issues that we are aware of".

Is there anyone else in the same boat?

laura_morgan · Answer

TreyContello&nbsp;I'm checking with our engineering team on the issues you are reporting and to get latest status. Thank for you raising this here!

treycontello · Answer

Thank you Laura. It's very frustrating dealing with Support through LTI Mindtree. They don't have any answers and won't / can't escalate to get anyone from the FSLogix or Teams group involved. So I've basically been stuck for the past 6 weeks while the only thing moving is the June 30th deadline -- which is coming closer and closer.

laura_morgan · Answer

TreyContello&nbsp;and others who are looking for timelines for&nbsp;end-of-support and end-of-availability for classic Teams please review this site:&nbsp;https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability
&nbsp;
Native clients excluding VDI:
The end of support for the classic Teams client starts July 1, 2024.
The end of availability for the classic Teams client starts July 1, 2025.
&nbsp;
VDI timeline:
The end of support for the classic Teams client in VDI starts October 1, 2024.
The end of availability for the classic Teams client in VDI starts July 1, 2025.

fernando_klurfan · Answer

When Teams cannot be started by the user,
Do you see anything on the event viewer?
https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#troubleshooting-new-teams-deployment-errors

Also, can you run these and attach outputs:

> Get-AppxPackage -name MsTeams (from a PowerShell command under the user’s context, not as Admin. If output empty=Problem)
> Get-AppxPackage -name MsTeams –allusers (from an elevated PowerShell command, and compare with the previous command)

treycontello · Answer

We are gathering this info and will post is as soon as we have it.

Forum Discussion

"New Teams" in Windows 2019 RDSH environment with FSLogix profiles

8 Replies

Resources