Exchange Server 2000/2003 OWA without front-end server
| Article:HOWTO38216 | | | Created: 2010-12-24 | | | Updated: 2012-06-27 | | | Article URL http://www.symantec.com/docs/HOWTO38216 |
In the following example configuration there are no front-end Exchange Servers.
Instead, users connect to an Exchange Server that is configured as a back-end Exchange Server. This configuration can provide more security. You can force users to use IWA authentication instead of basic authentication when the clients connect to the Exchange Servers. Anonymous authentication is used for the connection between the Exchange Server and the Enterprise Vault server. The Data Access account is configured to manage the anonymous connections.
See Configuring Enterprise Vault for anonymous connections.
Connecting OWA clients directly to the back-end Exchange Server is a good way to troubleshoot problems with Enterprise Vault in the OWA clients. This test is also useful after you have upgraded the Enterprise Vault OWA Extensions, or made changes to OWA files on the Exchange Server.
As in previous configurations, an Enterprise Vault Exchange Desktop policy setting can be used to enable OWA 2003 clients to connect directly to the Enterprise Vault server. Direct connections are used when users start Archive Explorer or an archive search from their OWA client.
If your environment is configured as follows, then the Exchange Server 2003 back-end server and the Enterprise Vault Web server URL must be published to clients:
Clients connect to the Exchange Server 2003 back-end server through an ISA Server.
Direct connections are configured for Archive Explorer and archive search.
If direct connections are not configured (which is the default for Exchange Server 2003 OWA), then only the Exchange Server 2003 back-end server needs to be published.
|
|
Legacy ID
v9934745_v34981136
Article URL http://www.symantec.com/docs/HOWTO38216
Terms of use for this information are found in Legal Notices










Thank you.