This message was deleted.

looks good to me. CldFlt = 1 and Teams comes up.

Great news!

Great. Email sent!

Does this new HF address issues where new teams auto start doesnt work in Server 2022/Citrix VDI?

@John Rankine My understanding is that any teams/fslogix issue with 2022 is due to virus vendors and not teams/fslogix.

Any update on a release date for HF4?

No date - we discovered 2 issues today that we need to resolve before HF4 goes out. As much as people want it to GA, I have over 30 customers testing it in a private build and only 55% have responded with results. My bar is 80-85% response with successful validation. I am sure you'd agree that we don't GA unless we have positive test results 🫤

Understood - but we are in a tough spot though with only three months until classic Teams EOL and we can't even begin testing.

You wouldn't believe the gong show my team has had to go through just to get to this point. I hear you and we are literally shelving all other work to make this happen while maintaining a high quality bar.

Looking forward to this release. For Teams v2 in Server 2019, I've managed to iron out the Outlook presence and working towards the plugin (Classic Teams cache causes issues, ok when removed). Last piece of the puzzle is to get FS working to persist.

How is the progress on Windows Server 2019 and FSLogix for Teams 2.0 on CVAD?

I’ve been testing the latest private HF4 hotfix, it’s getting there but I’m still having some issues in our environment with AppX package registering and auto launching without using some kind of login script. It was explained to me that they had to add Teams AppX package registration through powershell on login as the API method doesn’t work in Server 2019. My current issues are that the registration process worked with an existing profile but fails with a brand new profile and when it tries to auto launch it prompts the user with an OpenWith dialogue box on launch. Waiting for a reply from Teams and FSlogix on these issues.

seems like ms should delay the teams classic sunset. that is my opinion.

One of my larger clients has asked MS to do exactly that

We originally had 36 customers testing, but only about half are providing their results despite the urgency I keep hearing about 🤣. We have 17 customers testing a private HF4 build which is working for some but not others. We have a final item on our list of issues which is in a nasty part of the kernel and we've yet to pin point the exact cause and scenarios in which it occurs. This issue is the "the parameter is incorrect". Some instance can be overcome via AV exclusions others not. Some see this issue with no AV installed. We've tested internally a private build that may help workaround it, but we have more work to do. I would suspect that Teams will extend the deadline once we have finalize the issues in VDI so I wouldn't sweat it.

@Jason Parker why dont you ask for testers on the blog post. Thats where most of the activity seems to be. Here is more limited and a smarter bunch 🙂

Because I don't have an army of people to help organize the testing and validation. It requires a significant amount of time to not only organize the testing, but capture all the results and feedback from all the testers. The preview will be on the blog post once we have validation the changes are working as intended and they are well understood.

Any updates here?

Large orgs on 2019 requiring a prod FSLogix hotfix now have almost zero chance of meeting the June deadline. Most work on 2 month release cadences for gold images so that time window is rapidly closing.

I can tell you it’s almost working in HF4, I can get it to work with a login script hack lol, still working with both products teams, waiting on on Teams group to get back to me on why it’s the AppX is not showing up for users even though it’s install under the All Users switch

Tracking this thread. We are looking to deploy new Teams in 2019 SHD/Citrix

I'm testing a new hotfix 4 from Jason that just came out on Saturday and it appears to be resolving most of our issues. I wouldn't waste your time until it comes out. (Unless you have allot of free time) Plus there also the teams outlook plug in nonsense to deal with that I'm not entirely sure that has been resolved.

Like stormlight said, we just got a new HF4 build over the weekend to test and looks very promising for Server 2019. Only issue we have now is installing into a new profile and first time launch which we’re using a login script or WEM to achieve.

Yup, can't reveal the dates, but they are getting extended.

@Jason Parker Any update on the HF4 release?

Writing the release notes as we speak, will have a blog post soon...stay tuned.

NICE!

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.

Unless you're on VDI, when the EOS date is October 1st

VDI = Hosted Shared Desktop?

That has been my experiance. They seem to treat RDSH,VDI, and hosted shared desktop all the same

Yes, MS don't differentiate. Any virtual environment where you'd offload/optimise via a remote protocol

The classic Teams for VDI will reach end of support on October 1, 2024, and end of availability on July 1, 2025. For more information,

Yes, just the End of Support date is OCtober not July

you scared me for a second.. I just wanted to know the date it won't actually launch