Hi there,
I've browsed through reams of documentation regarding 2007 to 2013 migration, but am unclear on a few points:
My Exchange 2007 deployment is split into a CAS server and a mailbox server, and hosted at a datacentre. Almost all of my users use OWA/ActiveSync/Outlook Anywhere (there's 166 mailboxes and only 15 or so 'onsite'). I've done the work to patch 2007 and 2013 to the relevant versions.
My questions are as follows:
- With mention of creating a 'legacy' DNS namespace, are we just talking a 'legacy.companyinternalname.local' A-record inside the hosting site, or a 'legacy.company.com' A-record external to the datacentre in internet DNS? (My servers are behind NAT)
- Which CAS server am I going to be using during the migration process to give connectivity to the mailboxes yet to migrate? the 2007 one or the 2013 one? and do I need to poke the 2013 one through NAT before the migration or after the migration?
- When obtaining certificates for the 2013 server I intend to take 'webmail.company.com' from the 2007 CAS server and apply it to the 2013 server. How do I do that if the above scenarios require 2 CAS servers poked through the firewall?
Frankly, I can't fathom out how to migrate and avoid downtime during the migration. The documentation so far is a little lacking and i'm sure I must be one of the earlier guys to attempt this, but there must be people out there who've done this already?
Incidentally, I have already migrated my test mailbox from 2007 to 2013 and I can't see it via the 2007 CAS, and I keep getting strange redirects when poking the uncertificated 2013 server through the firewall with a different internet IP and trying to log into mailboxes still housed on the 2007 server (although the test mailbox worked fine, but you'd expect that).
Thanks,
Mike.