This message was deleted.

My personal take = serve the masses. I don't think most people actually care that FSLogix is inbuilt into Windows 10/11 Multi - we have forever and a day, regardless of where we deploy workloads and on what OS, been used to pulling an install, and getting it deployed - so I think that would be your best path, and won't upset anyone 🙂

Yup, that is always the struggle of having a product that sits squarely between cloud and on-premises. You'd be surprised the flack we got when the images were not updated after stating they would be due to a pipeline error. Thanks for the honest feedback and I know we'll never make everyone happy.

You can't win them all that's for sure, surprises me that people would find a way to complain that the starting block isn't up to date in a pipeline when they could simple just add to the same pipeline and be in a guaranteed state - but hey, there is logic, and then there is logic, and then there is other logic 🤷‍♂️ Be interesting to see what others feel, this is just my personal opinion here. Appreciate you asking the question though, I'm sure everyone else will as well

Side question, will it prevent install on Win2019? Because I guarantee some will see a new version and blindly download and try to install on Win2019 regardless of support status and what you put in the release notes 🙄

We take full control of what’s in the image - having the FSLogix agent in the image or not makes no difference

I don’t think it matters whether you GA it now and then wait for the Azure images to be updated later. What really matters is the stability of the new version, that has been the bigger issue in recent times.

I can confirm what Nathan says. I'm back to 2201 because we have massive problems with server 2022 and the current GA of FSlogix. Hopefully with the next GA version the stability will be better again

• @Daniel Marsh - yes it will install, but Teams 2 will not work consistently. • @Nathan Sperry / @Christian Jöns - what kind of "stability" issues are you seeing with Server 2022? As you can imagine, replicating every VDI scenario is impossible. I do have an idea to try and stand up a program like the TAP program for Microsoft modern apps, but that will take some time. I do have a list of customers who've agreed to be part of an early adopter program where I share early versions of FSLogix so we can see better how this handles in the wild. We don't aim to make a shotty product and I'd love to get be able to get this community and all our customers to the point where they don't have to be worried.

Ill give my 2 cents here. We are on 2201 HF2 for all customers, stable and beautiful. (Server 2016, 2019, Win 11) I have no desire to upgrade, however, we HAVE to support Teams 2.x with the aggressive rollout and end date of classic teams around the corner. We just upgraded to the PREVIEW build internally to start to vet this version. So far its been ok, but I haven't put it on anything except Win11 VDI Citrix MCS. I would feel better about it NOT having "preview" in the name so I could start rolling to customers asap, for what thats worth. Also, I will agree with the others, that we take full responsibility with whatever is inside the OS. there is no need for Microsoft to be concerned with pre-installing anything in regards to FSLogix. That actually seems worse IMO, because we might prefer a different version, etc. Hope that helps!

@Josh Farlow I know many in this community run older versions due to "stability" issues. Can you elaborate a bit so I can better understand the hesitation to move to the latest? Feel free to DM me.

@Jason Parker I had massive Problems with the current version and server 2022. We are using Citrix PVS. Container Mode was configured as Direct Access. We had between 20-30 users per day with approx. 1000 active sessions who repeatedly had problems logging off. Either the container simply got stuck on the server or the complete logoff process resulted in the server no longer responding at all. The only thing that helped was to restart the server. Shrinking, Roam RecycleBin and AppX were also deactivated. When downgrading to 2201 HF2, the problems mentioned above no longer occurred.

yeah our main issues revolve around users stuck logging off, or vhdx’s stuck on the xenapp server. Also having issues mounting on login, hence creating a temp profile

In fairness my reluctance to upgrade started way back with all the search index issues. Since then we’ve had issues like mentioned above. The point is once confidence is lost it’s very difficult to get it back. Which is why I go back to my original point stability is key rather than when newer versions are rolled out in conjunction with Azure images. Though thinking about this again, I’d be happy to have it removed all together as I can control which version is installed and when.

Thank you all for your honest feedback. Getting your trust back into our product releases are a top priority for me. I'd be happy to dive deeper for any of your scenarios to better understand the struggles and issues. This thread may not be the place, but you do have my attention. Thanks again!

@Jason Parker MS is giving us a very aggressive timeline to replace Classic Teams on Citrix Windows Server 2019. I see and understand that you are working hard on support for 2019. A few days ago rumors started popping up on reddit, that MS will ditch New Teams support on 2019 via FSLogix completely. But if I understand you correctly, 2022 is soon ready, where 2019 is on its way, but takes longer. Can you confirm us, that MS intends to support new Teams on 2019 through FSLogix without any (hidden) drawbacks? Because supporting dozens of customers with 2019 still in main support, telling them to switch to 2022 a lot sooner than anticipated is impossible.

@Marco Hofmann Not sure where these "rumors" come from but they are neither accurate nor true rumors. Some simple facts: • Classic Teams retirement for VDI is June 30th, 2024 (and, yes it is an aggressive timeline - not my team 🥹) • FSLogix 2210 hotfix 3 GA release is eminent with the following caveats: ◦ No Teams or classic Teams; works on Windows 10 & 11, Server 2012 R2, 2016, 2019, 2022 ◦ New Teams; works on Windows 10 & 11, Server 2022 ◦ Support for new Teams on Server 2019 is already "*in progress*", no ETA on ship date (we shifted work away from feature work to do this, aka: cut features) • Depending on the fix for Server 2019 and new Teams - we may release a 2210 hotfix 4 or it will go into our next feature release (v3).

Here is the rumors I was referring to: https://www.reddit.com/r/Citrix/s/KpmRKTFn3s

I've seen that post and nothing in there suggests as you say, "MS will ditch New Teams support on 2019 via FSLogix completely" I did reply to the one post about the new Teams app crash though.