mark-grant
asked on
Exchange 2010 - New Exchange Certificate / Legacy Exchange Server
Current production server is Exchange 2003 SP2 (v6.5 Build 7638.2) on Windows 2003 SP 2 Standard. New host has installed Windows 2008 R2 SP 1 with Exchange 2010 SP1 and custom installation of CAS. The plan is run a Transition Method from Exchange 2003 to Exchange 2010 moving mailboxes over time. OWA and OAB are currently in prodction using SSL (owa.contoso.com). I plan to use the same FQDN for the Exchange 2010 in support of OWA and OAB. I am not clear on the "New Exchange Certificate" option for "Legacy Exchange Server". I have purchased a new SSL for Exchange 2010 server. My plan was to use the same FQDN (owa.contoso.com).
My questions: Do I select "Use Legacy Domains" and can I use owa.contoso.com in the "Domain name to use for legacy servers"? Can I have OWA and OAB running on both Exchange 2003 and Exchange 2010 with same FQDN? What happens when I start migrating mailboxes?
My questions: Do I select "Use Legacy Domains" and can I use owa.contoso.com in the "Domain name to use for legacy servers"? Can I have OWA and OAB running on both Exchange 2003 and Exchange 2010 with same FQDN? What happens when I start migrating mailboxes?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Alternately can I leave owa.domain.com in the CAS "Configure Client Acess Server External Domain" and do not select to support owa.domain.com (2003 Exchange OWA/OAB) in "Use Legacy Domains" in Exchange 2010? The idea here would be to not have a new host for OWA/OAB on Exchange 2010 in the end. There are too many smartphones and users to touch.