This message was deleted.
# _general
s
This message was deleted.
👀 1
j
@JimMoyle any clues? Sorry for tagging you but you're the only person I know at MS who seems able to generate traction on anything
👍🏻 2
👍 1
b
Anyone have any insight here? This is one of the main reasons my org hasn't fully adopted VDi...
j
Yep, I'd love to see an answer of some sort....raised it with Microsoft but they don't send their best to our meetings usually
j
@Bill Pennie So you have the same issue, you are happy to spend significant extra money on VM resources to run Teams with all features enabled? This will be very costly for you and would impact the performance for video and audio if you didn't have reliable excellent low latency network connection.
And this issue is specifically a blocker for you to increase AVD uptake
d
@JimMoyle For RemotePC use cases this might be an option to give the users full featured Teams experience
👍 1
b
My organization in the the "discovery" phase of exploring the modern desktop and how that is going to pan out. VDi (including, but not exclusively, AVD) is on the table. Leadership is fully riding the AVD train and is looking for ways to justify E3 to E5. There are many factors at play here. One major hurdle is feature parity in Teams. We are currently evaluating vGPU/GRID for knowledge workers, among other "high performance" VDi options.
👍 1
j
Just in case anyone is under an incorrect impression here, this isn't my area and I'm making no promises of an answer or a fix in any way. I'm having a poke around internally.
1
j
In my case, it's for the trade floor and money is no object. These guys are the company's crown jewels and have the best of everything.
And yes, if this worked in AVD as they want it, it would definitely be on the table as a solution
j
@James Rankin I know the type 🙂
😉 1
b
Thanks @JimMoyle!
j
Just had an interesting call with Microsoft where they said they are aiming for feature parity between "full" and "VDI" Teams clients. It won't be quick, but it seems that they are aware that it is an issue for people and are aspiring to get the features brought into line.
👍 1
Apparently feature parity will be achieved by the end of the year, by moving to a native Teams engine instead of WebRTC. So we only have to put up with the "lag" in features for another six months or less. Good news, it means we don't get the horrors of running unoptimized such as bad peripheral detection, network dependency, etc.
👍 2