OWA 2007 and OWA 2003 mixed environment

The following configuration shows a possible mixed OWA 2007 and OWA 2003 environment. OWA 2007 clients access the Exchange 2007 Mailbox server through the Exchange 2007 CAS server. OWA 2003 clients access the Exchange Server 2003 back-end server through the Exchange 2007 CAS server.

This mixed configuration may exist while Exchange Servers are gradually being upgraded to Exchange Server 2007.

Figure: Mixed OWA 2007 and OWA 2003 configuration

Mixed OWA 2007 and OWA 2003 configuration

In this configuration, the Enterprise Vault OWA 2003 Back-End Extensions are installed on Exchange Server 2003 and Enterprise Vault OWA 2007 Extensions are installed on the Exchange 2007 CAS server. OWA 2003 users access their mailbox using a URL such as https://cas_server/exchange, rather than http://cas_server/owa. This is because Enterprise Vault extensions on the Exchange 2007 CAS server do not process requests from OWA 2003 clients. Instead, these requests are just passed to the appropriate Exchange Server 2003 back-end server.

If an OWA 2003 client accesses a mailbox on Exchange Server 2003 through the Exchange 2007 CAS server, then any Archive Explorer or archive search requests will always attempt to access the Enterprise Vault server directly (irrespective of the value of OWA setting, Client Connection, in the Exchange Desktop policy).

If OWA 2007 clients need access to archived items in public folders on Exchange Server 2003, then you need to perform additional configuration steps. The configuration steps are described in the following technical note on the Enterprise Vault Support Web site:

http://entsupport.symantec.com/docs/317582.

If clients connect through a Microsoft ISA Server, then you will need to publish to clients the OWA site on the Exchange 2007 CAS server and the Enterprise Vault Web Access application.

See Using ISA Server with Enterprise Vault.

The Exchange Server 2003 back-end server and the Exchange 2007 CAS server connect to the Enterprise Vault server using anonymous authentication. On the Enterprise Vault server, the Data Access account is configured to manage the anonymous connections.

See Configuring Enterprise Vault for anonymous connections.