SOLVED

How has your organization managed the 4.0 GHz processor requirement vs Zooms 2 GHz requirement?

%3CLINGO-SUB%20id%3D%22lingo-sub-1645966%22%20slang%3D%22en-US%22%3EHow%20has%20your%20organization%20managed%20the%204.0%20GHz%20processor%20requirement%20vs%20Zooms%202%20GHz%20requirement%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1645966%22%20slang%3D%22en-US%22%3E%3CP%3EWorking%20remotely%2C%20due%20to%20COVID-19%20thrust%20our%20organizational%20users%20to%20quickly%20adopt%20Microsoft%20Teams.%20Our%20larger%20meetings%2C%20video%2C%20or%20voice%20quality%20is%20compromised%20while%20using%20Teams%20on%20a%20VDI.%20A%20part%20of%20our%20organization%20had%20used%20Zoom%20on%20their%20VDI%20and%20experienced%20no%20issues.%20My%20theory%20is%20the%20processor%20requirement%20is%20the%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Have%20you%20experienced%20the%20issue%3F%3C%2FP%3E%3CP%3E2.%20Do%20you%20have%20a%20solution%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1645966%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1646153%22%20slang%3D%22en-US%22%3ERe%3A%20How%20has%20your%20organization%20managed%20the%204.0%20GHz%20processor%20requirement%20vs%20Zooms%202%20GHz%20requirement%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1646153%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F786302%22%20target%3D%22_blank%22%3E%40marthaowen%3C%2FA%3E%26nbsp%3Bwhat%204Ghz%20CPU%20requirement%3F%20I%20don't%20see%20anything%20mentioned%20other%20than%202%20vCPU%20cores%20in%20the%20documentation%20at%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20important%20factor%20for%20Teams%20performance%20is%20to%20have%20the%20right%20versions%20of%20Citrix%2C%20VMWare%20etc.%20configured%20to%20allow%20the%20client%20to%20offload%20the%20audio%2Fvideo%20to%20the%20VDI%20client.%20The%20server%20is%20taken%20out%20of%20the%20processing%20for%20the%20latency%20sensitive%20media%20workload%2C%20and%20you'll%20get%20basically%20the%20browser%20experience%20for%20a%20meeting%20superimposed%20on%20the%20virtual%20desktop%2C%20as%20described%20in%20the%20diagram%20in%20the%20above%20document.%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorSteven%20Collier_0%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1664231%22%20slang%3D%22en-US%22%3ERe%3A%20How%20has%20your%20organization%20managed%20the%204.0%20GHz%20processor%20requirement%20vs%20Zooms%202%20GHz%20requirement%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1664231%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F178440%22%20target%3D%22_blank%22%3E%40Steven%20Collier%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20was%20not%20about%20a%20GHz%20requirement%20but%20a%20number%20of%20cores%20recommendation.%20The%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%3C%2FA%3E%20document%20or%20others%20that%20I%20had%20previously%20found%20USED%20to%20says%20the%20recommended%20number%20of%20cores%20for%20Teams%20was%204.%20It's%20been%20awhile%20since%20I%20looked%20at%20it%20so%20I%20assumed%20it's%20changed%20but%20I'm%20positive%20that%20it%20used%20to%20say%204%20was%20the%20recommended%20number%20in%20a%20virtual%20environment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1665876%22%20slang%3D%22en-US%22%3ERe%3A%20How%20has%20your%20organization%20managed%20the%204.0%20GHz%20processor%20requirement%20vs%20Zooms%202%20GHz%20requirement%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1665876%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F786303%22%20target%3D%22_blank%22%3E%40Mike_Pudans%3C%2FA%3E%26nbsp%3Byou%20can%20see%20the%20history%20of%20the%20edits%20to%20that%20page%2C%20if%20was%20created%20in%20March%202019%20and%20said%202%20vCPU%20at%20the%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Working remotely, due to COVID-19 thrust our organizational users to quickly adopt Microsoft Teams. Our larger meetings, video, or voice quality is compromised while using Teams on a VDI. A part of our organization had used Zoom on their VDI and experienced no issues. My theory is the processor requirement is the issue. 

1. Have you experienced the issue?

2. Do you have a solution? 

5 Replies
Highlighted

@marthaowen what 4Ghz CPU requirement? I don't see anything mentioned other than 2 vCPU cores in the documentation at

 

https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi

 

The important factor for Teams performance is to have the right versions of Citrix, VMWare etc. configured to allow the client to offload the audio/video to the VDI client. The server is taken out of the processing for the latency sensitive media workload, and you'll get basically the browser experience for a meeting superimposed on the virtual desktop, as described in the diagram in the above document.

 

 

 

Highlighted

@Steven Collier 

 

This was not about a GHz requirement but a number of cores recommendation. The https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi document or others that I had previously found USED to says the recommended number of cores for Teams was 4. It's been awhile since I looked at it so I assumed it's changed but I'm positive that it used to say 4 was the recommended number in a virtual environment.

Highlighted
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

@Mike_Pudans you can see the history of the edits to that page, if was created in March 2019 and said 2 vCPU at the time.

Highlighted

@Steven CollierI have found where the 4 core recommendation was coming from that I had seen and it was not in this document, it was in a VMware document for running Teams on a Horizon desktop. My apologizes for confusing the two.

 

In this document https://docs.vmware.com/en/VMware-Horizon-7/7.12/horizon-remote-desktop-features/GUID-E64B3E85-BA1E-... it says:

 

"Microsoft Teams with Real-Time Audio-Video requires a minimum 4 vCPU, 4 GB RAM configuration, with a maximum video resolution of 640 x 480 pixels. Additional vCPUs and memory configurations deliver a superior experience."

 

That is what I remember seeing when I made that comment about 3 cores vs 4 cores.

Highlighted

@Mike_Pudans That article is where VMWare are talking about using Teams using what they call 'Real-Time Audio/Video' which is basically just connecting your webcam to the virtual desktop, all the work is happening on the server.

 

They also have a page that describes "Media Optimisation" on Horizon with Teams. This is where your the audio/video is offloaded from the virtual desktop to your client, resulting in far more reliable call quality, and less server load. There they recommend 2vCpu ...

 

https://docs.vmware.com/en/VMware-Horizon/2006/horizon-remote-desktop-features/GUID-F68FA7BB-B08F-4E...