This message was deleted.
# microsoft-365
s
This message was deleted.
r
From the Citrix section In the MS link. In addition, you must deploy the following registry key on the VDA for the new Teams client to be optimized: Location:  HKLM\SOFTWARE\WOW6432Node\Citrix\WebSocketService Key (REG_Multi_SZ): ProcessWhitelist Value: msedgewebview2.exe  If this registry key is missing, the new Teams client functions in nonoptimized mode (server-side rendering).
m
yeah, that one is in there
classic teams is working fine from the same endpoint even in the same session
just new teams refuses to spawn webrtc on the endpoint
r
Okay, not certain yet. Something I haven’t got to test yet.
Notice how the MS doc says 2212 VDA and CWA 2302 for CU then says any LTSR. I would assume they mean for the CR it needs to be those versions as a minimum for CR and up.
But then again it references the Citrix link in the MS article . So I assume it follows the current legacy teams deployment guide by citrix. But I was reading this blog, and seen the install parameters are different. Even though it horizon (not saying this is the same) Just reading it reading to see if anything was related for extra knowledge. https://www.stephenwagner.com/2023/10/07/deploy-install-new-teams-vdi/amp/
m
yeah, I read that too
we’re onVDA 2308
and CWA 2309
and it all works fine with classic teams
r
Hmmm 🤔
m
I cannot figure this one out
like all the services look they are runing
the only thing that doesn’t happen is that reg key, but it’s not there for classic teams either and that works, so I think that’s a legacy thing
MsTeamsRedirSupport
s
Do you have both installed on the same machine? Can only one hook into redirect service which name is escaping me
v
I ended up uninstalling Classic Teams to get it to work. I have to do more testing to see if that was the key to get it to function as expected. Win 11 VDA 2203 CU3
m
I uninstalled classic teams but still couldn’t get it to work
v
I burned myself initially by having a typo in the registry.
m
I wonder if that’s what I’ve done, maybe some unicode thing
s
mine is optimized, have set only the key above:
m
hmmmmm
r
Ran into the same issue 2203CU2 VDA 2309 CWA… reverted to classic for now..
m
I can’t figure out how to get new teams off there, the -x option fails with the bootstrapper
r
Ok I just re read the article and found my error, I created a REG_SZ and is REG_Multi_SZ. It works now.. 😅
m
oh lol, I’ve done the same thing
😅 1
r
Ouch
m
trying again now
r
Glad you found it
m
still didn’t fix it for me 😞
oh wait, I blew away my profile and now it’s working
💥 2
thanks @RickE
👍 1
r
I need to test it soon. I have so many things I want to analyze with it to see what still applies from the current teams doc that Citrix has.
I tested it this morning, very light but it works too. Going to do a deep dive this weekend
s
What happens when you have users that it doesnt work for and you cant blow away their profile?
r
The new location is here. You can blow this away if needed. Not sure if that is what you meant? C:\Users\username\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe