We are in the middle of a large migration from 2010 to 2013.
To narrow down the situation ill only tell whats relevant.
###Exchange 2010:
Exchange 2010 Casarray: casarray.contoso.com
Internal and external namespaces are webmail.contoso.com
Outlook Anywhere enabled on 2010, external hostname: webmail.contoso.com, auth: internal NTLM, IIS, basic&NTLM
SCP is the FQDN of the 2010 CAS servers
Its a hybrid setup with Office 365,
External autodiscover and namespaces are pointing to the 2010 CAS array.
### Exchange 2013
multi rol servers
namespaces internal and external webmail.contoso.com
Outlook Anywhere configured with NTLM, internal clients do not require SSL, external yes.
outlookprovider: EXPR is MSSTD:webmail.contoso.com
The servers are in the build fase and we started testing the servers before putting in production by moving the namespaces. To avoid problems during the configuration, we changed the SCP of the 2013 servers to the FQDN of the 2010 servers. The SCP records are only filled with 2010CAS servers.
I am trying to test the Exchange 2013 servers:
OWA: works correct, proxy to 2010 mailbox gives no problems.
Autodisover/autodiscoverpage gives an Error code 600, thats ok.
We have created a mailbox on the 2013 server and added a hostfile on a client so that the CAS2010 servers (SCP) are resolved to the CAS2013 server. Because the cas2010 fqdn's are added to the certificate, no SSL warning is displayed.
For testing purposes in other migrations we never had problems with changing the hostfile to test the autodiscover process. But now, if we use Outlook 2013 and want to connect to the 2013 server, Outlook is configured by autodiscover to use the CAS-Array as entry point. Sure that's not going to work.
Manually configure the outlook client doesn't work either.
What is going wrong.......
Marcel