We have been very busy working to improve the testing options that are available from the MCA client. We are excited to microsoft connectivity analyzer tool windows 10 the 1.

This tool is a companion to the Microsoft Remote Connectivity Analyzer web site. The MCA tool provides administrators and end users with the ability to run connectivity diagnostics for five common connectivity symptoms directly from their local computer. Users can test their own connectivity, and save results in an HTML format that administrators microsoft connectivity analyzer tool windows 10 recognize from viewing results on the RCA website. Install the MCA 1. We are microsoft connectivity analyzer tool windows 10 on combining MCA with MLCA in the near future but wanted to make both these great tools available to customers now to improve our client diagnostics options.

Please let us know what you think of the tool and whether this will be helpful in troubleshooting connectivity scenarios. Also feel free to provide feedback on additional tests you microsovt like to see added in the future. We are excited to announce the 2. The tool provides administrators and end users with the ability to run connectivity diagnostics for our servers to connectivoty common issues with Exchange, Lync connectivitj Office We have added new Office Domain Name Server tests, enhanced existing tests, and improved the overall site experience.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in. Products 68 Special Topics 42 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Microsoft FastTrack. Microsoft Viva. Core Infrastructure and Security.

Education Microsoft connectivity analyzer tool windows 10. Microsoft PnP. AI and Machine Learning. Microsoft Mechanics. Healthcare and Life Sciences.

Small and Medium Business. Internet of Things IoT. Azure Partner Community. Microsoft Tech Connectiviry. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise.

Browse All Community Hubs. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Show only Search instead for. Did you mean:. Sign In. The Exchange Team. Published Mar 11 AM There is an option to run the SSO test provided on the parameters page. Microsoft Remote Connectivity Analyzer 2. Tags: troubleshooting. Resize Editor. Version history. Last update:. Updated by:.

Education Microsoft in education Office for students Office for schools Deals for students and parents Microsoft Azure in education.

Remote Connectivity Analyzer Change List - Sharing your test report

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. It's an adjunct tool to the network assessment and network insights available in the Microsoft admin center under the Health Connectivity menu. It's important to sign in to your Microsoft tenant as all test reports are shared with your administrator and uploaded to the tenant while you are signed in. Network insights in the Microsoft Admin Center are based on regular in-product measurements for your Microsoft tenant, aggregated each day.

In comparison, network insights from the Microsoft network connectivity test are run locally in the tool. In-product testing is limited, and running tests local to the user collects more data resulting in deeper insights. Network insights in the Microsoft Admin Center will show that there's a networking problem at a specific office location.

The Microsoft connectivity test can help to identify the root cause of that problem and provide a targeted performance improvement action.

We recommend that these insights be used together where networking quality status can be assessed for each office location in the Microsoft Admin Center and more specifics can be found after deployment of testing based on the Microsoft connectivity test.

When you click the Run test button, we show the running test page and identify the office location. You can type in your location by city, state, and country or choose to have it detected for you. If you detect the office location, the tool requests the latitude and longitude from the web browser and limits the accuracy to meters by meters before use. It's not necessary to identify the location more accurately than the building to measure network performance.

After office location identification, we run a TCP latency test in JavaScript and we request data from the service about in-use and recommended Microsoft service front door servers. When these tests are completed, we show them on the map and in the details tab where they can be viewed before the next step. Next, we start the download of the advanced tests client application.

We rely on the user to launch the client application and they must also have. NET 6. Most of the tests require the application to be run.

It will populate results back into the web page as it runs. You'll be prompted to download the advanced client test application from the web site after the web browser tests have completed. Open and run the file when prompted. Once the client application starts, the web page will update to show this result. Test data will start to be received to the web page. The page updates each time new-data is received and you can review the data as it arrives.

When the tests are completed, the web page and the advanced tests client will both show that. If the user is signed in, the test report will be uploaded to the customer's tenant. The test report requires authentication to your Microsoft account. Your administrator selects how you can share your test report. The default settings allow for sharing of your reports with other user within your organization and the ReportID link is not available. Reports will expire by default after 90 days.

Test reports excluding any personal identification are shared with Microsoft employees. This sharing is enabled by default and can be disabled by your administrator in the Health Network Connectivity page in the Microsoft Admin Center. You can choose users to share your report with. Being able to choose is enabled by default, but it can be disabled by your administrator.

You can share your test report with anyone by providing access to a ReportID link. This link generates a URL that you can send to someone so that they can bring up the test report without signing in. This sharing is disabled by default and must be enabled by your administrator.

The results are shown in the Summary and Details tabs. The summary tab shows a map of the detected network perimeter and a comparison of the network assessment to other Microsoft customers nearby. It also allows for sharing of the test report. Here's what the summary results view looks like:. Here's an example of the details tab output. On the details tab we show a green circle check mark if the result was compared favorably. We show a red triangle exclamation point if the result exceeded a threshold indicating a network insight.

The following sections describe each of the details tab results rows and explain the thresholds used for network insights. The user location is detected from the users web browser. It can also be typed in at the user's choice. It's used to identify network distances to specific parts of the enterprise network perimeter.

