two domains ( xxxx.net and the other one is xxxx.edu,kw ) the AD domain name is xxxx.net and i’ve exchange 2013 with it, in order to migrate to O365 i’ve added the other domain as alternative xxxx.edu.kw and configure the DNS so now all the mailboxes are in the cloud ( xxxx.net and xxx.edu.kw ) and has the same mailbox synced with the ADconnect, now they need to cancel xxxx.net at all and keep only xxx.edu.kw

what i did is i created a new AD with the new domain name xxx.edu.kw and move all the users and groups using ADMT.

my question do i install a new exchange server with the new domain and then install a new ADconnect or what’s the best solution for this ?

I am confused. Is this where I rename the 2010 URLs to a legacy name?
Then move the production URL “mail.contoso.com” to the 2016 server URLs at mailflow cutover time?

This is what we did from 2007 to 2010 coexistence.

Or, do i just switch the client connections to hit the new load balanced 2016 servers, and then they will route mail to both 2016 and 2010 mailboxes in coexistence?

Josh

The servers using the new namespace will need to be in a new/separate AD site than the existing servers. Other than that, as long as you get your certificates in place correctly, there should be no issues.

In our environment, we are looking to introduce Exchange 2013/2016 to stand up a new platform to consolidate 3-4 Exchange orgs (read M&A). The Exchange 2013/2016 is to have a new namespace as the old one does not reflect the new business. The new platform will be across 2 regions and in their own AD sites

Will this be any connectivity issues when migrating users from Exchange 2010 to Exchange 2013/2016 because the namespace will be different? Anything else that we need to look out for certificates, etc?

Thanks.

Regards

You say they aren’t using split DNS but then say they have a public DNS zone and the same zone hosted internally on their DCs? That means they are using split DNS.

You can use any namespace you want to configure on the Exchange virtual directories. Just add the appropriate records to DNS for that namespace.

No namespaces/vdirs, should point to the servers FQDNs.

They only have the publicly hosted DNS externally, and a matching external zone that is published internally on their domain controllers. They don’t and are not getting a load balancer. All of their internal virtual directories point directly to the server FQDN’s as well as the SCP records. They have an external name space (SMTP.domain.com) that they use for OWA.

My question is this. Should I create a new namespace internally for them? Or is there a way that I could configure the records on the internal DNS servers to use SMTP properly? Thanks again as always sir.

I’ll update DNS internal and external once Exchange 2013 is gone. Got a wildcard cert on Exchange 2016, so that should be fine…. hopefully.

Thanks again. You’re the man!

I think they won’t update. But as long as the old name still resolves in DNS and the SSL cert if still valid for that name (as well as the new name obviously) then it should be okay.

Great! I’ll do so tonight while everybody is out.

Do you know if this will also cause ActiveSync/Mobile devices to automatically update their connection point to mail.contoso.com? Or will I have to touch all of those?

Thanks so much for your quick reply.