If you are in the process of migrating from Skype for Business to Microsoft Teams for the first time, in that case, always is a best practice to execute the network assessment tool to identify any possible bottleneck in your internal network.
Sometimes, even when you have excellent network switches, the problem can be wireless clients’ access points.
When there is a branch office in the company, because they don’t have the same infrastructure as in the headquarter, this kind of tool will help you identify possible network problems before implementing Microsoft Teams.
Suppose you are already using Microsoft Teams, and you have bad quality in either voice or video. In that case, this tool is a good resource to identify what device or configuration is causing these failures.
When I say failures in your network, maybe it is just the quality of service configuration or adjustments that will allow using the same network. Still, with some improvements for the voice or video, in the same way, you will find some delays in your network or jitters, but again, if you don’t have this kind of tools, it will be hard to be 100% sure about what is going on in your internal network.
For all the messaging administrators that were using the same tool but for the Sky for business, this new version is exclusively for Microsoft Teams.
You can get that tool from this link Download Microsoft Teams Network Assessment Tool from Official Microsoft Download Center, download and install it on a computer.
Where you can see the results?
Open the file NetworkAssessmentTool.exe.config and you will find these configuration, you can modify if needed.
<!-- Audio: 50000-50019 Video: 50020-50039 VBSS: 50040-50059 --> <add key="MinimumSourcePort" value="50000"/> <add key="MaximumSourcePort" value="50019"/> <!-- Duration of media flow for the quality checker, in seconds --> <!-- Note that Ctrl+C can be pressed at any time to stop the quality check --> <add key="MediaDuration" value="300"/> <!-- File name of where detailed service connectivity check results are stored --> <!-- Directory: %appdata%\..\Local\Microsoft Teams Network Assessment Tool --> <add key="OutputFileName" value="service_connectivity_check_results.txt"/> <!-- File name of where quality check results are stored --> <!-- Directory: %appdata%\..\Local\Microsoft Teams Network Assessment Tool --> <add key="ResultsFileName" value="quality_check_results.csv"/>
Thanks for reading, I hope it helps.