08-27-2019 07:43 AM
08-28-2019 06:35 AM
Hi @RPollina, I just came across this issue, too.
Users experience this only within the Teams Client on Windows, it is not occurring if the users join a Teams online meeting by using the browser.
Did you try to join a meeting via browser?
I opened the task manager during an online meeting however the utilization of CPU/network/RAM/... was very low, so I guess it's not a client hardware topic. Altough I cannot exclude this for 100 % right now. Maybe wrong or "outdated" system device drivers could cause this issue... e.g. wrong NIC drivers, wrong audio ... drivers...
I've checked network connectivity towards Microsoft SFBO/Teams by using the SFBO network assessment tool https://www.microsoft.com/en-us/download/details.aspx?id=53885
Results were ok.
I also checked the firewall/proxy (SSL / packet interception ... were off).
As a next step I'll test to temporarily turn off the thirdparty antivirus scanner on a Windows PC to exclude the AV scanner as issue source.
09-01-2019 10:57 PM
Hi @RPollina , I'm not yet sure. I'm still investigating this issue.
I'll also try to set up a new clean Windows machine, not domain joined, update it with the latest updates for Windows as well as Office. Than I'll check if the issue remains if the user joins a meeting via this (test) Windows client.
As far as I figure out something new I'll also answer to this thread but I'm not sure when this will be.
09-07-2019 02:55 AM
Hi @RPollina, still on it, we're investigating towards firewall because the issue does not occure if I test this on a "unmanged" internet connection, i.e. if the user/s are located remote at home without VPN/DA... And the network monitoring/reporting did not show such bad network metrics towards O365...
12-01-2019 09:27 AM
Hi @HaydenMoulds, sorry, I don't have any further details on what the FW admins did to fix it. I only provided the Office 365 URLs and IPs list which need to be accessible by Microsoft Teams clients. I'd guess that they had not set up these URLs/IPs correctly or had some packet inspection or interception configured. Best Regards Erik