Only the city from this location detection and the distance to other network points are saved in the report. We identify the network egress IP address on the server side. Location databases are used to look up the approximate location for the network egress. If the location looked up from the network egress IP address isn't accurate, this would lead to a false result. To validate if this error is occurring for a specific IP address, you can use publicly accessible network IP address location web sites to compare against your actual location.

We determine the distance from that location to the office location. This is shown as a network insight if the distance is greater than miles kilometers since that is likely to increase the TCP latency by more than 25 ms and may affect user experience. The map shows the network egress location in relation to the user office location indicating the network backhaul inside of the enterprise WAN. Implement local and direct network egress from user office locations to the Internet for optimal Microsoft network connectivity.

Improvements to local and direct egress are the best way to address this network insight. We identify whether proxy server s are configured on the local machine to pass Microsoft network traffic in the Optimize category.

We identify the distance from the user office location to the proxy servers. The distance is tested first by ICMP ping. We show a network insight if the proxy server is further than miles kilometers away from the user office location. This test detects if you're using a VPN to connect to Microsoft A split out workload avoids the VPN entirely. A tunneled workload is sent over the VPN.

A selective tunneled workload has some routes sent over the VPN and some split out. A passing result will show if all workloads are split out or selective tunneled.

Network latency between the user office location and the Exchange Online service is compared to other Microsoft customers in the same metro area. This means their users will have better performance in the Microsoft user interface. This network insight is generated on the basis that all users in a city have access to the same telecommunications infrastructure and the same proximity to Internet circuits and Microsoft's network.

This shows the DNS server configured on the client machine that ran the tests. The distance from the user office location to the DNS Recursive Resolver server location is then calculated. This is shown as a network insight if the distance is greater than miles kilometers. The location looked up from the network egress IP Address may not be accurate and this would lead to a false result from this test.

To validate if this error is occurring for a specific IP Address, you can use publicly accessible network IP Address location web sites. This network insight will specifically impact the selection of the Exchange Online service front door.

To address this insight local and direct network egress should be a pre-requisite and then DNS Recursive Resolver should be located close to that network egress. The in-use Exchange service front door is identified in the same way that Outlook does this and we measure the network TCP latency from the user location to it. The TCP latency is shown and the in-use Exchange service front door is compared to the list of best service front doors for the current location.

This is shown as a network insight if one of the best Exchange service front door s isn't in use. Not using one of the best Exchange service front door s could be caused by network backhaul before the corporate network egress in which case we recommend local and direct network egress.

It could also be caused by use of a remote DNS recursive resolver server in which case we recommend aligning the DNS recursive resolver server with the network egress. We calculate a potential improvement in TCP latency ms to the Exchange service front door. This is done by looking at the tested user office location network latency and subtracting the network latency from the current location to the closets Exchange service front door. The difference represents the potential opportunity for improvement.

It's provided for information only and there's no associated network insight. The in-use SharePoint service front door is identified in the same way that the OneDrive client does and we measure the network TCP latency from the user office location to it.

We measure the download speed for a 15 Mb file from the SharePoint service front door. The result is shown in megabytes per second to indicate what size file in megabytes can be downloaded from SharePoint or OneDrive in one second. The number should be similar to one tenth of the minimum circuit bandwidth in megabits per second. For example if you have a mbps internet connection, you may expect 10 megabytes per second 10 MBps.

This is the latency under load and It's compared to the latency when not under load. The increase in latency when under load is often attributable to consumer network device buffers being loaded or bloated. A network insight is shown for any bloat of 1, or more. If this is blocked, then Microsoft Teams may still work using TCP, but audio and video will be impaired. Shows the UDP packet loss measured in a second test audio call from the client to the Microsoft Teams service front door.

This should be lower than 1. We test for HTTP connectivity from the user office location to all of the required Microsoft network endpoints.

How to Test Microsoft Exchange Server Connectivity Remotely - Download client analyzer for macOS or Linux

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Replace HardDrivePath with the path to which the tool was extracted to, for example:. In addition to the above, there is also an option to collect the analyzer support logs using live response.

On Windows 8. All the PowerShell scripts and modules included with the analyzer microsoft connectivity analyzer tool windows 10 Microsoft-signed. If files have been modified in any way, then the analyzer is expected to exit with the following error:. If this error is shown, then the issuerInfo. This is the main HTML output file, which will contain the findings and guidance that the analyzer script run on the machine can produce.

Description: Detailed result from certificate revocation executed by calling into CertUtil. Description: Output from running dsregcmd. This provides details about the Azure AD status of the machine. Description: Details about SSL configuration applied to the machine gathered from registry. Skip to main microsoft connectivity analyzer tool windows 10.

This browser is no longer supported. Download Microsoft Edge More info. Table of contents Exit focus mode. Table of contents. Note The exact files captured may change depending on factors such as: The version of windows on which the analyzer is run. Event log channel availability on the machine. The start state of the EDR sensor Sense is stopped if machine is not yet onboarded. If an advanced troubleshooting parameter was used with the analyzer command. Submit and view feedback for This product This page.

View all page feedback. In this article.