Journal Commander Modules

To find software applications that are compatible with Journal Commander modules, check out the Source/Target Matrix article here.

Installing Journal Commander Modules

Note: Before installing any Journal Commander modules, check that all the prerequisites for the planned installation have been fulfilled.
To determine which modules to install on which servers, refer to the Planning Guide. Journal Commander modules are 32-Bit, and can be installed on Windows 2003 servers, if required. For example, when extracting data from older versions of Enterprise Vault.
For a list of supported operating systems for the Journal Commander modules, see the Journal Commander Software page.
The following modules require .NET Framework 4.6.1:

  • EVCollectorModule40
  • ExchangeExportModule
  • ExchangeImportModule
  • ImageMasterModule
  • ImapModule
  • Office365Module
  • NativeformatImportModule
  • NativeFormaMapiImportModule
  • PowerShellModule
  • Metalogix module
  • PowerShellScriptExecutionModule
  • ShortcutProcessModule40

Note: The Office 365 module requires PowerShell v3 and the Azure AD Commandlets and may need to be installed on some Operating Systems.
If the module installer does not find this prerequisite on the system where it is being run it will provide an option to connect to the Internet in order to download it.

Recommended bitness

It is recommended to use 64-bit modules when ingesting data. In many environments an ingest bridgehead server is used to perform the ingestion, and while the machine (physical or virtual) may have 16-GB or more RAM, out of memory errors may be observed from time to time if the regular, 32-bit modules are used.
To use the 64-bit modules, you’ll need to install 64-bit Outlook, and then the 64-bit modules. These modules will utilize RAM beyond the normal 2-GB Windows process limit allow for faster and more reliable migrations to take place.

Office 365 Module

The Journal Commander Office 365 module ingests data into Office 365 mailboxes using the Advanced Ingestion Protocol (AIP) and optionally Exchange Web Service (EWS), utilizing Office 365 ‘service accounts’.

Configure the Office 365 Module

The Office 365 module needs credentials so it can connect to Office 365.

For authentication under modern authentication (oAuth) in Journal Commander, click here. Please note this is the preferred authentication route.

For authentication under basic authentication, click here.

Be aware you must select ONE method of authentication with your Journal Commander project; either basic authentication or Modern Authentication (OAuth). Mixed authentication is not available.

Configure Application Impersonation

For accounts to be used to ingest data into Office 365 mailboxes, the Application Impersonation role needs to be assigned to the user. This can be done in the Office 365 Portal or via PowerShell. To perform the required steps using PowerShell, follow this Microsoft link here.

Configure Access to Office 365 Through a Proxy Server

This information only applies to users using proxy servers. Click here for more information.

PowerShell Execution Module

This module is responsible for executing PowerShell commands in the Stage 2 Workflow for a mapping. It is recommended to have one of these installed in the environment.
It is not necessary to associate this module with a particular link. That process happens automatically, and is controlled by the Core.
Note: This module requires .Net Framework 4.6.1

Print Friendly, PDF & Email