Académique Documents
Professionnel Documents
Culture Documents
Autodiscover is the tool that Exchange client use for getting about the
Exchange infrastructure.
Autodiscover is the method in which Exchange CAS server provides
information to his Exchange clients.
Autodiscover is the information itself.
In the following article, I would like to zoom in on the aspect of the Exchange CAS
server as the source for information and the Autodiscover process that enables the
Exchange client to retrieve the required information.
If we want to use a metaphor for describing the role of the Exchange CAS server
as an information provider, we can relate to the Exchange CAS server as a door to
the information.
In the following diagram, we can get a general concept about the type of
information that provided by the Exchange server.
The exchange provides many types of services to his client, most of this
Exchange service consider as web services.
Exchange clients access the Exchange web service, by using a URL address
that includes the FQDN of the host (Exchange CAS server) that provides the
specific web service.
The information about the available Exchange web services is passed to the
Exchange client as part of the Autodiscover process.
Each time that the Exchange client needs to use a specific Exchange web
service, the client will use the information (the Autodiscover infrastructure)
that was sent by the Exchange CAS server.
The Exchange CAS server is the information provider and, at the same time,
the elements that provide different web services.
3. Other
Under the other section, we can add additional types of details and information
that provided to the Exchange clients.
Technically, there is no limitation or restriction to the amount of data, that can be
included in the information package, that is provided by the Exchange server.
The Autodiscover information that is provided by the Exchange CAS server can
include a new and updated type of information that was not provided by former
versions of Exchange servers.
The catch is that as long that the client knows how to read and relate to the data
that is included in the Autodiscover response its O.K.
In the current article, and in the next articles of this series, we will use different
terms for describing this client and server relationships:
The client side
We can relate to the client as: client, as a Mail client or, as an Exchange client.
When we relate to the specific process of Autodiscover, we will relate to the
Exchange client as Autodiscover client.
The server side
As mentioned, the Exchange architecture includes five types of server roles, but
99% of the time when we mention the term: server or Exchange server the
meaning is the Exchange server who holds the CAS (Client Access server) role.
When we relate to the Autodiscover process, the terms that will be used for
describing the server-side side element that provides the Autodiscover services
could be:
Autodiscover Endpoint
Destination server
Destination host
Potential Autodiscover Endpoint
Final Autodiscover Endpoint.
The reason for using the term Potential is because, when the Autodiscover client
addresses the destination host, he doesnt know if this is the right host that can
help him to complete the authentication process, provide the Autodiscover
information and so on.
In other words -the Autodiscover client hope that the Autodiscover Endpoint that
he tries to connect is the correct or the last hope in the Autodiscover process
round trip.
The request or the query that he Exchange client sends, described as Autodiscover
request.
The answer of the server who includes the requested information described as
Autodiscover response.
In my mind, the Exchange CAS server is some kind of superman that came to save
the world in his hour of distress.
The Autodiscover response that provided by the Exchange CAS server (the
Autodiscover Endpoint), is dynamically generated and sent to the Exchange client
(the Autodiscover client).
The Autodiscover response thats sent to the Autodiscover client includes two main
parts:
1.Configuration settings\instructions for Outlook + Outlook Anywhere mail profile
The task of creating a new Outlook mail profile can be considered as a complicated
task because the Outlook mail profile such as Outlook Anywhere mail profile,
includes many different parameters that relate to the protocol type, the
authentication protocol, the method to the server identification and the name of
the required Exchange CAS server.
In case that the Exchange infrastructure is based on Exchange 2013, the task of
getting the name of the Exchange CAS server become even more complicated
because in an Exchange 2013 environment, the mail client doesnt use the
Exchange CAS server name but instead, use a session ID that is sent by the
Exchange CAS server.
The reason for the dynamic nature of the data is because Exchange infrastructure
and especially Office 365 and Exchange Online infrastructure could consider as very
dynamic.
The meaning of dynamic is that in each mint or hour, there could be changes in
the Exchange infrastructure such as Exchange CAS server\s that are not available
for any more verses new Exchange CAS server\s.
Other examples could be changes or updates of Exchange CAS server\s that
provide a specific web service.
After we have to review the basic components of Autodiscover, lets recap some of
the concepts of Autodiscover infrastructure.
The Autodiscover infrastructure is built from two parts: the client side and the
server side.
The Autodiscover service in the client side enables to the Exchange client to
perform tasks such as:
Accept requests from Autodiscover client, provide them the public server
certificate, get the user credentials.
Generate the autodiscover.xml file and provide the file to the Autodiscover
client.
client and, based on the specific Outlook version, generate a custom Autodiscover
responded.
For example, Exchange server will create a different answer (XML response) for
Outlook client version 2007 versus Outlook client version 2013.