Beruflich Dokumente
Kultur Dokumente
The Microsoft Connectivity Analyzer (MCA) tool is the installable client or the
software client version of the ExRCA (Microsoft Remote Connectivity Analyzer
Tool) Autodiscover test.
The main purpose of using the Microsoft Connectivity Analyzer (MCA) tool versus
the Microsoft Remote Connectivity Analyzer web Tool is the ability to test the
Autodiscover process from inside the organizations network or by testing the
Autodiscover process from a specific user desktop.
Disadvantages
The Microsoft Connectivity Analyzer (MCA) client cannot monitor and inspect
the Autodiscover in an Active Directory environment (the Autodiscover based
on the LDAP query, etc.).
The Microsoft Connectivity Analyzer (MCA) doesnt include all the options that
include when using a tool such as the ExRCA.
The Microsoft Connectivity Analyzer (MCA) toll considers as a software that we
download + install versus the ExRCA tool that is a web-based tool.
Versus this option, the MCA (Microsoft Connectivity Analyzer wizard offers the user
to choose an option named I cant log on with office Outlook.
In case that the user selects this option, the MCA will perform two different tests at
the same time the Autodiscover test + the Outlook Anywhere (RCP/HTTPS) test.
General notes about the MCA interface
My opinion or wish is that the user interface should have designed differently and
provide an interface that is similar or even identical to the Remote Connectivity
Analyzer Tool.
I hope that in future, somebody will read what I have written and adapt my
recommendations (yes, I know that I live in a la la land; -))
Download and install the MCA (Microsoft Connectivity Analyzer)
software component.
Go to the -Microsoft Remote Connectivity Analyzer
(https://testconnectivity.microsoft.com/) site and, choose the Client tab and click on
the Install now option.
The tool supports the following operating systems: Windows Vista, Windows 7,
Windows Server 2008, Windows 8
Microsoft .NET Framework 4.5 is required
Using the MCA (Microsoft Connectivity Analyzer)
To demonstrate the use of the use of the MCA (Microsoft Connectivity Analyzer), we
will use the following scenario:
A user named John that uses the E-mail address John@o365info.com , what to
create a new Outlook mail profile.
John desk is a domain joined and, John is located in the private company network.
Note Dont forget that the MCA (Microsoft Connectivity Analyzer) doesnt know
how to use the Active Directory Autodiscover method and the MCA (Microsoft
Connectivity Analyzer) can only use the Autodiscover method that is implemented
in a non-Active Directory environment.
We would like to review the Autodiscover workflow that is implemented between
the Autodiscover client and the Autodiscover Endpoint.
2. A detailed report about each of the operations that was included in the test
(Part B in the screenshot)
The MCA (Microsoft Connectivity Analyzer) result is display based on the same
hierarchical concept that is used by the ExRCA tool.
The top level result can be expanded so we can see each of the steps that were
involved in a specific test and most of the time, we also have the ability to expand
each of the specific steps to get more detailed information.
In our scenario, although the host manage to resolve the hostname to IP address,
when the Autodiscover client tries to verify if the potential Autodiscover Endpoint
can communicate using HTTPS, the test fails (number 1).
Step 2: Trying to connect the potential Autodiscover Endpoint using the
Autodiscover standard host name
In the following screenshot, we can see that the Autodiscover client move on to
the next host name option in which he will try to look for the potential Autodiscover
Endpoint using the naming convention: Autodiscover + recipient SMTP domain
name.
In our scenario, the potential Autodiscover Endpoint will be
autodiscover.o365info.com
We can see that the steps of: Resolving the host name to IP and Verify the potential
Autodiscover Endpoint can communicate using HTTPS complete successfully
(number 2).
The End of the Journey the client gets the required Autodiscover.xml file
In the following screenshot, we can see that the Autodiscover client sends to the
Autodiscover Endpoint a request:
attempting to send an Autodiscover POST request to Potential Autodiscover URLs.
The Autodiscover Endpoint generates the required information and sends it to the
Autodiscover client. We can see that the content of the information includes the
data in an XML format.
The Autodiscover server response includes the URL address of the different
Exchange web services such as Availability services, OOO and so on.
We will not go into a detailed review of the Outlook Anywhere service test results,
but its important to understand that the Outlook Anywhere includes a complete set
of steps that need to be implemented.
In case that we want to view a detail report of the Outlook Anywhere results, we
need to expand the required section.
In the following screenshot, we can see all the steps that are involved in an Outlook
Anywhere communication channel.
For example, we can see that the Outlook Anywhere client is talking with the
internal name of the Exchange On-Premise server, by using the host name
exo1.o365info.lcoal (number 5).
Additional reading
Video link