RE: Configureing OWA 2K10 in Coexistence
There is no such thing as CAS-to-FE proxying. However, you can configure the CAS to redirect the user to the Exchange 2003 server. Typically, you will do something like this: Set-OWAVirtualDirectory CAS2008\OWA* ` -Exchange2003URL "https://legacy.example.com"; And the Exchange 2003 server will have the 2010 SAN certificate loaded which includes legacy.example.com. This does necessitate that you have TWO external IP addresses. You configure redirection the same as you did in Exchange 2003 and/or Exchange 2007 - you put a redirection script in the root of the website, whether it's ASP, ASPX, Perl, or whatever. I cover this in the May 2010 cover article of WindowsITPro. :) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Friday, March 26, 2010 11:12 AM To: MS-Exchange Admin Issues Subject: Configureing OWA 2K10 in Coexistence All- I'm setting up an server with all the roles on one server. Currently the client is using https://webmail.company.com to access their webmail externally to their E2K3 box. What I want to do is use that same name on the E2K10 CAS server and have E2K10 handle all OWA request for both servers (e2k10, e2k3). What I'm unsure of is how do I setup redirection so users won't have to type out https://webmail.company.com/owa? Thank you, John Bowles
RE: Configureing OWA 2K10 in Coexistence
>And the Exchange 2003 server will have the 2010 SAN certificate loaded which >includes legacy.example.com. Upgrading our existing cert costs more than just getting another cert for legacy.mycompany.com so a silly question… An existing cert for mail.mycompany.com points to 2K3 FE’s. Could we move the mail.company.com to the CAS array and get a separate legacy.company.com cert on the FE's? Assume we’re not using OutlookAnywhere externally so (hopefully) no need for autodiscover.mycompany.com. /confused:)
RE: Configureing OWA 2K10 in Coexistence
Sure, you can do that. The disadvantage is that you'll have a short switchover timeframe during which the FE will probably not be accessible. (That is, the interval between when you put in the new certificate and update your DNS and then the DNS propagates to everwhere you need it to.) Using a SAN certificate containing the old and the new name avoids that. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: pramatow...@mediageneral.com [mailto:pramatow...@mediageneral.com] Sent: Friday, March 26, 2010 12:50 PM To: MS-Exchange Admin Issues Subject: RE: Configureing OWA 2K10 in Coexistence >And the Exchange 2003 server will have the 2010 SAN certificate loaded which >includes legacy.example.com. Upgrading our existing cert costs more than just getting another cert for legacy.mycompany.com so a silly question… An existing cert for mail.mycompany.com points to 2K3 FE’s. Could we move the mail.company.com to the CAS array and get a separate legacy.company.com cert on the FE's? Assume we’re not using OutlookAnywhere externally so (hopefully) no need for autodiscover.mycompany.com. /confused:)
RE: Configureing OWA 2K10 in Coexistence
Sorry for the late thank you, but, Thanks:) Decision was go with the SAN cert after all, just to avoid downtime (short as it may be) or any other issues. Paul >Sure, you can do that. The disadvantage is that you'll have a short switchover timeframe during which the FE will probably not be accessible. (That is, the interval between when you put in the new certificate and update your DNS and then the DNS propagates to everwhere you need it to.) Using a SAN certificate containing the old and the new name avoids that. Regards, Michael B. Smith
RE: [MARKETING] RE: Configureing OWA 2K10 in Coexistence
> I cover this in the May 2010 cover article of WindowsITPro. :-) WTG Mike! ~JasonG
