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 Tuesday, March 10, 2015 2:17 PM

Hello

I would recommend you to add the same Internal and external url name space with exchange 2013 redirect all clients to new cas server 2013 then move mailboxes from old exchange 2007 mailboxes to 2013.

this way it will be easy for you to migrate all mailboxes.

Yep, that's the document I'm working off of

I think what I'm going to do is to temporarily assign owa, oab, active sync etc mail.domain.com.  Once the old hub transport / cas server is decommissioned and shut down I'll re-run my powershell scripts to server1.domain.com.

thanks all