Re: E2k7 CAS/Mailbox server & E2k3 BE server-OWA and iPhone Active syn

Tech-Archive recommends: Fix windows errors by optimizing your registry

An Exchange 2007 CAS is supposed to be able to proxy requests for Exchange 2000 and 2003 servers like a front-end server would. You use the /exchange virtual directory, not /owa. I know this works because I just did it today. In general, you can use the front-end or CAS server to front-end lower versions, but not the other way around. That is, you can't get to an Exchange 2007 mailbox with an Exchange 2003 front-end server. (Exchange 5.5's OWA is a kind of an exception--it was just a MAPI client, though a limited one.) I didn't attend the TechEd session where they supposedly said that (I didn't attend TechEd at all) but if they did say that it would throw a monkey wrench into the typical version transition practice. I know that I've heard that you can't install an Exchange 2010 mailbox server into an organization with Exchange 2007 CAS or earlier front-end servers, because Exchange will throw an error, so I belive you misheard what was said.

Going back to the original post, your Exchange 2007 CAS should be able to open Exchange 2003 mailboxes with the /exchange virtual directory, but not the /owa directory. If it's not working it's not necessarily because of your design, but likely something else. Is http: (non-SSL) OWA open on your Exchange 2003 mailbox server? A front-end server (or CAS, which is working as an Exchange 2003 front-end server in this scenario) requires non-SSL access to OWA on the mailbox server.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Hmoll" <Hmoll@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:145E92A7-C089-4260-956D-BD5A02B64866@xxxxxxxxxxxxxxxx
It's not possible. Afaik, the OWA and BE server versions must match.

I know at TechEd they said Exchange 2010 OWA cannot access mailboxes on
2007. And I thought I remembered the same is true for Exchange 2003, as well.
IE, Exchane 2007, no way, no how, could access 2k/2k3 mailboxes.

In fact, they made a big deal about how OWA 2k10 will redirect to the
appropriate 2k7 server, without (and this was the big deal) having the user
login again.

"amanda a" wrote:

Hi there. I have a W2k8/E2k7 CAS/Mailbox server receiving mail. W2k3/
E2k3 BE server where users mailboxes are still sitting.
Mail flows fine, but users on E2k3 server cannot access OWA (works for
users on E2k7 server) and can't connect their iphones either.

OWA ISSUE DETAILS:
Users with mailboxes on E2k3 server gets the following message when
they go to https:\\mail.domainname.com\owa (which is how its set up in
E2k7 System Manager as the OWA external URL.)

Outlook Web Access could not find a mailbox for domainname\aacheson.
If the problem continues, contact technical support for your
organization and tell them the following: The mailbox may be stored on
a Microsoft Exchange 2000 or Microsoft Exchange 2003 server, or the
Active Directory user account was created recently and has not yet
replicated to the Active Directory site where this Client Access
server is hosted

If users type in https:\\mail.domainname.com\exchange, they get a
Error 404, page not found.

I have OWA set in E2k7 to go to https://mail.domainname.com/owa, I
tried changing authentication settings in webdav tab in E2k7,
disabling Forms based authentication for OWA, tried setting External
URL to \exchange instead...and a bunch of other stuff.

ACTIVESYNC ISSUE DETAILS:
For Activesync, I tried uninstalling and reinstalling outlook anywhere
(set to mail.domainname.com), removing forms based authentication for
OWA, pointing to /exchange in URL tab in E2k7, user was connecting
over 3G network-not wifi, removing SSL authentication for Activesync,
changing the default URL for activesync to mail.domainname.com IIS and
about a million other things. No go.

Please help!
Thanks, Amanda



.

Quantcast