Skip to main content

Outlook Web Access (OWA) implementation in mixed Exchange 2007 and Exchange 2000/2003 environment

Microsoft documentation about transition to Exchange 2007 suggests that you should install HUB Transport and Client Access (CAS) roles first and than mailbox server role. Exchange 2007 installation order in transition should look like this:

  • Client Access server role
  • Hub Transport server role
  • Mailbox server role
  • Unified Messaging server role

Exchange 2007 CAS role enables users to gain access to their mailboxes through web browser (OWA), ActiveSync or Outlook Anywhere (fromerly known as RPC over HTTPS). It is actually "replacement" for Exchange Front-End server known from previous versions.

Microsoft suggests that you should replace Front-end servers with Exchange 2007 CAS (I think it would be best to say redirect users to new Exchange CAS. Redirection process can be done on FW or just as a change in DNS, but this depends on your network configuration) prior mailbox move from Exchange 2000/2003 to Exchange 2007 mailbox server.

Since new Exchange 2007 OWA is using /owa(https://whatever.yourdomain.com/owa) as virtual directory name, redirection is done automatically if you open https://whatever.yourdomain.com/exchange in your web browser.

Choice whether you will be redirected to Exchange 2007 OWA or Exchange 2000/2003 OWA is based on your mailbox storage location. This means that if your mailbox resides on Exchange 2003 server you will see Exchange 2003 OWA look-and-feel, and if your mailbox resides on Exchange 2007 mailbox server you will see Exchange 2007 OWA look-and-feel. This process is done automatically and the only request is that primary point for OWA is Exchange 2007 CAS server.

So if you access https://whatever.yourdomain.com/exchange...

... OWA 2007 screen will be shown on the page and if your mailbox store is on Exchange 2003 server....

...you will see Exchange 2003 look-and-feel.

Note:
Don't forget to import SSL certificate from your Exchange 2000/2003 server to your new Exchange 2007 Client Access Server (or servers).

Related articles:
http://msexchangeteam.com/archive/2007/02/07/434523.aspx
http://technet.microsoft.com/en-us/library/aa997610.aspx

Comments

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.