On-Premises Journaling Administration

Once existing AMS Client Servers, SyncManager and VaultBoxes are upgraded to a compatible Client software versions (AMS Client 6.6 or later), Email Archival On-Premises Journaling provides support for Exchange Envelope Journaling. Envelope journaling captures enhanced recipient information from the message envelope, including expanded distribution lists, BCC recipients and alternative recipient information.

On-Premises Journaling provides enhanced metadata to Email Archival Reviewers and provides limited additional metadata to Email Archival Users. For example, Reviewers can see BCC recipients for all messages, whereas Users can only see BCC recipients for messages the user sent.

On-Premises Journaling is supported in both hybrid mode (where both journaled and traditional capture through Redirector Agent mailboxes coexist) and journaled-only mode. Envelope journaled messages can be sent directly to the Data Center instead of using a local VaultBox, depending on the configured environment.

  • Email Archival only customers using journaled-only mode, VaultBoxes, Event Sink and Transport agents would no longer be required.
  • Email Continuity customers, the Event Sink and Transport Agents are still required for partial activation.

To support journaling capture, the AMS client includes a Capture Policy Service that queries Active Directory to determine which Exchange users have been enabled for envelope journaling. Once it determines that a user is enabled for envelope journaling, that information is transmitted to the Data Center and AMS removes that user from Event Sink and the Transport Agent replication lists to reduce the possibility of messages being archived twice. Also, the list of envelope-journaling-enabled users is compared to existing retention policies to help ensure that customers who are members of an AMS data retention policy are also enabled for Exchange journaling.

On-Premises Journaling differs from Cloud Journaling (see About EMS Cloud Services) in that On-Premises Journaling applies to Exchange users and Exchange servers located within the customer’s data center (on-premises). Cloud Journaling applies to Office 365 users whose messages are forwarded to Email Archival from the Office 365 cloud. Customers who have Office 365 users in rich coexistence can use envelope journaling on-premises and within Office 365. These policies are managed within the Exchange management Console and Office 365 Administration Console respectively.

Managing On-Premises Journaling Addresses

The On-Premises Journaling window (Historical Mail > On-Premises Journaling) manages the journaling addresses to which all copies of on-premises journaling mail are sent.

A journaling address is a Global Unique Identifier (GUID). On-Premises Journaling user’s journaling addresses tie to an AMS Data Center.

To a dd On-Premises Journaling Address:

  1. Click on Historical Mail > On-Premises Journaling
  2. Click on Add On-Premises Journaling Address link.
  3. Select the zone for which the address is to be assigned.
  4. Click Create.

To delete On-Premises Journaling Address:

NOTE

Before deleting an existing journaling address and beginning to use a new one, it is recommended you create and configure the new address and allow sufficient time for existing messages which may be currently in-process to be archived/imported before deleting an existing journaling address.

  1. Click on Historical Mail > On-Premises Journaling
  2. To the right of the address to be deleted, click the Delete button.
  3. In the verification pane, click Delete.

On-Premises Journaling Address Best Practices

For most organizations, the single On-Premises Journaling address created when the feature was enabled is sufficient.

If it becomes necessary to retire a journaling address, it is recommended that all journaling rules be updated with a new journaling email address and that sufficient time (up to 48 hours) be allowed to elapse before retiring any existing journaling address.

NOTE

After a journaling address has been deleted from the AMS admin console, new mail received by the AMS Data Center addressed to that deleted address will be rejected, resulting in unrecoverable, lost data.