Tune Journal Transformation

This section contains steps to migrate a single test archive within Enterprise Vault to an Office 365 mailbox.

Prerequisites

Complete these steps before beginning the migration:

  • Enable all modules.
  • Enable appropriate Active Directory Domains for scanning.
  • Add an Enterprise Vault Environment for the migration.
  • Create a Link Database for the source archives.
  • Configure Module Mappings for the source archives.

 

Note: It is assumed that the mailbox has been moved to Office 365 already and that it is the EV Archive that will be moved.

Office 365 Global Admin

You need credentials that have sufficient privileges (Global Admin) to configure the Journal Commander to Office 365 connection.

User Principal Name (UPN)

When mailbox information is gathered from Office 365, it’s matched to local Active Directory users by using the Primary SMTP Address.
This means that the local Active Directory users must have the same UPN as the Office 365 users, or they need to have the same Primary SMTP Address.

Note: Journal Commander does not support automatic matching of mailboxes to more than one set of Active Directory users (for example, matching to both on-prem and cloud users) when the same UPNs are present in both Active Directory instances.

Configure the Office 365 Module

The Office 365 module needs credentials supplying to it in order to be able to connect to Office 365. To provide these credentials, follow the steps here.

These credentials will be used by the module when it connects to Office 365.
Note: Additional configuration may be necessary in order to obtain good ingest performance, and/or to work in environments where web/HTTP proxies are used. These are described in the Installation Overview.
Note: Alternatively, you can use Modern Authentication (OAuth) instead of service account credentials. To do this, add the OAuth credentials using the Credential Editor, and also select the Use modern authentication (OAuth) option on the Office 365 Module settings.

To migrate an archive to Office 365, a Journal Commander Office 365 Link is required. Follow these steps to configured it:

  1. Go to the Links page.
  2. Click Office 365 in the Actions Bar.
  3. Click Create Link.
  4. Give the link a name, for example, O365.
  5. Click Create.

The new link needs to have Journal Commander Modules associated with it, and the Staging Area Path needs to match the EV Export Module.

Sync mailbox data

Before you can map a container in the source environment to an Office 365 target, select the Office 365 link on the Links Administration page, and click Sync Mailboxes in the Actions Bar.

Continue now from this information on the Readiness site:

This is a link to our internal readiness site with the information on it.

Tune Stage 2 policies

If an existing Stage 2 workflow policy can’t be used, then a copy should be made of an appropriate one, and commands added/removed, as required.

Tune modules

It’s possible to tune the schedule of the modules so that they only operate at specific times on specific days. It’s also possible to have different configurations run at different times on different days. For example, more or less parallelism could run at specific times of the day to lessen impact on source environments.

Configure Accepted Domains

 

‘All exploded SMTP addresses are always stored in Archive Shuttle; however, only addresses of listed domains are automatically enabled for further processing (IsEnabled=True). All other addresses are filtered out and not available for user interaction. Use a new line to separate multiple domains. (This setting applies only during explosion processes, but not for already exploded addresses.)

Link to article.

What happens if these things aren’t working?

If some of the items on this list are not successful/adequate, work to isolate the issue(s) and resolve them.

Print Friendly, PDF & Email