Description

Some initial planning should be done to properly configure Office Mail App (OMA) to work through a load balancer. The namespace used for example must be determined beforehand. In the following example mail.company.com is the namespace that is used to access outlook web access (OWA) and therefore will also be used to access the OMA app for Enterprise Vault.

Note: Having a single namespace is not a requirement.

1. On an Exchange 2013 or higher server - launch the Exchange Management Shell to configure Office Mail App (OMA) by executing the New-App command. 


Note: Take note of the &BaseURL In this example, the base URL will be set to use Mail.company.com/EnterpriseVault for OMA and Outlook Web App (OWA) will use Mail.company.com/OWA
Note: The above New-App command configures OMA to be available for everyone in the Exchange organization.

2. In NetScaler: Add the Exchange Servers and Enterprise Vault Servers - [Traffic Management - Load Balancing - Servers ]



3. Create a Service for Exchange and a Service for Enterprise Vault [Traffic Management - Load Balancing - Services]

                       

Note: A Service Group [Traffic Management - Load Balancing - Service Group] would be used instead of a Service when you want to load balance between multiple Exchange Servers and/or multiple Enterprise Vault Servers



Note: At least one monitor must be bound to each service. The monitor must be able to successfully communicate to the intended servers (exchange/enterprise vault) to show a status of UP. The default monitor specified for each service created is tcp-default.  

5. Create a Virtual Server for Exchange and then create a Virtual Server for Enterprise Vault.  [Traffic Management - Load Balancing - Virtual Servers]

           

Note: The Exchange Virtual Server does not have an IP Address assigned to it. Select Non Addressable
Note: The Enterprise Vault Server is assigned an available IP Address on the network.



Note: Select the Services or Service Groups (if multiple exchange and/or enterprise vault servers) created in step 3 and bind to the appropriate Virtual Server. 



Note: Each Virtual Server must have an appropriate certificate and corresponding root certificate authority

6.  Create one Content Switching Virtual Server. [Traffic Management - Content Switching - Virtual Servers]

        

Note: The Content Switching Virtual Server is assigned an available IP Address on the network.
Note: The Content Switching Virtual Server IP Address is the IP Address associated to the url Mail.company.com

7. Create an Action for Exchange and one for Enterprise Vault. [Traffic Management - Content Switching - Content Switching Actions]



8. Create a policy for Exchange and one for Enterprise Vault.  [Traffic Management - Content Switching - Content Switching Policies]



Note: The Exchange Policy is bound to the Exchange Action and the Enterprise Vault Policy is bound to the Enterprise Vault Action created in step 7.

9. Edit the Content Switching Virtual Server and bind the Content Switching Policies created in the previous step.

How to Configure Office Mail App (OMA) to work through a Citrix NetScaler Load Balancer