OK, Exchange 2003 - 2010 migration gurus, here is one for you:
We are upgrading from Exchange 2003 to Exchange 2010. All Exchange 2003 and Active Directory pre-requisites are met. We are about to install Exchange 2010 CAS role first, and the Exchange 2010 mailbox/hub transport roles on a different VM. The current external Exchange 2003 OWA URL is webmail.domain.com. We have a requirement to use a different OWA URL for Exchange 2010 CAS such as webmail2.domain.com. The requirement is that existing Exchange 2003 users are going to continue using webmail.domain.com without interruption, while new test mailboxes in Exchange 2010 and any pilot mailboxes migrated from Exchange 2003 to Exchange 2010 will use the new Exchange 2010 URL (webmail2.domain.com). The idea is that during that time period, a new SSL VPN solution will be tested and validated for Exchange 2010 remote access. Once the solution is tested and validated, the existing Exchange 2003 OWA URL will be switched to point to the Exchange 2010 CAS via the SSL VPN solution, and we will then create a Legacy DNS record to point to the Exchange 2003 front end server to allow for re-direction for users still on Exchange 2003. The questions are:
- Is this a valid approach?
- Will the introduction of Exchange 2010 in this manner not interrupt the user community during the co-existence period? Or will Exchange 2010 just take over?