This message was deleted.

Microsoft rebranded the one you have been using as classic, regardless of whether you opt in on the new client or not. We are holding off with new one until fslogix and other HDX features work as expected.

Have been trialling the new Teams, but several testers found that it was randomly failing to refresh properly and display new threads (but showed comments on the thread as a new thread?), despite them showing up fine in Teams "classic". Trial has been halted until it's stabilised a bit.

Has Citrix/Microsoft given any info when the hdx optimization will be ready in the new? I'm thinking no

Thanks a lot guys, great feedbacks! 🙏

The VDI piece of this is still Public Tech Preview so should not be used in prod of any sorts. There will be things they are fixing (such as new Teams incompatibility with FSLogix) which I'm sure will be there before GA.. or at least I would hope

Great stuff, it was my understanding about the VDI piece. What really troubled me was the Classsic rebranding, started to get this Outlook presence issue happening. I was wondering, was something pushed or was it a bad update that broke stuff. So Teams was rebranded Classic, still annoying to get this done behind us ... and that's it! I'll wait for the HDX and to get it stable. I am often late to adopt new tech, I like it to be mature :) One point that prob a lot of us would be interested, how big will the Teams "profile" will be? I am not using a profile container, only UPM to roam Teams (very specific files, small storage footprint) happy users and the storage team still like me, I'd like to keep it that way!

HDX optimization works in new teams, it also works with FSLogix if using full profiles.

Hdx optimization works now with the new teams is only with a preview desktop agent and/or workspace client?

it works with the latest versions of CWA and New Teams

Nice! Will the 2203 ltsr vda agent work?

MS might be calling it a preview but anyone can get it

Thanks! Is the optimization status in the same place as the classic client? (About - version)

That's for the help!

don’t forget to set that reg key as multi_sz, I set it as SZ and optimization wouldn’t work

Thanks for the tip!

this article is good too: https://www.stephenwagner.com/2023/10/07/deploy-install-new-teams-vdi/

@Mike Streetz (O_P) yes, it is PUBLIC Tech preview, not private anymore which it was in the prior lifecycle stage, so yes, everybody can get and test.

I switched back because they removed the "Contacts" option, I have it filled up with tons of contacts and the chats with them. Once they implement that again I will give it another try

i was able to get it to optimize but the video functionality needs to bake a bit yet it looks like. If i initiate a call from my optimized setup i never see my video nor the other persons video. but the recipient can see both just fine . also if i initiate a call from the optimized side to a non optimized side the recipient seems to get a "unable to complete call" or something like that but if i do it in reverse it works.

The FSLogix issue is that it doesnt persist the data so it always does a cold start and causes download of data each time. Hopefully the FSLogix team will have it resolved soon. Citrix Profile Containers are not affected.

hmm, I cant get "HDX optimized" to work. Running lates Teams 2.0 Client on a Server 2022 RDSH, VDA 2203 CU3, CWA 23.3 Regkey (multi_SZ) is set. Any idea?

I think they said RDSH is not supported for new teams optimization