Hi,

I agree with Michael, please check whether you created a A record for autodiscover service and pointed to the 2013CAS server.

In Exchange 2013 server, please run the following command to check your autodiscover service settings:

Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri

We can set the autodiscover by running the below command:

Set-ClientAccessServer -Identity CAS2013 -AutodiscoverServiceInternalUri https://autodiscover.domain.com/autodiscover/autodiscover.xml

Best Regards,

David 

Hi,

I agree with Michael, please check whether you created a A record for autodiscover service and pointed to the 2013CAS server.

In Exchange 2013 server, please run the following command to check your autodiscover service settings:

Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri

We can set the autodiscover by running the below command:

Set-ClientAccessServer -Identity CAS2013 -AutodiscoverServiceInternalUri https://autodiscover.domain.com/autodiscover/autodiscover.xml

Best Regards,

David 

Hey All,

I have just deployed a couple of CAS/MB combo Exchange 2013 servers in a new site, co existing with Exchange 2010 SP3, and after I moved my mailbox to the 2013 server, autodiscover stopped working internally. TestRemoteConnectivity works fine, and it works for all the people still on Exchange 2010, but for my mailbox which I moved to the 2013 server, I get 401 unauthorized. In my testing, if I go to the https://autodiscover.domain.com/autodiscover/autodiscover.xml, I cannot login. But, if I go straight to the cas/MB server, it works https://exmb1.domain.com/autodiscover/autodiscover.xml. I have checked permissions on the IIS folders and all looks fine. 

Any ideas?

Thanks

Hello

tip: check iis log for 401 and share log please.
if have proxy check exceptions
and check autodiscover internal url  and dns point to cas server

Hey All,

I have just deployed a couple of CAS/MB combo Exchange 2013 servers in a new site, co existing with Exchange 2010 SP3, and after I moved my mailbox to the 2013 server, autodiscover stopped working internally. TestRemoteConnectivity works fine, and it works for all the people still on Exchange 2010, but for my mailbox which I moved to the 2013 server, I get 401 unauthorized. In my testing, if I go to the https://autodiscover.domain.com/autodiscover/autodiscover.xml, I cannot login. But, if I go straight to the cas/MB server, it works https://exmb1.domain.com/autodiscover/autodiscover.xml. I have checked permissions on the IIS folders and all looks fine. 

Any ideas?

Thanks

It should like you haven't pointed the autodiscover A record to Exchange 2013 CAS servers. Try pointing the record to one of your 2013 and see if it work. Also, have you changed the autodiscover VD to the https://autodiscover.domain.com/autodiscover/autodiscover.xml ?

Hey All,

I have just deployed a couple of CAS/MB combo Exchange 2013 servers in a new site, co existing with Exchange 2010 SP3, and after I moved my mailbox to the 2013 server, autodiscover stopped working internally. TestRemoteConnectivity works fine, and it works for all the people still on Exchange 2010, but for my mailbox which I moved to the 2013 server, I get 401 unauthorized. In my testing, if I go to the https://autodiscover.domain.com/autodiscover/autodiscover.xml, I cannot login. But, if I go straight to the cas/MB server, it works https://exmb1.domain.com/autodiscover/autodiscover.xml. I have checked permissions on the IIS folders and all looks fine. 

Any ideas?

Thanks

It should like you haven't pointed the autodiscover A record to Exchange 2013 CAS servers. Try pointing the record to one of your 2013 and see if it work. Also, have you changed the autodiscover VD to the https://autodiscover.domain.com/autodiscover/autodiscover.xml ?

Thanks to all for the replies. After some further investigation, it seems that it was the NTLM authentication that was causing the issue. I had to go into IIS on each CAS server and change the provider order so that NTLM was above Negotiate in the list. Then the issue went away.

Thanks again

• Marked as answer by RichB PSGS 9 hours 17 minutes ago