What does the process of optimizing New MS Teams f...
# citrix-vad
a
What does the process of optimizing New MS Teams for Citrix look like? Based on the article https://support.citrix.com/s/article/CTX691425-how-to-enable-teams-optimization-with-microsofts-new-vdi-optimization-engine-slimcore, it appears that enabling ‘public preview’ is necessary. However, I see ‘HDX optimized’ without configuring virtual channels for MS Teams. Can you help to clarify this? 🤷🏻‍♂️ 🤔
m
AFAIK there is an old and a new way. The old way still works, hence you still see ‘HDX optimized’. And the new way is in preview and not yet ready. At least that's how I understood the information.
👍 1
💯 1
j
On my setups it was only switching to SlimCore when setting to "Users can opt in" so the user has to manually enable the preview feature in Teams, restart twice and after that, slimcore gets enabled and the slimcore plugin gets installed on the windows-endpoint. "On for everyone" needs some idle time of teams in the VDI - see MS feedback here:
👍 1
That was my post / request to MS: Bug or Feature? I've tested MS Teams SlimCore optimization with Citrix. The Teams Preview settings in the Admincenter have to be set to Opt-In. As soon as the User enables Previewfeature by manual in the HDX Session's Teams (and restart Teams twice) the MSIX got installed at the Endpoint and SlimCore is active. I've used "On for everyone" and the Optimization ALWAYS did a fallback to HDX Optimized.
m
i can confirm that @Julian Jakobs answer solved my problem, too 🙂
❤️ 1
👍 1
j
For Workspace App, make sure to enable the Teams VDI plug-in during install. That is the component tie-ins for Slimcore. The WebRTC for non-slimcore still gets installed during the regular CWA install without any prompts needed.
m
The testing I’ve done with slimcore wasn’t good. Every time a session disconnects and you reconnect, optimization has left the chat. You have to sign completely out of teams and kill it a time or two to get optimization working. We’ve removed the msteamsplugin from our endpoints to ensure it continues to utilize old hdx
j
Yeah at the moment you have to restart teams twice EVERY time you logon a new HDX session... I don't know why they proceed with that thing during a preview, you can't tell testusers to restart teams every time 😄
🫣 1
r
WEM trigger here address it.