Exchange Server Forums

OWA in co-existence Envt. having problem

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> OWA in co-existence Envt. having problem

Page: [1]

Message

<< Older Topic Newer Topic >>

OWA in co-existence Envt. having problem - 19.Nov.2008 1:02:42 PM

samybhatia

Posts: 28
Joined: 3.Apr.2008
Status: offline

Hi,

We have co-existance envt. of 2003 and 2007 and need to access to OWA/exchange without asking users to learn one more website.

We want that web mail (2003) will automaticall redirect user to their new url based on their mailbox if on 2007.

We have http://mail.domain.com for x2003 and http://email.domain.com for x2007.

Now when user is trying to access his mailbox thru http://mail.domain.com while being his mailbox on 2007 it is redirecting to x2007 server (using FQDN, instead email.domain.com) next page with error message "There is a problem with this website's security certificate" and if you click "Continue to website(not recommended)" it will take you to right one.

My question is is there any way we can get rid of this middle error page..by directly specifying the redirection to email.domain.com (rather than fqdn of x2007)

Did I mention we do have SSL for this new site and server. And this is for internal access(Intranet) only. As eventually we will replace the url once we decommision the x2003.

We have all the roles of x2007 installed on one server. (CAS, Mailbox & Hub)

It may sound confusing but please feel free to ask if u need more clarification.

Thanks in advance.

< Message edited by samybhatia -- 19.Nov.2008 1:32:56 PM >

Post #: 1

Featured Links*

RE: OWA in co-existence Envt. having problem - 19.Nov.2008 8:52:41 PM

Elan Shudnow

Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline

The general way to coexist and have a single URL is:
1. Deploy a CAS that does not contain the Mailbox Role
2. Place a certificate on CAS that contains the existing FQDN that users utilize to access their 2003 environment. For example, if you currently use https://webmail.domain.com/exchange to access OWA, you'd have a certificate that contains at least webmail.domain.com and put that on the CAS.
3. Ensure that Integrated Auth is enabled on /exchange directory on your 2003 BackEnd
4. Have all users go through CAS for OWA. The CAS will pull up the 2007 OWA experience for users who are on 2007 and the 2003 OWA experience for users on 2003.

Of course it's always good to test the functionality with a HOSTS file point to the CAS before you cut over production DNS.

Here's some more info:
http://msexchangeteam.com/archive/2007/02/07/434523.aspx
http://msexchangeteam.com/archive/2007/09/04/446918.aspx
http://msexchangeteam.com/archive/2007/09/10/446957.aspx

_____________________________

Elan Shudnow
Exchange MVP
http://www.shudnow.net

(in reply to samybhatia)

Post #: 2

RE: OWA in co-existence Envt. having problem - 20.Nov.2008 10:44:33 AM

samybhatia

Posts: 28
Joined: 3.Apr.2008
Status: offline

Elan, Thanks a lot for your time and response.

Any way you can achieve this without putting a CAS on seperate server..?

As right now also it is working fine by using x2003 url (mail.domain.com) but with one additional step, which is throwing an error message before going on x2007 server using their FQDN name (http://servername.domain.com) instead (http://email.domain.com)

Off course if we are directly using url of x2007 it's working fine.

Thanks again for your help.

(in reply to Elan Shudnow)

Post #: 3

RE: OWA in co-existence Envt. having problem - 20.Nov.2008 12:09:03 PM

Elan Shudnow

Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline

Have you read the above links? They describe all the different scenarios with URLs that are possible.

_____________________________

Elan Shudnow
Exchange MVP
http://www.shudnow.net

(in reply to samybhatia)

Post #: 4

RE: OWA in co-existence Envt. having problem - 20.Nov.2008 12:54:26 PM

samybhatia

Posts: 28
Joined: 3.Apr.2008
Status: offline

Yes, they all talk about accessing x2003 mailbox from Owa / x2007 url. Which they say You need to have seperate CAS server if you want to access through one link. But no one talks about x2007 from x2003.Except one article "If your mailbox is located on an Exchange 2003 server you need to enable Integrated Windows Authentication via Exchange System Manager." Which I did but with no luck.

Additionally MS-KB says "If you do not have multiple Active Directory sites in your organization, you do not have to configure Exchange 2007 for proxying or redirection."

< Message edited by samybhatia -- 20.Nov.2008 1:08:05 PM >

(in reply to Elan Shudnow)

Post #: 5

RE: OWA in co-existence Envt. having problem - 20.Nov.2008 1:10:48 PM

Elan Shudnow

Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline

You can't access a 2007 Mailbox from a 2003 Front End. You'd need to move over to the CAS separate from the Mailbox role to provide OWA access to both 2003 and 2007. No other way.

_____________________________

Elan Shudnow
Exchange MVP
http://www.shudnow.net

(in reply to samybhatia)

Post #: 6

RE: OWA in co-existence Envt. having problem - 20.Nov.2008 1:15:02 PM

Exchange_Geek

Posts: 1287
Joined: 31.Dec.2006
Status: offline

Oh and btw using E2k3 FE in an existing E2k7 environment isnt supported nor recommended either.

(in reply to Elan Shudnow)

Post #: 7

RE: OWA in co-existence Envt. having problem - 20.Nov.2008 1:16:35 PM

Elan Shudnow

Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline

Yep, pretty much one of the reasons you typically deploy a CAS and have that Front End both environments and not the other way around.

_____________________________

Elan Shudnow
Exchange MVP
http://www.shudnow.net

(in reply to Exchange_Geek)

Post #: 8