OWA 2000 or 2003 without front-end Exchange Server

In the following configuration there are no front-end Exchange Servers.

Figure: Back-end only OWA 2000 or 2003 example configuration

Back-end only OWA 2000 or 2003 example configuration

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 Access application must be published to clients:

If direct connections are not configured (which is the default for OWA 2003), then only the Exchange Server 2003 back-end server needs to be published.

See Using ISA Server with Enterprise Vault.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.