This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 51%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Anyone with insight on Microsoft fixing the issue with New Teams on Server 2019 using FSLogix? "New Teams on Windows Server 2019 currently isn't compatible with FSLogix and fails to launch"
Info last updated 2/13/2024:
We have several Citrix customers on Server 2019 and with Classic Teams depreciating 6/30/2024, we need to start testing the New Teams version.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 51%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
@Cicindela31 it's just FSLogix HF4
https://learn.microsoft.com/en-us/fslogix/overview-release-notes#fslogix-2210-hotfix-4-29888427471
Imho it's still better to move to Server 2022 as I read a lot of cases where the fix still doesn't work.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Andy S
We apologize for the inconvenience. According to the documentation, this issue is currently under investigation with high priority. Depending on the fix, this may come in the next feature release or as another hotfix.
To fix this problem more quickly, you can send a feedback directly to Microsoft Feedback to add it in future updates.
Many features of our current products are designed and upgraded based on customers’ feedback. With requirements like this increase, the problem may well be released in the future.
Thanks for your understanding and support.
********************************************************************************************************* If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. *********************************************************************************************************
Hi @Andy S I am checking the status of this case. Please let us know if you would like further assistance. Meanwhile, if the reply is helpful to you, please try to mark it as an answer to help others who encounter the same issue and read this thread. Thank you for your understanding and patience!
(duplicate)
Hi @Anonymous I did submit feedback but would like to check what MIcrosoft is doing regarding this issue, is there a private work-around available so we can at least test the New Teams on Server 2019?
Hi @Andy S
We apologize for the inconvenience caused to you. According to our research, Microsoft has not yet officially launched a solution.
We will continue to pay attention to this case and will notify you as soon as there are any official updates.
@Anonymous is there an internal Microsoft ticket I can be added to?
Hi, my RDS2019 users still can not switch to Teams new. Any news for a fix?
@Anonymous the fix is already out, HF4 for FSLogix. Did you test it?
The FSLogix page says this:
Customers who are deploying or using new Teams, this version is only supported on the following operating systems:
So Server 2019 is unsupported for the new Teams. It might work but don't expect anything.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 17%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETD%3C/text%3E%3C/svg%3E)
While this is correct for the current situation, this is not for general - Microsoft has to find a solution until Teams 1.0 is eol (and they need to give customers time to adapt). They mention "This issue is currently under investigation with high prioritization" - but I highly doubt that, since the two monthes of complete silence. I wonder if anybody even works in the FSLogix department, since they only do some hotfixes here and there - which is also evidence if you look at the version: "2210"... so they only do some fixes here and there since over 18 monthes...
If they don't find any fix for this, they need to support Teams 1.0 until the eol of Windows Server 2019.
I agree for sure but I would not gamble they will fix this before the end of June. And I won't count on any Teams 1.0 extension either just because it doesn't work on 2019.
Wohoo update came out with the fix :)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 40%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
@Martijn Kools can you give me link of the update with the fix pls
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 40%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPV%3C/text%3E%3C/svg%3E)
Did the Fix work? i read a lot of problems that even Hotfix 4 does not work properly
did anyone had succes with this Fix? i have the same problems over 300 servers
Here is the Fix : https://learn.microsoft.com/en-us/fslogix/overview-release-notes
it seems MS fixed also this problemen. we can confirm everything works. Search on 2022 and new teams on 2019
Same here, everything works now. Finally:)