asked on Considerations for Exchange 2010 when changing external domain name.
Exchange 2010 SP1
Single Site Domain/Organisation
HUB, MB and UM running on Server 2008
CAS running on Server 2008
We are, in the next few weeks, going to be changing our external domain name. The change will be distinct: ourcurrentdomain.co.uk -> ournewdomain.org. The change will not involve any changes to any servers or external IP addresses. We have configured our new DNS external zone with correct name to IP mappings. We will have to implement a new authoritative domain in Exchange 2010 as well as new email address policies for our clients to reflect the new domain in their SMTP addresses. Because my superiors want the old domain name to still be usable for a period of time TBD, we've altered our SAN cert by adding the new FQDNs for the new domain as well as making the new domain FQDN for CAS/OWA the CN of the cert whilst leaving all of the original FQDNs for the current (soon to be old) domain in. We are also aware that we will need to change the external URL for OWA in Exchange. Please note, we do not use autodiscover, nor do we have Outlook Anywhere enabled. My question is, after we've implemented these changes, will external users still be able to use https//mail.ourcurrentdoma
Also, on the new cert, I've left the FQDN for Activsync set to the old domain name (since it's not really going anywhere) to avoid having a rush on the IT office from all our mobile users. If we leave the old URL in the Activsync settings in Exchange, will this work? Kind regards,
Adam
Single Site Domain/Organisation
HUB, MB and UM running on Server 2008
CAS running on Server 2008
We are, in the next few weeks, going to be changing our external domain name. The change will be distinct: ourcurrentdomain.co.uk -> ournewdomain.org. The change will not involve any changes to any servers or external IP addresses. We have configured our new DNS external zone with correct name to IP mappings. We will have to implement a new authoritative domain in Exchange 2010 as well as new email address policies for our clients to reflect the new domain in their SMTP addresses. Because my superiors want the old domain name to still be usable for a period of time TBD, we've altered our SAN cert by adding the new FQDNs for the new domain as well as making the new domain FQDN for CAS/OWA the CN of the cert whilst leaving all of the original FQDNs for the current (soon to be old) domain in. We are also aware that we will need to change the external URL for OWA in Exchange. Please note, we do not use autodiscover, nor do we have Outlook Anywhere enabled. My question is, after we've implemented these changes, will external users still be able to use https//mail.ourcurrentdoma
Also, on the new cert, I've left the FQDN for Activsync set to the old domain name (since it's not really going anywhere) to avoid having a rush on the IT office from all our mobile users. If we leave the old URL in the Activsync settings in Exchange, will this work? Kind regards,
Adam
Exchange
Last Comment
stedwardsitdept
ASKER
Arnold,
Thanks for your response. Yes, we're aware of those items as well. What I'm really looking at is trying to figure out if the old OWA address (from our old domain) will still work after the change considering that all those domain references will still be listed on the SAN cert. I would've thought that this connection would be broken after modifying the external URL for OWA from within Exchange. If so, is there some sort of jiggery-pokery that we could do with the default website URL redirection in IIS? Also looking to see if anyone can verify that Activsync will continue to work with the old domain FQDNs since that DNS zone will remain active and the old domain listings will still be on the SAN. We want to avoid having to update everyone's mobile devices right at the time of the switch over (we'll phase them in gradually after the dust settles). Thanks.
Thanks for your response. Yes, we're aware of those items as well. What I'm really looking at is trying to figure out if the old OWA address (from our old domain) will still work after the change considering that all those domain references will still be listed on the SAN cert. I would've thought that this connection would be broken after modifying the external URL for OWA from within Exchange. If so, is there some sort of jiggery-pokery that we could do with the default website URL redirection in IIS? Also looking to see if anyone can verify that Activsync will continue to work with the old domain FQDNs since that DNS zone will remain active and the old domain listings will still be on the SAN. We want to avoid having to update everyone's mobile devices right at the time of the switch over (we'll phase them in gradually after the dust settles). Thanks.
Will external users still be able to use https//mail.ourcurrentdomain.co.uk/o wa to access OWA?
Yes. The domain portion isn't important in this instance - for example you can access OWA at https://IP.of.CAS.svr/OWA
In fact I've just tested pointing a different domain to OWA and it works fine.
ASKER
Thank you BlueCompute. I guess my question now is, how does that work? Is it just down to a DNS entry for the FQDN? If there's no http redirection in IIS and the external URL is set to a specific FQDN, how is the traffic routed to the right place? Got to be DNS, no?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks BlueCompute, that pretty much tells me what I need to know. Awarding your answer the points.
Cheers.
Cheers.
You may eventually need to update the reverse DNS to reflect the new domain reference as well as adjust the name exchange uses in the outgoing connection.