RPC over HTTP: Configuring Enterprise Vault Extensions in an active/active Microsoft cluster

Although Enterprise Vault RPC Extensions are supported in active/active clustered Exchange Virtual Server configurations, such configurations are not recommended by Microsoft and should be avoided, wherever possible.

In an active/active configuration, it does not matter which node you install the Enterprise Vault Extensions on first.

Running the Enterprise Vault RPC configuration wizard on the first active node will perform the following tasks:

Create the following IIS virtual directories on the active node computer:
- ```
EnterpriseVaultProxy
```
- ```
EVOWA
```
Populate the Proxy bypass list on the active node computer from the file, Enterprise Vault\OWA\EVServers.txt.

Examine the log file, Enterprise Vault\OWA\BackEnd200nSetup.wsf.log, for any errors.

When you then run the Enterprise Vault RPC configuration wizard on the other active node, it performs the following tasks for the Virtual Exchange Server associated with that node:

Create the following IIS virtual directories on the active node computer:
- ```
EnterpriseVaultProxy
```
- ```
EVOWA
```
Populate the Proxy bypass list on the active node computer from the file, Enterprise Vault\OWA\EVServers.txt.