How to configure Exchange 2013/2016/2019 to forward journaled messages to Enterprise Vault SMTP Archiving Servers for archiving

book

Article ID: 100038566

calendar_today

Updated On:

Description

There may be a desire to take advantage of SMTP Archiving to ingest journaled messages and forgo the traditional exchange journaling process. Listed are steps that can assist customers in configuring their current Exchange 2013 environment to utilize SMTP Archiving to journal messages.

Step 1. Create a Remote Domain From the Exchange Management PowerShell

Remote Domain:

In previous versions of Exchange Server, the Exchange Management Console was used to create a Remote Domain; in Exchange Server 2013 the ECP/EAC has no analogous functionality so you must use PowerShell to create the Remote Domain.

To create a Remote Domain, you must enter a Name to describe the domain, and the actual Domain Name to use. In this example, EnterpriseVault.local is the "fake" Domain Name that is used.

Open Exchange Server 2013, and click Exchange Management Shell.

a. Execute the following command to create the remote domain; this command ensures
TNEF encoding is disabled:

New-RemoteDomain -DomainName EnterpriseVault.local
-Name "EV SMTP Server"

b. Next, execute the following command to enable auto-forwarding:

Get-RemoteDomain | Where {$_.DomainName -eq
"EnterpriseVault.local"} | Set-RemoteDomain -TNEFEnabled
$false -AutoForwardEnabled $true

c. Enter the following command to verify the settings:

Get-RemoteDomain | Where {$_.DomainName -eq
"EnterpriseVault.local"} |Format-table Name, DomainName,
TNEFEnabled, AutoForwardEnabled

Step 2. Create a Recipient Mail Contact/Alternate Email Address

The Mail Contact is the account that is to act as a "holding location" for journaled messages. The email address associated with this account is the designated recipient and must be associated with a non-existent, non-routable dummy Domain Name created above in Step 1. Use the following steps to create the Mail Contact:

Open Exchange Server 2013, and in the Exchange Admin Center (EAC) click recipients in the left pane, select contacts at the top of the page, and then click the Add icon to create a new Mail contact:
In the new mail contact page, enter details for the designated recipient account details:
Click save. The new contact contact is displayed on the contacts list.

Step 3. Create a Send Connector for the Remote Domain

To route journaled mail that is sent to the mail contact that was created in Step 2 to the Enterprise Vault SMTP Server(s), use the following steps to create a Send Connector for the Remote Domain:

Open Exchange Server 2013, and in the EAC click mail flow in the left pane, select send connectors at the top of the page, and then click the Add icon to create a new send connector:
In the Name field, enter a name for the connector, and in the Type section, select Custom:
Click next. In the Network settings page, select Route mail through smart hosts and click the Add icon:
Click next. In the add smart host page, enter the fully qualified domain name (FQDN) or IP Address of the EV Server:
Click save. The FQDN or IP Address displays in the SMART HOST list; verify the address:
Set the authentication the Send Connector will use to connect to the Enterprise Vault Server; click next:
In the Address space section, click the Add icon:
In the Address Space page | Full Qualified Domain Name (FQDN) enter the domain that matches the domain for the external email address used to create the journal contact, for example, EnterpriseVault.local:
The domain is added to the Address space list:
Click next. In the Source server section, click the Add icon:
Verify all of the appropriate Exchange Servers are listed; click add to add additional servers.
Click ok. In the Source server page, the selected servers display:
Click finish. The new send connector displays as enabled in the send connectors list.
Click the Edit icon to edit the Send Connector properties. From the Maximum send message size (MB) drop-down list, select unlimited, and then click save: