Hello,

I migrated Exchange 2010 to Exchange 2013 server. Outlook 2007 and 2010 clients are not connecting with Exchange 2013 server and showing disconnected. I ran the outlook test connectivity and found issue that autodiscover error https://autodiscover.domain.com/autodiscover/autodiscover.xml failed (0x800C8204). After finding this, ran Get-autodiscover CMDlet on powershell to view the internal and external URL which was blank no record shown.

My question is that autodiscover URL is necessary set an internal/external or it should be blank. kindly guide.

Thanks  

Hi Lucky-Hamu,

"setting the InternalURL and ExternalURL on the Autodiscover Virtual Directory is not required, and has no effect on your configuration."

please see http://blogs.technet.com/b/rmilne/archive/2013/04/02/busting-the-set-autodiscovervirtualdirectory-myth.aspx

Did you try to get the URL via a web browser? What was shown in the Browser?If it did not respond with a 600.. error I suggest to recreate the folder http://blogs.technet.com/b/get-exchangehelp/archive/2013/02/07/managing-exchange-2013-iis-virtual-directories-amp-web-applications.aspx

Regards,
Martin

Hi Martin,

Thanks for your reply, I didn't check the URL in web browser. I will try and share the result with you.

Hi ,

There is no need to have the autodiscover internal and external url for the autodiscover virtual directories .

Step 1 : But we need to make sure the below mentioned autodiscover internaluri is configured in all of your cas servers.

get-ClientAccessServer -Identity "CAS server name" | fl *InternalUri*

If it not configured , please do the below in all of your cas servers.

Set-ClientAccessServer -Identity "CAS server name" -AutoDiscoverServiceInternalUri "https://autodiscover.domain.com/autodiscover/autodiscover.xml"

Step 2 :We need to have the name "autodiscover.domain.com" on the SAN certificate installed on the exchange servers.

Step 3: Then we need to create the HOST A record for the name autodiscover.domain.com and it should point to the ip address of the load balancer .In case if you don't have the LB then you should have to directly point the HOST A record to the ip address of the exchange 2013 cas server.

Step 4 :

Then you need to add the internal outlook anywhere and autodiscover url names on the internet explorer proxy exceptions so that if the client queries those namespaces it will not the hit the proxy server instead it will hit the exchange server directly.

Step 5: Then you can check the autodisocver configuration by browsing the autodiscover url on the internet browser and it should give you an response with 600 error .

Step 6 : Then finally do the outlook test connectivity on the outlook client and check the results.

please reply me if you have any queries.

Hi Nithyanandham,

Thanks for your detailed explanation. I have a query if I have multiple CAS servers then how should I point autodiscover IP to CAS servers. Please guide

Hi ,

Just consider you are having 2 exchange 2013 CAS servers .So for that you need to create the HOST A record for the autodiscover on the internal dns like below.

consider the ip address of the 2013 cas server as below.

192.168.1.30

192.168.1.40

Then you need to create the HOST A record on the internal DNS like below 

autodiscover.domain.com - 192.168.1.30 

autodiscover.domain.com - 192.168.1.40

we would say the above method as windows DNS round robin method.So on such case if the client queries autodisocover service it would get resolved in to anyone of the exchange 2013 cas server's ip address and then it will connect to the cas server.

Above mentioned method only needs to be followed if you don't have load balancer.

Please reply me if you have any queries.

Hi,

The autodiscover url on the autodiscover VD only used for proxy and redirection, it does not affect how Outlook connect with autodiscover.

Outlook has its own order to access autodiscover url:

1. SCP.

2. https://autodiscover.domain.com/autodiscover/autodiscover.xml

3. localxml

4. SRV record

About your issue (0x800C8204) , can you directly access https://autodiscover.domain.com/autodiscover/autodiscover.xml via IE and get code 600? If so, this mean autodiscover works properly.

Hi,

The autodiscover url on the autodiscover VD only used for proxy and redirection, it does not affect how Outlook connect with autodiscover.

Outlook has its own order to access autodiscover url:

1. SCP.

2. https://autodiscover.domain.com/autodiscover/autodiscover.xml

3. localxml

4. SRV record

About your issue (0x800C8204) , can you directly access https://autodiscover.domain.com/autodiscover/autodiscover.xml via IE and get code 400? If so, this mean autodiscover works properly.

Hi Simon,

Thanks for your reply, have a quick question if don't have HLB can use WNLB or use DNS Round Robin ?

Hi ,

In addition to simon suggestion's , Based on my knowledge i have given some points please have a look .

Windows NLB :-

If you use Windows NLB then it can provide redundancy on server level failure and not on application level.

DNS round robin :-

In case if we use the windows round robin method for load balancing then it wouldn't provide server level and application level redundancy during the failures.At the Same time we need to manually adjust the DNS records during the server failure but on the client end dns caches will create the issues.

Note : Windows NLB  is best when we Compare with DNS round robin method.I have given the reasons above .

By the way one thing you need to note is that you cannot have the node on the windows NLB which is already been an member in DAG.Because windows NLB and failover cluster will not function on the same node .

Hi,

DNS round robin does NOT mean that you are required to adjust some DNS entry if case of failover. That method is used to have a load balancer forthe HTTPS access layer, like OWA, Outlook, ActiveSync.

see also https://technet.microsoft.com/en-us/library/jj898588%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396 , please understand that it is a recoomended Load Balancer Layer for HTTP-based protocols. I know several bigger installation that used DNS RR for Outlook, OWA without issues.

see also http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part1.html

DNS round robin is OK for client types mentioned above, while it is not applicable to have redundancy for IMAP, SMTP or POP3 - this clients do not evaluate service (!) availability in order to connect to a specific server resolved by DNS. In that case, compared with NLB, it is a great improvement. 

Hi,

Thanks both Nithyanandham and Martin for your valuable feedback. What I understand is DNS is better option in compare to WNLB but for SMTP, POP3 and IMAP need HLB. Please correct me if I am wrong.  

Thanks

Hi,

When will I configure Autodiscover on Exchange 2013 CAS server the users still connected on Exchange 2010 wouldn't be get any impact on Exchange 2010. Please guide.

Hi Lucky-Hamu,

please know that it is expected that your URLs are configured to use the Exchange 2013 CAS.

See also http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx

For those Exchange servers / mailbox clients who are sharing the same namespace as your Ex 2013 (Ex2010, Ex2013) you must use autodiscover, EWS, OAB, ... URL that points to Ex 2013 CAS.

Regards,
Martin

Hi Nithyanandham,

I browsed the autodiscover in IE it prompted user name and password and after give the 600 error. After while I created the internal URL of autodiscover in my both CAS servers and also pointed DNS to CAS servers. One more thing I did that configure Exchnge 2010 internal URL to autodiscover with same as Exchnage 2013 autodiscover. Again ran the test on Outlook 2007 on Win 7 client but still showing disconnected.

I am confusing that on Outlook test run the autodiscover first point to Exchange 2010 SCP and then redirect to Exchange 2013 CAS autodiscover server. As I mentioned I migrated some users from Exchange 2010 to Exchange 2013 and both are still running in coexistence. Please guide what further should I do to resolve this issue.

Kindly someone suggest what should further I do resolve this issue.

Thanks

Hi ,

Really sorry for delay.

1.Please make the all the cas servers autodiscover internal uri are set as below.Which includes exchange 2010 CAS and exchange 2013 CAS.

https://autodiscover.domain.com/autodiscover/autodiscover.xml

Command to use : 

Set-ClientAccessServer -Identity "CAS server name" -AutoDiscoverServiceInternalUri 

2.Then tell me what would be the result for the below mentioned command.

start--->run---->cmd----->nslookup autodiscover.domain.com

Please run the above mentioned command in anyone of the domain controller and also on the client machines .Then share me the output in the below format.

Client machines : 

Enter the output 

Domain controller : 

Enter the output

Hi Nithyanandham,

Thanks for your response. I already set the autodiscover for both Exchange 2010 and 2013 as per your advice on last reply. I will run these commands and let you know the result.

Hi ,

Please make sure wherever i.e (DC,client PC and exchange server) we resolve autodiscover.domain.com it should get resolved in to exchange 2013 cas servers.

Hi,

I execute the cmd as per your instruction and received the following output.

Client machines : nslookup autodiscover.domain.local

Server: Unknown
IP Address: 192.168.0.10
DNS request time out
timeout was 2 second

Domain controller : nslookup autodiscover.domain.local

DNS request time out
Server: Unknown
IP Address: ::

Server: autodiscover.domain.local
IP Address: 192.168.0.40 (Exchange 2013 CAS 2)
IP Address: 192.168.0.20 (Exchange 2010 CAS/Mialbox)
IP Address: 192.168.0.30 (Exchange 2013 CAS 1)

Please advice client is not connecting to server.

Hi Lucky-Hamu,

instead of domain.local use your mail domain recipient username@maildomain.com needs to be able to resolve host autodiscover.maildomain.com

Regards,
Martin

Hi ,

Sorry for delay .

I hope you would be having the below mentioned url set for exchange 2010 and exchange 2013 cas servers.If so then the name "autodiscover.domain.com" needs to be resolved to exchange 2013 cas servers in all the client machines .

https://autodiscover.domain.com/autodiscover/autodiscover.xml

Note : In windows DNS just create a new forward lookup zone called domain.com .Then on that zone you need to create the Host A record for the name autodiscover.domain.com which should point to exchange 2013 CAS servers.

Please reply me if you have any queries.

Most importantly you need to check the dns settings on the client machines and the domain controllers are configured properly for doing the name resolution.

Hi Martin,

The setup I created is my lab environment and I configured domain.local right now and didn't add the domain.com. I faced that issue on production environment and want to first test in lab then will start migration in production.

Hi Nithyanandham,

I will try and inform you the result of name resolution.  

Hi,

Thanks for kind support that autodiscovery is working fine. I tested from outlook and it connects to Exchange CAS server but the outlook still showing disconnected and the Exchange proxy security certificate with Error Code 8 prompts that outlook could not connect to Exchange server.

Kindly suggest what other hurdle is behind to finally connect outlook with Exchange server.

Please guide.

Thanks 

Hi ,

Please share me the entire error message snap .So that it would be easy for us to troubleshoot further.

This the error snap shot similar to my error while connecting outlook to Exchange 2013

Hi ,

What is the internal outlook anywhere name set on the exchange servers ?

I thought it was set to "ca1.exchange2013demo.com" because of that you are facing the certificate related error.

Note : The name which is used on the internal outlook anywhere needs to be available on the SAN certificate installed on the exchange 2013 cas servers, then only you can make the outlook connections without any certificate related errors.

Hi Nithyanandham,

Sorry for replying you late as I was busy on other works and did get time to check and verify the configuration settings. The Certificate issue has been resolved after entering the name in SAN certificate. I am facing some other issues like on Windows XP with Office 2007 SP3 with hotfix that required for connecting to Exchange 2013 but always prompt user name and password. I tried other to remove user profile and created new one and receiving the error message "the connection to microsoft exchange is unavailable. outlook must be online to complete this action" and prompt user name and password, when entered the credentials again another popup error message "the name cannot be resolved. the connection to microsoft exchange is unavailable. outlook must be online to complete this action"

kindly guide how can I resolve this issue.

Hi,

Can some reply me on this to figure out the issue. OWA is working perfectly but the issue only with Outlook it always prompt username and password. I tried alot but could not get success. Please suggest

Hi ,

I am really sorry for my delay, i am on off for past 3 days :)

Please go through the below mentioned article which will help you to make the outlook connectivity in windows xp to your exchange 2013 server .

http://clintboessen.blogspot.in/2014/10/windows-xp-clients-must-match.html

Note : I thought Microsoft has already ended the support for windows xp and this is for your information.

Hi Nithyanandham,

Thanks for your reply and yes I have already verified the things but unable to get access the outlook and it prompts username and password.

Can you arrange remote session so I show you exactly what is going on

Hi ,

Apart from the exchange server settings , Please install the SAN certificate in anyone of the windows xp clients and configure the outlook profile.

Really sorry , i am not sure whether the supporting persons in Microsoft forums are recommended to take the remote sessions.

In case if you face any issues please share me the error.

Hi Nithyanandham,

Thanks for your valuable feedback. I have resolved the issue on Win 7 computer, the solution was I added the same domain name in internal and external access on all virtual directories in Exchange 2013. The windows XP machines but still prompting username and password and I updated XP machine with all patches and hotfixes. Kindly suggest how XP machines will also connect to Exchange 2013.

Thanks 

Hi Luck-Hamu,

Outlook clients installed in any operating system will connect to exchange server 2013 through outlook anywhere over port no 443.

1.Please tell me did you have installed the SAN certificates on windows xp machines.

2.During password prompt if we provide the user name and password will get accepted or not ?

3.After providing the user name and password if you face any error please share me that too ?

4.Please disable the internet proxy settings on the internet explorer and then the configure the outlook profile on windows xp client machines.

Hi Nithyanandham, 

Please tell me did you have installed the SAN certificates on windows xp machines.

• Yes installed SAN on XP machines

During password prompt if we provide the user name and password will get accepted or not ?

• Not accept the password

After providing the user name and password if you face any error please share me that too ?

• No error comes up only user name and password prompt window

Please disable the internet proxy settings on the internet explorer and then the configure the outlook profile on windows xp client machines.

• Disabled the proxy settings but no luck

Kindly suggest what should further do.

• Edited by Lucky-Hamu 1 hour 19 minutes ago