I'm testing various scenarios for migrating from 2007 to 2013.  I was hoping for some feedback on 2 different scenarios to see which would be the recommended path.  I have a hub transport / client access 2007 server where OWA is servername.domain.com for internal and external access, where servername is the actual name of the server.

Should I

a) abandon the old internal / external address and update my public certificate with a new subject alternative name and then update all smart phones to the new address and direct users to access OWA internally and externally with the new address.  This would also entail updating internal systems that send mail directly to the hub transport like copiers.

b) just add my new Exchange 2013 server and assign it the same external / internal owa address (the actual server name would be different) and then work quickly to migrate everything and decommission the old server so that there is no naming conflict once it's shut down.

• Edited by Seth Killey 17 hours 5 minutes ago

Hello

tip:

external owa, eas, Outlook Anywhere point to new exchange server and exchange 2013 can redirect owa /legacy name/ and eas,Outlook Anywhere  proxy to 2007 if user mailbox on 2007 server.
before install latest ru to 2007 and start install with latest exchange 2013 cu.

Thanks for the reply Sneff, however it doesn't really answer my question.  Let me re-phrase so my scenario is a little more clear.

Currently: Exchange 2007 Client Access / Hub transport server hostname is server1.domain.com.  Internal and External addresses for owa, oab, active sync, etc all point to server1.domain.com

In an ideal world this would have been set up as mail.domain.com for all internal / external addresses with a separate hostname, but alas this is not the case

So, do I just transition to mail.domain.com going forward with Exchange 2013 (and alert all staff to the new address) or can I just use server1.domain.com for internal / external addresses on the new Exchange Server 2013 (with hostname of server2.domain.com) even though for a short period the old server1.domain.com hub transport and client access server will still exist on the domain.

Does this make sense?

Hello

sorry..

if you dont want new public cert and public cert only have one domain name i think chose b.

Apart from above suggestion, I would refer you on this informative technet blog that could be a good approach to achieve the migration goal in more easier way : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Moreover, if you wish to get this job done automatically, you may also give a shot to this automated solution (http://www.exchangemailboxmigration.com/) that could be an appropriate alternative solution for you.