Hi there,
We have been running Exchange 2010 for about 4 years we have 4 CAS servers in the environment, al of their AutoDiscoverServiceInternalUri are set too:
cas1 - https://cas1.domain.org/autodiscover/autodiscover.xml (actual hostname = cas1.domain.local)
cas2 - https://cas2.domain.org/autodiscover/autodiscover.xml (actual hostname = cas2.domain.local)
cas3 - https://cas3.domain.org/autodiscover/autodiscover.xml (actual hostname = cas3.domain.local)
cas4 - https://cas4.domain.org/autodiscover/autodiscover.xml (actual hostname = cas4.domain.local)
First of all you may be saying they are not set to https://autodiscover.domain.org/autodiscover/autodiscover.xml, however we havent ever had a problem with client not connecting or resolving to their mailbox... We have 4 A records (using dns round robin)
that point to an object called outlook.domain.org that resolve to each of the 4 CAS servers.
My question is based around the microsoft Exchange deployment assistant, specifically "configure service connection point" for the duration of the migration from 2010 to 2013 why can we not just change the A records in DNS to point to the new 2013
CAS boxes, we have deployed the same cert on the new servers and test mailboxes are working without any errors.
It says 2010 and 213 will proxy between depending on if your mailbox is on a new or old DB.
Or is it that you have to create a new object for the 2013 deployment, for example outlook2.domain.org and set the SCP object on every CAS 2010 server to the AutoDiscover URL of the new Exchange 2013 servers? As per the Deployment assistant process.
We would also need to create the DNS round robin a records for outlook2.domain.org for the new servers.
Have i understood this correctly, why cant i just use the same SCP name for the new servers.
Thanks!