If Exchange 2003 is used with co-existence you have to do this from Exchange 2010 EMC or EMS from Server Configuration -> CAS -> Outlook Web App. Select Exchange 2003 and type in legacy.domain.com as the external name. Or using cmdlet; Set-OWAVirtualDirectory -Exchange2003URL ‘https://legacy.contoso.com/exchange’ -Identity ‘CASSERVER\OWA*’
Make sure that Windows Integrated is used on the OWA sites (NTLM) so it will be single sign on.
Add a DNS record for legacy.domain.com to point to Exchange 2003/2007 server.
Final step will be to change the firewall rules so it instead of pointing to the old server, point it to the Exchange 2010 CAS server(s).
I hope this will help someone!
If using this example in your organization, make sure to test it before using it.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi
After reading and answering in MS forum I can tell you all that this is a very common question that need to be clarified.
Before Exchange 2010 was released there was a built-in function that handled the co-existence for OWA.
A little background check, Exchange 2003 and 2007 could co-existence by pointing to the Exchange 2007 CAS server(s) and use /exchange.
In Exchange 2010 this function is removed and replaced by “Legacy”.
What to think about when you are planning for a co-existence?
http://technet.microsoft.com/en-us/library/bb123515(EXCHG.80).aspx Set-OwaVirtualDirectory -ExternalUrl ‘https://legacy.domain.com/owa’ -Identity ‘CASSERVER\owa (Default Web Site)’
If Exchange 2003 is used with co-existence you have to do this from Exchange 2010 EMC or EMS from Server Configuration -> CAS -> Outlook Web App. Select Exchange 2003 and type in legacy.domain.com as the external name.
Or using cmdlet;
Set-OWAVirtualDirectory -Exchange2003URL ‘https://legacy.contoso.com/exchange’ -Identity ‘CASSERVER\OWA*’
I hope this will help someone!
If using this example in your organization, make sure to test it before using it.
No warranties, use at your own risk.
Also, here’s a helpful link from TechNet:
http://technet.microsoft.com/en-us/library/ee332348.aspx
Share this post
Link to post
Share on other sites