Deploying the ESExchangeServices web service on the Exchange Server

To collect folders, items, and user permissions from user mailboxes, you must deploy a web service that is provided with Watson Explorer Content Analytics on the Microsoft Exchange Server 2007, 2010, 2013, or 2016 Mailbox server before you configure an Exchange Server crawler. Exchange 2016 is supported in fixpack 11.0.2.3 and later.

Procedure

To deploy the ESExchangeServices web service on the Exchange Server Mailbox server:

Copy the ES_INSTALL_ROOT/bin/ESExchangeServices.zip (or ES_INSTALL_ROOT/bin/ESExchangeServices2013.zip for Exchange 2016) file to the Exchange Server server and extract all files from the archive file.
Put the extracted files in the C:\inetpub\wwwroot\ESExchangeServices directory. This path is the default IIS website.

Exchange Server 2010 only: Edit the Web.config file. Locate the following section and change the value of the bindingRedirect newVersion attribute to 14.0.0.0:

<dependentAssembly>
<assemblyIdentity name="Microsoft.Exchange.Management"
    publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="8.0.0.0" newVersion="14.0.0.0"/>
</dependentAssembly>

Exchange Server 2013 only: Edit the Web.config file. Locate the following section and change the value of the bindingRedirect newVersion attribute to 15.0.0.0:

<dependentAssembly>
<assemblyIdentity name="Microsoft.Exchange.Management"
    publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="8.0.0.0" newVersion="15.0.0.0"/>
</dependentAssembly>

Open the IIS Manager and create an application pool:

Option	Description
Exchange Server 2007	Right-click Application Pool and click New ->Application Pool. Set the value of the application pool ID to `ESServicePool`. Select the option to use the existing application pool as a template, and select DefaultAppPool as the application pool name.
Exchange Server 2010, 2013, and 2016	Click Application Pool in the left pane and click Add Application Pool in the right pane. Set the value of the name to `ESServicePool`, select v2.0 for ES 2010, and select v4.x for ES 2013 and 2016 as the .NET framework version, and select Classic as the managed pipeline model. Click Advanced Settings and set the value of the process model identity to NetworkService.

Open server site tree for the default web site. The ESExchangeServices folder is included in the tree. Convert this folder to an application:

Option Description

Exchange Server 2007

Option	Description
Exchange Server 2007	Right-click the folder and select Properties. Click Create and select ESServicePool as the application pool. Click Configuration. If there is no .asmx mapping, click Add and set the value as shown here (modify the version number for your environment): `Executable: C:\windows\microsoft.net\framework64\v.2.0.50727\aspnet_isapi.dll Extension: .asmx Verbs: All verbs` `Executable: C:\windows\microsoft.net \framework64\v.2.0.50727 \aspnet_isapi.dll Extension: .asmx Verbs: All verbs` Open the ASP.NET tab, select ASP.NET version, and click Apply.
Exchange Server 2010, 2013, and 2016	Right-click the folder and select Convert to Application. Right-click the folder again, select Manage Application -> Advanced Settings, and select ESServicePool as the application pool.

Right-click the folder and select Properties.
Click Create and select ESServicePool as the application pool.

Click Configuration. If there is no .asmx mapping, click Add and set the value as shown here (modify the version number for your environment):

Executable: C:\windows\microsoft.net\framework64\v.2.0.50727\aspnet_isapi.dll
Extension: .asmx
Verbs: All verbs

Executable: C:\windows\microsoft.net
\framework64\v.2.0.50727
\aspnet_isapi.dll
Extension: .asmx
Verbs: All verbs

Open the ASP.NET tab, select ASP.NET version, and click Apply.

Exchange Server 2010, 2013, and 2016

Right-click the folder and select Convert to Application.
Right-click the folder again, select Manage Application -> Advanced Settings, and select ESServicePool as the application pool.

Confirm the ESExchangeServices application settings.

By default, the SSL setting is enabled, and Basic and Windows authentication are enabled.

Option Description

Exchange Server 2007

Option	Description
Exchange Server 2007	Right-click the folder, select Properties and open the Directory Security tab. Click Edit in Secure communications and select Require secure channel. Click Edit in Authentication and access control and clear the Enable anonymous access check box. For authenticated access, select the Integrated Windows authentication and Basic authentication check boxes.
Exchange Server 2010, 2013, and 2016	In the features view, click SSL Settings and select Require SSL. Click Authentication and enable Basic and Windows authentication. Confirm that anonymous authentication is disabled. If there is an error when opening the Authentication setting, edit Web.config and remove the `<system.web>` entry.

Right-click the folder, select Properties and open the Directory Security tab.
Click Edit in Secure communications and select Require secure channel.
Click Edit in Authentication and access control and clear the Enable anonymous access check box. For authenticated access, select the Integrated Windows authentication and Basic authentication check boxes.

Exchange Server 2010, 2013, and 2016

In the features view, click SSL Settings and select Require SSL.
Click Authentication and enable Basic and Windows authentication. Confirm that anonymous authentication is disabled.

If there is an error when opening the Authentication setting, edit Web.config and remove the <system.web> entry.

Confirm that the deployment was successful by accessing the server at https://Exchange Server_hostname/ESExchangeServices/ESExchangeServices.asmx.
After you authenticate, the Custom Service page should show the supported operations, such as GetGroup, GetMailbox, GetMailboxPermission, GenUserDomain, and WhoAmI.