Binary Tree E2E Complete Mailbox Migration User Guide

E2E Complete 4.2
User Guide
July 2016
Table of Contents
Table of Contents ............................................................................................................................ 1
1. Introduction to E2E Complete .................................................................................................... 5
About this Document ..................................................................................................................................................5
Supported Mailbox Migration Paths ...........................................................................................................................6
Supported Public Folders Migration Paths .................................................................................................................7
Components of E2E Complete ....................................................................................................................................9
About the E2E Admin Portal .....................................................................................................................................10
2. Creating and Managing Forests ................................................................................................ 13
Adding a New Source Forest .....................................................................................................................................13
Adding a New Office 365 Forest ...............................................................................................................................22
Forest Configuration .................................................................................................................................................26
Forest Alerts ..............................................................................................................................................................27
Deleting a Forest .......................................................................................................................................................28
Source Forest Configuration | General Tab ..............................................................................................................28
Source Forest Configuration | Accounts Tab ............................................................................................................30
Source Forest Configuration | Sites Tab ...................................................................................................................32
Source Forest Configuration | Mailboxes & Public Folders Tab ...............................................................................33
Source Forest Configuration | Credentials Tab ........................................................................................................33
Target Forest Configuration | General Tab ..............................................................................................................34
Target Forest Configuration | Accounts Tab ............................................................................................................36
Target Forest Configuration | Sites Tab ....................................................................................................................38
Target Forest Configuration | Mailboxes & Public Folders Tab ................................................................................39
Target Forest Configuration | Credentials Tab .........................................................................................................39
Tenant Forest (Office 365) Configuration | General Tab ..........................................................................................40
Tenant Forest (Office 365) Configuration | Sites Tab ...............................................................................................42
Tenant Forest (Office 365) Configuration | Licenses Tab .........................................................................................43
Tenant Forest (Office 365) Configuration | Credentials Tab ....................................................................................44
3. Managing E2E Workers ............................................................................................................. 45
Enabling/Disabling Workers .....................................................................................................................................45
Viewing and Editing Worker Settings .......................................................................................................................46
Viewing Worker Processing Statistics .......................................................................................................................48
Viewing the E2E Worker Application ........................................................................................................................49
4. Managing Configuration Settings ............................................................................................. 50
Settings | General Tab ..............................................................................................................................................50
Settings | Activities Tab ............................................................................................................................................52
Settings | Mailboxes Tab ..........................................................................................................................................54
Settings | Public Folders Tab ....................................................................................................................................56
E2E Complete 4.2 User Guide
2
Settings | O365 Groups Tab......................................................................................................................................60
Settings | Workers Tab .............................................................................................................................................61
Settings | Scripts Tab ................................................................................................................................................62
Settings | Notifications Tab ......................................................................................................................................62
Settings | Licenses Tab .............................................................................................................................................66
5. Mailboxes View ......................................................................................................................... 67
Working in the Mailboxes View ................................................................................................................................67
Adding Mailboxes to the Mailbox Jobs .....................................................................................................................74
6. Mailbox Jobs View..................................................................................................................... 78
7. Blackout Times View ................................................................................................................. 81
Overriding Blackouts or Scheduled Migrations ........................................................................................................84
8. Migration Summary View ......................................................................................................... 85
9. Migration Schedule View .......................................................................................................... 86
10. Migration Metrics View .......................................................................................................... 87
11. Public Folders View ................................................................................................................. 89
Adding Public Folders to the Public Folder Jobs .......................................................................................................89
12. Public Folder Jobs View........................................................................................................... 94
Public Folder Migration for Non-Trusted Environments ..........................................................................................95
Migrating Public Folders to Exchange Online ...........................................................................................................99
Migrating Public Folders to Office 365 Groups ...................................................................................................... 106
13. Content Analysis View .......................................................................................................... 109
14. The User Portal ..................................................................................................................... 110
15. Troubleshooting .................................................................................................................... 113
Appendix A: About Inter-Org Migrations ................................................................................... 115
Appendix B: Migrating Mailboxes to Office 365 ........................................................................ 117
Appendix C: Diagnostic and Operational Report Scripts ........................................................... 118
Appendix D: Migration Processing Scripts ................................................................................. 121
Enabling Migration Customization Scripts ............................................................................................................. 121
Migration Customization Scripts ........................................................................................................................... 122
Appendix E: How to Support Schedule+ Free/Busy Coexistence
Between Exchange 2003 and Exchange 2010/2013 ................................................................... 124
E2E Complete 4.2 User Guide
3
Appendix F: E2E Mailbox Job Importer ...................................................................................... 126
Appendix G: E2E Public Folder Job Importer ............................................................................. 131
Appendix H: Public Folder Analysis and Job Administration ..................................................... 134
Public Folder Analysis Scripts ................................................................................................................................. 134
Public Folder Job Administration Scripts ............................................................................................................... 140
Table Definitions .................................................................................................................................................... 146
Job States ............................................................................................................................................................... 147
Public Folder Migration Engine Folder Handling Notes ......................................................................................... 148
E2E Public Folder Migration Child Job Management ............................................................................................. 148
Appendix I: E2E Connectivity Test Results ................................................................................. 149
Appendix J: Mailbox Permissions Migrated ............................................................................... 150
Appendix K: Updating Outlook 2003 Clients for Inter-Org Migrations...................................... 151
The Outlook Profile Update Service (OPUS) .......................................................................................................... 151
End-User Execution of OPUS ................................................................................................................................. 152
Command line execution of OPUS ......................................................................................................................... 155
Allowing for local override when E2E web service is unavailable ......................................................................... 155
E2E Complete 4.2 User Guide
4
1. Introduction to E2E Complete
About this Document
This document provides information about how to use Binary Tree’s E2E Complete to perform migrations from
supported source versions of Microsoft Exchange to supported target versions of Exchange or to Microsoft Office
365 Exchange Online. See Supported Mailbox Migration Paths and Supported Public Folders Migration Paths below
for checklists of supported scenarios.
A separate E2E Complete Installation and Configuration Guide describes how to install and configure the E2E
Complete product.
This document assumes the reader brings some basic admin-level experience with Microsoft Exchange and
Microsoft Outlook. If you are unfamiliar with some Outlook and Exchange terms or concepts that appear in this
document, please refer to the Microsoft documentation.
Online Help
E2E Complete also offers context-sensitive browser-based help from the data-entry screens and tabs of the Admin
Portal.
Getting more information
The E2E Complete Fast Start Guide and Installation and Configuration Guide, both available from Binary Tree,
describe how to get started with E2E Complete, with an orientation to the product’s intended uses and features,
and to the E2E Admin Portal, plus detailed instructions for installing and configuring the product for your
environment.
For additional resources, refer to Support: http://www.binarytree.com/Support.aspx
About E2E Complete
E2E Complete is part of Binary Tree's Complete Migration Technology (CMT) product suite. E2E Complete facilitates
migration from one version of Microsoft Exchange to another. It combines a back-end policy engine with front-end
management components to provide project managers and administrators more control over their Exchange
upgrades.
Key features and functions include:







Workflow engine lets administrators create migration tasks, select objects, schedule jobs, and provide user
self-service.
Unified console enables flexible filtering and selection of mailbox objects.
Content included in the mailbox is moved in one transaction, so mailbox security and permissions
(delegates) are retained.
Reports on object and migration status feed into the console, reducing effort required to create tasks.
Does not require server-hosted agents for any of its functionality.
Public folder migration for Exchange and Microsoft Office 365.
Migration to Microsoft Office 365, resource forest migrations, and Outlook 2003 profile updates.
E2E Complete 4.2 User Guide
5
Supported Mailbox Migration Paths
The current release of E2E Complete supports mailbox migration for these source/target scenarios:
E2E Complete 4.2 User Guide
6
Supported Public Folders Migration Paths
E2E Complete supports inter-org (only) public folders migration for these source/target scenarios:
E2E Complete 4.2 User Guide
7
E2E Complete 4.2 User Guide
8
Components of E2E Complete
The main components of E2E Complete are: the MCP Windows Service, the Admin Portal and the User Portal.
MCP Windows Service
The MCP Windows Service (BinaryTree E2E MCP Service) is the controlling service for all E2E Complete functions.
This service should automatically start. Make sure that BinaryTree E2E MCP Service is started in Windows Services.
Admin Portal
E2E Complete's Admin Portal is a friendly user interface that lets you configure and execute most administrative
tasks associated with a migration. The Admin Portal is a Microsoft Silverlight application that runs in a web browser.
To launch the Admin Portal, double-click the E2E Complete shortcut on your Windows desktop, or select E2E
Complete from the Windows Start menu:
The Admin Portal opens in a browser window. E2E Complete supports Internet Explorer 8 and 9, Firefox and Google
Chrome.
The Admin Portal launches with http://localhost/e2e/admin/default.aspx. You can use localhost, <machinename>,
or the IP address to access the Admin Portal.
E2E Complete 4.2 User Guide
9
User Portal
The User Portal is available for users to postpone and schedule blackouts for their migrations and to provide
alternative notification capabilities.


The User Portal is located at: http://<MachineName>/E2E/user/default.aspx
Windows Authentication is enabled for this virtual application. When performing cross-forest migrations, if
the users in the source forest attempt to connect to the E2E server in the target forest and a trust has not
been established between the two forests, the users will be prompted for their target credentials.
About the E2E Admin Portal
E2E Complete's Admin Portal is a friendly user interface that lets you control various administrative tasks related to
Exchange mailbox migration.
The first time you run the Admin Portal after installing E2E Complete, the program leads you through a series of
screens for you to enter your E2E license key and configure E2E communications with other programs and
hardware. This process is documented in the E2E Complete Installation and Configuration Guide. After that initial
configuration, the Admin Portal lets you update configuration data, define new forests to E2E, designate mailboxes
and public folders for migration, schedule and execute migrations, pause and resume migrations, review migration
statistics, and so forth.
To access the Admin Portal, double-click the E2E Complete shortcut on your Windows desktop, or select E2E
Complete from the Windows Start menu:
The Admin Portal opens as a new tab in your browser called E2E Complete:
We recommend the browser hosting E2E Complete be set to clear its temporary files and history upon
exiting the E2E machine.
E2E Complete 4.2 User Guide
10
Main Toolbar
E2E Complete's Main Toolbar appears across the top of the browser tab:
The toolbar buttons let you change the view of the Admin Portal, to show different types of information and
different groups of available features below the Main Toolbar:

Mailboxes: Lists mailboxes from all the sites in the specified forest. In addition, it allows you to sort, group,
search, and select mailboxes to add to the migration queue.

Mailbox Jobs: Manages the sequence of migration requests for the selected migration destination site.

Public Folders: Displays the public folder tree from the selected Source and Target forest. In addition, it
allows you to sort, group, search, and select public folders to add to the migration queue. Public folder
migration is only enabled during on-premises cross forest migration projects.

Public Folder Jobs: Manages the sequence of migration requests for the selected migration destination.
Public folder migration is only enabled during on-premises cross forest migration projects.

Content Analysis: Allows public folder content information collection and analysis in SQL for data
remediation.

Blackout Times: Allows the configuration of time periods when mailboxes cannot be migrated for the
selected migration site.

Summary: Displays high-level accounting of mailbox migrations, which allows you to view all status levels.

Schedule: Displays estimated migration sequence for the selected migration site. It is a read-only view.

Metrics: Provides historical data and throughput measurements of migrations in a graphical format.

Forests: Configure global forest settings, add new forest, etc.

Workers: Administer public folder migration workers.

Settings: Configure general settings, activities, mailboxes, public folders, workers, scripts, notification
templates, and licenses.

Help: Opens a browser window of context-sensitive Help: field notes and application notes for the currently
open screen or tab. From the context-sensitive Help window, you can navigate to other E2E topics using
the navigation links and tools that appear across the top of the Help display.

About: Displays version information about the E2E Complete product.
E2E Complete 4.2 User Guide
11
Data Panel
In addition to the Main Toolbar, the Admin Portal also contains a Data Panel that displays data depending on the
button that is currently selected.
Version Information
To view version information: Click About in the main toolbar to open the About window:
E2E Complete 4.2 User Guide
12
2. Creating and Managing Forests
E2E Complete migrates data from a source forest to a target forest. The source forest can be any forest in your local
domain. The target forest can be another local forest, or can be a tenant forest in Office 365. Within E2E Complete
we classify forests by three types:

Source Forest: A forest in your local domain from which you will migrate.

Target Forest: A forest in your local domain to which you will migrate. Generically speaking, a "target
forest" can reside either in your local domain or in Office 365, but within E2E Complete we define and
configure Office 365 forests separately (see below). Within E2E Complete you can designate only one forest
of this Target Forest type. A local Exchange target forest is defined when migrating Intra-org (no other
forests would be needed), or when migrating Inter-org (a source forest would be defined).

Office 365 Forest: A forest in Microsoft's Office 365 to which you will migrate. Within E2E Complete you
can designate only one forest of this target forest type.
The first time you run the Admin Portal after installing E2E Complete, the program leads you through a series of
screens for you to enter your E2E license key and configure E2E communications with other programs and
hardware. (This process is documented in the E2E Installation and Configuration Guide.) These screens also prompt
you to identify and characterize your Target Forest—to register it with E2E Complete so the program will know
where the forest resides and how to connect to it. After this initial configuration, you can register and configure one
or more Source Forests.
The subtopics below explain how the Forests view lets you define (register with E2E) forests for cross-forest
migrations, and how to update configuration settings for previously defined forests.
Adding a New Source Forest
To add a new E2E source forest: Click Forests in the main E2E toolbar, and then click Add Forest:
E2E then opens the first of a series of screens to define and configure the new forest. The first in the series is the
Source Forest screen.
Work your way through the screens, as described in the subtopics below. E2E will register the new forest when you
click the Finish button from the Summary screen (the last screen in the series).
E2E Complete 4.2 User Guide
13
Add Source Forest: Source Forest Screen
Enter the name of the Source Forest (top-level domain) you want to add to E2E, and be sure to leave the
Office 365 Forest checkbox unmarked.
Or, if you are migrating to Office 365 and configured the local/on-premises forest during your initial
E2E Forest configuration, you can configure the O365 forest now, and E2E will automatically switch
the two. That is, E2E will correctly configure the on-premises forest as the source and the O365
forest as the target. In that case, mark the Office 365 Forest checkbox and see Adding a New Office
365 Forest below.
The Source Forest must be a fully qualified domain name (FQDN), and must be resolvable in DNS to a domain
controller and global catalog server in the source forest.
When you have entered the Source Forest name:

Click Next to advance to the next screen; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
14
Add Source Forest: Active Directory Screen
Enter the User Name and Password for the account E2E should use for Active Directory calls, and specify the
Global Catalog for this forest. You can mark the Auto-detect a Global Catalog checkbox to have E2E scan your
environment and determine the Global Catalog for you, or manually enter the Global Catalog into the text box.
When these settings appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
15
Add Source Forest: PowerShell Screen
Enter the User Name and Password for the account E2E should use for PowerShell calls. This account should have
PowerShell Remoting access with the Exchange organization.
Leave the Auto-detect PowerShell Hosts checkbox marked if you want E2E to automatically find and specify the
PowerShell hosts, or unmark the checkbox if you want to manually specify the hosts in the respective text boxes:
Exchange 2010 Host, Exchange 2013 Host and Exchange 2016 Host.
A PowerShell host must be specified here as a Fully Qualified Domain Name (FQDN). An IP address will
generate an SSL certificate error.
If you specify the hosts manually, be sure to click the Verify PowerShell Host(s) button to verify connectivity to the
PowerShell host servers.
When these settings appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
16
Add Source Forest: Exchange (MAPI) Screen
These settings are required only when migrating public folders in cross-forest migrations where no trusts exist.
Enter the User Name, Password and Email Address for the account E2E should use for Exchange (MAPI) calls, and
select the Outlook Profile.
If E2E Complete is installed on a Windows 2012 server with Outlook 2010 as the MAPI provider: You
must use an Outlook Profile to connect to a secondary forest.
If the MAPI provider is Outlook 2013: Both trusted and non-trusted Exchange 2013 forests can be
reached without an Outlook Profile.
When these settings appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
17
Add Source Forest: Staged Migrations Screen
This screen is used to specify an Exchange 2010 server and database for E2E to use when an intermediate staging
server is required. E2E does not support direct migration from Exchange 2003 to Exchange 2013 or Exchange 2016,
or from Exchange 2007 to Exchange 2016. In these scenarios, the source is migrated first to an intermediate
Exchange 2010 staging server, and then from the staging server to the eventual Exchange target 2013 or 2016
target.
If you will require a staged migration, make sure the Enable staged migrations checkbox is marked, and specify the
Exchange Staging Server and Exchange Staging Database from the drop-down lists here. If you will not require a
staged migration, just leave the checkbox unmarked.
When these settings appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
18
Add Source Forest: Mailboxes Screen
Select the sites, servers and databases you want E2E to search for mailboxes to migrate. All content is selected by
default.
You can right-click in the list area to select options to expand/collapse levels of the tree.
When the selections appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
19
Add Source Forest: Public Folders Screen
Select the sites, servers, and databases you want E2E to search for public folders to migrate. All content is selected
by default.
You can right-click in the list area to select options to expand/collapse levels of the tree.
When the selections appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish to save all your configuration settings (in all screens in this sequence) and return to the Forests
view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings screen.
E2E Complete 4.2 User Guide
20
Add Source Forest: Summary Screen
Review the displayed summary of the new forest's configuration settings, and determine whether you want to
change any settings before you save them into a new forest record.
If necessary, you can click Previous to return to any previous screen in the sequence to change the settings there.
When this Summary shows all the configuration settings as you want them, click Finish to save all the settings (in all
screens in this sequence) and return to the Forests view, with the newly defined forest opened into the multitabbed Forest Configuration Settings screen.
E2E Complete 4.2 User Guide
21
Adding a New Office 365 Forest
To add a new E2E Office 365 tenant forest: Click Forests in the main E2E toolbar, and then click Add Forest:
E2E then opens its Source Forest screen. This is actually the first screen in a series to define a new source forest, but
a checkbox on this screen lets you shift the feature to the series for an Office 365 tenant forest.
To shift the feature to define a new Office 365 tenant forest, mark the checkbox for Office 365 Forest. The screen
title then changes to Office 365 Forest, and the text-box field name also changes to Office 365 Forest.
Work your way through the screens, as described in the subtopics below. E2E will register the new forest when you
click the Finish button from the Summary screen (the last screen in the series).
Add Office 365 Forest: Office 365 Forest Screen
Enter the name of the Office 365 Forest (top-level domain) you want to add to E2E, and be sure to leave the
Office 365 Forest checkbox marked. (If you unmark the checkbox, the screen will shift back to its Source Forest
mode and the entire screen sequence will change to the Source Forest configuration mode.)
When these settings appear as you want them:

Click Next to advance to the next screen; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
22
Add Office 365 Forest: Exchange Online Screen
Enter the User Name and Password for the account E2E should use for program calls to Exchange Online.
Then, if you will migrate public folders to Exchange Online, specify a Public Folders Migration Mode from the
drop-down list. PowerShell and MAPI are the two available methods.
When these settings appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
23
Add Office 365 Forest: Exchange (MAPI) Screen
These settings are required only when migrating public folders in cross-forest migrations where no trusts exist.
Enter the User Name, Password and Email Address for the account E2E should use for program calls to Exchange
(MAPI), and select the Outlook Profile.
If E2E Complete is installed on a Windows 2012 server with Outlook 2010 as the MAPI provider: You
must use an Outlook Profile to connect to a secondary forest.
If the MAPI provider is Outlook 2013: Both trusted and non-trusted Exchange 2013 forests can be
reached without an Outlook Profile.
When these settings appear as you want them:

Click Next to advance to the next screen; or

Click Previous to return to the previous screen in the sequence; or

Click Finish (if enabled) to save all your configuration settings (in all screens in this sequence) and return to
the Forests view, with the newly defined forest opened into the multi-tabbed Forest Configuration Settings
screen.
E2E Complete 4.2 User Guide
24
Add Office 365 Forest: Summary Screen
Review the displayed summary of the new forest's configuration, and determine whether you want to change any
settings before you save them into a new forest record.
If necessary, you can click Previous to return to any previous screen in the sequence to change the settings there.
When this Summary shows all the configuration settings as you want them, click Finish to save all the settings (in all
screens in this sequence) and return to the Forests view, with the newly defined forest opened into the multitabbed Forest Configuration Settings screen.
Before you can begin migrating to Office 365, you must select Office 365 license packs and related
service plans for E2E to use when auto-licensing Exchange Online mailbox migrations, adding mailboxes
to the migration queue and scheduling mailbox migration to Office 365. Licensing information is
specified in the Licenses tab in the Forest Configuration Settings screen.
E2E Complete 4.2 User Guide
25
Forest Configuration
Forests that have already been defined to E2E can be configured and reconfigured in the multi-tabbed Forest
Configuration Settings screen, which appears in the Forests view below the Forests toolbar. The three different E2E
forest types (Source, Target, and Office 365 Tenant forests) are configured differently, on different sets of tabs.
This illustration shows the screen with the tabs to configure a source forest:
Configuration Tabs for a Source Forest
These tabs are documented under separate topic headings:
General Tab
Accounts Tab
Sites Tab
Mailboxes & Public Folders Tab
Credentials Tab
Configuration Tabs for the Target Forest
These tabs are documented under separate topic headings:
General Tab
Accounts Tab
Sites Tab
Mailboxes & Public Folders Tab
Credentials Tab
E2E Complete 4.2 User Guide
26
Configuration Tabs for an Office 365 Tenant Forest
These tabs are documented under separate topic headings:
General Tab
Sites Tab
Licenses Tab
Credentials Tab
Forest Alerts
The forest selection bar on the Forests view includes a Forest Alert indicator to show the accessibility status of
required components for successful migration. A green checkmark indicates that no issues are detected. A red
exclamation mark indicates that there may be issues that need to be resolved.
The Forest Alerts may not appear during the initial setup of the forest. It may take an hour or more for
the first Alert indicators to display accurately.
Also note that the Forest Alert indicator is not available for Tenant (Office365) Forests.
Clicking on the icon will bring up dialog boxes to help in troubleshooting. You can click the Details button for more
information. This information also displays the relevant PowerShell script that is used to troubleshoot the issue.
Check the [] Fix This Issue checkbox to select the issues that you would like E2E Complete to attempt to repair for
you. Then click the Fix Issues button at the bottom.
E2E Complete 4.2 User Guide
27
The Export Scripts button allows you to optionally export and save the scripts. You can then use them as a
baseline to create custom scripts that meet your unique environmental needs.
Deleting a Forest
The Forests screen lets you delete additional (secondary) forests. When you delete a secondary forest, E2E removes
all its entries for the users and forest information, including any past migration history. Home forests cannot be
deleted on the Configuration Settings screen.
To delete a secondary forest: Click Forests in the main toolbar. Then select the secondary forest you want to delete
(in the Forest drop-down list), and click Delete Forest.
Source Forest Configuration | General Tab
To view or edit the General tab for source forest configuration: From the Forest view toolbar, select a previously
defined source Forest from the drop-down list, and then click the General tab. The General tab appears in its default
view when the Advanced checkbox option is left unmarked:
E2E Complete 4.2 User Guide
28
Or you can mark the Advanced checkbox to view additional options, although most admins simply accept the
default values for these Advanced settings:
Forest Section
The default (non-Advanced) view of this tab contains only one setting for the selected forest:

Allow users to postpone their Mailbox migration: Mark this checkbox if you want users to be able to set
their own migration blackout periods in E2E's User Portal.
The E2E_Schedulers group in Active Directory (if it exists) will override this user-postpone option.
These settings, also in the Forest section, appear only in Advanced mode:

Detect changed public folders: Mark this checkbox if you want E2E to monitor public folders in the
organization to detect forest-level additions, deletions and moves. The option is enabled by default, and we
recommend you leave it enabled. If this feature is turned off, the admin and E2E will not know when public
folders have changed after the initial sync. This would be irrelevant if you do not intend to re-sync public
folders after their initial sync, but would be necessary to permit future syncs.

Change Detection Tolerance: The spinner control lets you set a wait period for E2E's Detect feature (above,
if enabled), specifying a number of seconds for E2E to ignore changes to public folders after the time MAPI
reports the most recent sync. For example, if set to 5 seconds, any changes detected within 5 seconds of
the last sync are ignored. The default (and recommended) value is 2 seconds.

Apply mailbox blackouts to: Blackout periods can be defined in E2E's Blackout Times view (see the
Blackout Times topic for more information). The drop-down list here lets you specify one of three options
for applying blackout times to the forest:

Entire Migration (default, and recommended): All Mailbox jobs are affected by blackouts during the
entire migration.

Initial Migration: Mailbox jobs marked as "Suspend when ready to complete" are affected by
blackouts until the migration reaches 95% complete (pre-AutoSuspend). All other mailbox jobs are
affected by blackouts during the entire migration. Choose this setting when you want blackouts to
be enforced during the pre-staging process, but not for the cutover process.
E2E Complete 4.2 User Guide
29

Final Migration\Cutover: Mailbox jobs marked as "Suspend when ready to complete" are affected
by blackouts after it reaches 95% complete (post-AutoSuspend, cutover). All other mailbox jobs are
affected by blackouts during the entire migration. Choose this setting when you want all mailbox
jobs to be prevented from Cutover during the blackout period, but you want to allow “Suspend Until
Ready to complete” jobs to continue working up to the 95% complete stage (pre-staging).
Staged Migrations Section
These settings are used to specify an Exchange 2010 server and database for E2E to use for the selected forest when
an intermediate staging server is required. E2E does not support direct migration from Exchange 2003 to Exchange
2013 or Exchange 2016, or from Exchange 2007 to Exchange 2016. In these scenarios, the source is migrated first to
an intermediate Exchange 2010 staging server, and then from the staging server to the eventual Exchange target
2013 or 2016 target. The staging server can reside in either forest.
If you will require a staged migration, make sure the Enable staged migrations checkbox is marked, and specify the
Exchange Staging Server and Exchange Staging Database from the drop-down lists here. If you will not require a
staged migration, just leave the checkbox unmarked.
A staging server is not required for migration from Exchange 2003 to Office 365, but is required for a rollback migration, from Office 365 back to Exchange 2003.
Source Forest Configuration | Accounts Tab
To view or edit the Accounts tab for source forest configuration: From the Forest view toolbar, select a previously
defined source Forest from the drop-down list, and then click the Accounts tab. On this tab, all fields are displayed
whether or not the Advanced checkbox is marked.
Active Directory Section
Enter the User Name and Password for the account E2E should use for Active Directory calls, and specify the Global
Catalog for this forest.
You can mark the Auto-detect a Global Catalog checkbox to have E2E scan your environment and determine the
Global Catalog for you, or manually enter the Global Catalog into the text box. Make sure that the designated GC is
physically close to the E2E server. (If you know of another GC that is physically closer than the one found by the
Auto-detect feature, you may want to disabled Auto-detect and manually specify the nearer option.)
E2E Complete 4.2 User Guide
30
PowerShell Section
Enter the User Name and Password for the account E2E should use for PowerShell calls. This account should have
PowerShell Remoting access within the Exchange organization.
Leave the Auto-detect PowerShell Hosts checkbox marked if you want E2E to automatically find and specify the
PowerShell hosts, or unmark the checkbox if you want to manually specify the hosts in the respective text boxes:
Exchange 2010 Host, Exchange 2013 Host and Exchange 2016 Host. Make sure that the designated PS hosts are
physically close to the E2E server. (If you know of another PS Host that is physically closer than the one found by the
Auto-detect feature, you may want to disable Auto-detect and manually specify the nearer option.)
A PowerShell host must be specified here as a Fully Qualified Domain Name (FQDN). An IP address will
generate an SSL certificate error.
If you specify PowerShell hosts manually, be sure to click the Verify PowerShell Host(s) button to test connectivity
to the PowerShell host servers.
Exchange (MAPI) Section
These settings are required only when migrating public folders in cross-forest migrations where no trusts exist.
Enter the User Name, Password and Email Address for the account E2E should use for Exchange (MAPI) calls, and
select the Outlook Profile.
SMTP Section
These settings are necessary for E2E to use SMTP (Simple Mail Transfer Protocol), which is the Internet standard for
electronic mail transmission across Internet Protocol (IP) networks.
Complete the fields here, and then click the Send Test Email button to verify connectivity. When you Send Test
Email, E2E posts a status response:
If the test succeeds, click OK to continue. If the test fails, modify the above SMTP settings and test again.
E2E Complete 4.2 User Guide
31
Source Forest Configuration | Sites Tab
To view or edit the Sites tab for source forest configuration: From the Forest view toolbar, select a previously
defined source Forest from the drop-down list, and then click the Sites tab. On this tab, all fields are displayed
whether or not the Advanced checkbox is marked.
The table in this view displays a list of the AD sites that were found in your environment for the selected forest:
Most of the settings in this table can be edited:

Site Name: Displays the name of the migration site.

Site Alias: Displays the user-defined name for the migration site. Actual Site Names are often cryptic or
otherwise difficult to read, so E2E lets you assign "friendlier" shorthand names ("aliases") to identify the
sites within E2E features. This is an optional but popular feature, which can also be useful to differentiate
among duplicate or very similar Site Names—as sometimes occurs if you add external forests to your
project. To edit the alias value, just click inside the cell and the value becomes editable.

Time Zone: Displays the time zone of the migration, which E2E uses to calculate configured blackout
periods for a given site. An AD site may span several time zones, but E2E Complete associates each site with
a single time zone. To change a time zone setting: Click inside the cell to make the value editable (a small
triangle appears), then click the triangle to view a list of available options, and select the time zone you
want to assign to this forest.

MRS Proxy Server(s): Displays the Exchange Mailbox Replication Service (MRS) proxy servers that E2E has
discovered for the site. Server names are separated with commas. You can manually define the publicly
addressable names of the MRS proxy servers for the site. Manually entered server names are not
overwritten by scheduled or manual forest refreshes.
To manually define MRS Proxy Server(s): Click inside the cell to make the values editable, and enter publicly
addressable names for the site's MRS proxy servers, separating multiple names with commas.

O365 Proxy Server(s): This column applies only fora migration to Office 365 from Exchange 2003 or 2007,
which requires an on-premises Exchange 2010 FQDN to be used as a Mailbox Replication Server. Microsoft
uses this server as a connection point to pull your mailbox data into the Cloud. This server usually is the
same as for your Office 365 hybrid system, although larger distributed environments may want to use
different servers in remote sections of their networks.
This O365 Proxy Server(s) value lets you define this on an Active Directory site basis. If no proxy server is
specified, E2E uses the on-premises PowerShell host for this value; therefore, it is important that the name
be addressable over the public Internet. The cells in this column let you specify alternate addressable names
if you like, separated by commas. To add or change these values: Click inside the cell to make the values
editable, and enter publicly addressable names for the Office 365 proxy servers, separating multiple names
with commas.
Remember to click Save Forest (in the Forest toolbar above the tabs) to save any changes you make to
these settings.
E2E Complete 4.2 User Guide
32
Source Forest Configuration | Mailboxes & Public Folders Tab
To view or edit the Mailboxes & Public Folders tab for source forest configuration: From the Forest view toolbar,
select a previously defined source Forest from the drop-down list, and then click the Mailboxes & Public Folders tab.
On this tab, all options are displayed whether or not the Advanced checkbox is marked.
Mailboxes Section
Select the sites, servers and databases you want E2E to search for mailboxes in this forest to migrate. All content is
selected by default.
You can right-click in the list area to select options to expand/collapse levels of the tree.
Public Folders Section
Select the sites, servers, and databases you want E2E to search for public folders in this forest to migrate. All
content is selected by default.
You can right-click in the list area to select options to expand/collapse levels of the tree.
Source Forest Configuration | Credentials Tab
To view or edit the Credentials tab for source forest configuration: From the Forest view toolbar, select a previously
defined source Forest from the drop-down list, and then click the Credentials tab. On this tab, all options are
displayed whether or not the Advanced checkbox is marked.
The table in this tab shows the credentials that are available for E2E to use for its public folder Workers in the
selected forest. (Source and Target credentials are selected in the Worker’s settings, and the credentials defined
here make up the list of selectable creds for the Workers.)
To define a credential for this forest: Click the Add button (below the table) to open the Forest Credential screen:
E2E Complete 4.2 User Guide
33
... and enter this information:

Domain User: The Domain user (in Domain\Username format).

User Password: The password for the user

User Email: The email address of the user

Mail Profile: The name of the Outlook Profile that has been preconfigured on the Worker machine. A
Worker machine without Outlook installed cannot use credentials with Outlook Profiles. This field should
remain blank to create a credential for Workers that do not have Outlook installed.
Then click OK to create a new credentials record and dismiss the Credential screen.
You can also Edit or Delete a previously defined credential.
Target Forest Configuration | General Tab
To view or edit the General tab for target forest configuration: From the Forest view toolbar, select the previously
defined target Forest from the drop-down list, and then click the General tab. The General tab appears in its default
view when the Advanced checkbox option is left unmarked:
Or you can mark the Advanced checkbox to view additional options, although most admins simply accept the
default values for these Advanced settings:
E2E Complete 4.2 User Guide
34
Forest Section
In the default (non-Advanced) view of this tab, the Forest section contains these two settings for the selected forest:

Resource Forest: If the target Exchange environment is configured as an Exchange Resource Forest
environment, mark the Resource Forest checkbox to create a “Linked User” relationship between the
source and target account. This option applies only for Inter-Org migrations; and this checkbox appears
only when configuring the Home Forest. (For more information about resource forests, see Microsoft's
article http://technet.microsoft.com/en-us/library/aa998031.aspx and other Microsoft resources.)

Allow users to postpone their Mailbox migration: Mark this checkbox if you want users to be able to set
their own migration blackout periods in E2E's User Portal.
The E2E_Schedulers group in Active Directory (if it exists) will override this user-postpone option.
These settings, also in the Forest section, appear only in Advanced mode:

Detect changed public folders: Mark this checkbox if you want E2E to monitor public folders in the
organization to detect forest-level additions, deletions and moves. The option is enabled by default, and we
recommend you leave it enabled. If this feature is turned off, the admin and E2E will not know when public
folders have changed after the initial sync. This would be irrelevant if you do not intend to re-sync public
folders after their initial sync, but would be necessary to permit future syncs.

Change Detection Tolerance: The spinner control lets you set a wait period for E2E's Detect feature (above,
if enabled), specifying a number of seconds for E2E to ignore changes to public folders after the time MAPI
reports the most recent sync. For example, if set to 5 seconds, any changes detected within 5 seconds of
the last sync are ignored. The default (and recommended) value is 2 seconds.

Apply mailbox blackouts to: Blackout periods can be defined in E2E's Blackout Times view (see the
Blackout Times topic for more information). The drop-down list here lets you specify one of three options
for applying blackout times to the forest:

Entire Migration (default, and recommended): All Mailbox jobs are affected by blackouts during the
entire migration.

Initial Migration: Mailbox jobs marked as "Suspend when ready to complete" are affected by
blackouts until the migration reaches 95% complete (pre-AutoSuspend). All other mailbox jobs are
E2E Complete 4.2 User Guide
35
affected by blackouts during the entire migration. Choose this setting when you want blackouts to
be enforced during the pre-staging process, but not for the cutover process.

Final Migration\Cutover: Mailbox jobs marked as "Suspend when ready to complete" are affected
by blackouts after it reaches 95% complete (post-AutoSuspend, cutover). All other mailbox jobs are
affected by blackouts during the entire migration. Choose this setting when you want all mailbox
jobs to be prevented from Cutover during the blackout period, but you want to allow “Suspend Until
Ready to complete” jobs to continue working up to the 95% complete stage (pre-staging).
Staged Migrations Section
These settings are used to specify an Exchange 2010 server and database for E2E to use for the selected forest when
an intermediate staging server is required. E2E does not support direct migration from Exchange 2003 to Exchange
2013 or Exchange 2016, or from Exchange 2007 to Exchange 2016. In these scenarios, the source is migrated first to
an intermediate Exchange 2010 staging server, and then from the staging server to the eventual Exchange target
2013 or 2016 target. The staging server can reside in either forest.
If you will require a staged migration, make sure the Enable staged migrations checkbox is marked, and specify the
Exchange Staging Server and Exchange Staging Database from the drop-down lists here. If you will not require a
staged migration, just leave the checkbox unmarked.
A staging server is not required for migration from Exchange 2003 to Office 365, but is required for a rollback migration, from Office 365 back to Exchange 2003.
Target Forest Configuration | Accounts Tab
To view or edit the Accounts tab for target forest configuration: From the Forest view toolbar, select the previously
defined target Forest from the drop-down list, and then click the Accounts tab. On this tab, all fields are displayed
whether or not the Advanced checkbox is marked.
E2E Complete 4.2 User Guide
36
Active Directory Section
Enter the User Name and Password for the account E2E should use for Active Directory calls, and specify the Global
Catalog for this forest.
You can mark the Auto-detect a Global Catalog checkbox to have E2E scan your environment and determine the
Global Catalog for you, or manually enter the Global Catalog into the text box. Make sure that the designated GC is
physically close to the E2E server. (If you know of another GC that is physically closer than the one found by the
Auto-detect feature, you may want to disable Auto-detect and manually specify the nearer option.)
PowerShell Section
Enter the User Name and Password for the account E2E should use for PowerShell calls. This account should have
PowerShell Remoting access within the Exchange organization.
Leave the Auto-detect PowerShell Hosts checkbox marked if you want E2E to automatically find and specify the
PowerShell hosts, or unmark the checkbox if you want to manually specify the hosts in the respective text boxes:
Exchange 2010 Host, Exchange 2013 Host and Exchange 2016 Host. Make sure that the designated PS hosts are
physically close to the E2E server. (If you know of another PS Host that is physically closer than the one found by the
Auto-detect feature, you may want to disable Auto-detect and manually specify the nearer option.)
A PowerShell host must be specified here as a Fully Qualified Domain Name (FQDN). An IP address will
generate an SSL certificate error.
If you specify PowerShell hosts manually, be sure to click the Verify PowerShell Host(s) button to test connectivity
to the PowerShell host servers.
Exchange (MAPI) Section
These settings are required only when migrating public folders in cross-forest migrations where no trusts exist.
Enter the User Name, Password and Email Address for the account E2E should use for Exchange (MAPI) calls, and
select the Outlook Profile.
SMTP Section
These settings are necessary for E2E to use SMTP (Simple Mail Transfer Protocol), which is the Internet standard for
electronic mail transmission across Internet Protocol (IP) networks.
Complete the fields here, and then click the Send Test Email button to verify connectivity. When you Send Test
Email, E2E posts a status response:
If the test succeeds, click OK to continue. If the test fails, modify the above SMTP settings and test again.
E2E Complete 4.2 User Guide
37
Target Forest Configuration | Sites Tab
To view or edit the Sites tab for target forest configuration: From the Forest view toolbar, select the previously
defined target Forest from the drop-down list, and then click the Sites tab. On this tab, all options are displayed
whether or not the Advanced checkbox is marked.
The table in this view displays a list of the AD sites that were found in your environment for the selected forest:
Most of the settings in this table can be edited:

Site Name: Displays the name of the migration site.

Site Alias: Displays the user-defined name for the migration site. Actual Site Names are often cryptic or
otherwise difficult to read, so E2E lets you assign "friendlier" shorthand names ("aliases") to identify the
sites within E2E features. This is an optional but popular feature, which can also be useful to differentiate
among duplicate or very similar Site Names—as sometimes occurs if you add external forests to your
project. To edit the alias value, just click inside the cell and the value becomes editable.

Time Zone: Displays the time zone of the migration, which E2E uses to calculate configured blackout
periods for a given site. An AD site may span several time zones, but E2E Complete associates each site with
a single time zone. To change a time zone setting: Click inside the cell to make the value editable (a small
triangle appears), then click the triangle to view a list of available options, and select the time zone you
want to assign to this forest.

MRS Proxy Server(s): Displays the Exchange Mailbox Replication Service (MRS) proxy servers that E2E has
discovered for the site. Server names are separated with commas. You can manually define the publicly
addressable names of the MRS proxy servers for the site. Manually entered server names are not
overwritten by scheduled or manual forest refreshes. To manually define MRS Proxy Server(s): Click inside
the cell to make the values editable, and enter publicly addressable names for the site's MRS proxy servers,
separating multiple names with commas.

O365 Proxy Server(s): This column applies only fora migration to Office 365 from Exchange 2003 or 2007,
which requires an on-premises Exchange 2010 FQDN to be used as a Mailbox Replication Server. Microsoft
uses this server as a connection point to pull your mailbox data into the Cloud. This server usually is the
same as for your Office 365 hybrid system, although larger distributed environments may want to use
different servers in remote sections of their networks. This O365 Proxy Server(s) value lets you define this
on an Active Directory site basis. If no proxy server is specified, E2E uses the on-premises PowerShell host
for this value; therefore, it is important that the name be addressable over the public Internet. The cells in
this column let you specify alternate addressable names if you like, separated by commas. To add or
change these values: Click inside the cell to make the values editable, and enter publicly addressable names
for the Office 365 proxy servers, separating multiple names with commas.
E2E Complete 4.2 User Guide
38
Remember to click Save Forest (in the Forest toolbar above the tabs) to save any changes you make to
these settings.
Target Forest Configuration | Mailboxes & Public Folders Tab
To view or edit the Mailboxes & Public Folders tab for target forest configuration: From the Forest view toolbar,
select the previously defined target Forest from the drop-down list, and then click the Mailboxes & Public Folders
tab. On this tab, all options are displayed whether or not the Advanced checkbox is marked.
Mailboxes Section
Select the sites, servers and databases you want E2E to search for mailboxes in this forest to migrate. All content is
selected by default. You can right-click in the list area to select options to expand/collapse levels of the tree.
Public Folders Section
Select the sites, servers, and databases you want E2E to search for public folders in this forest to migrate. All
content is selected by default. You can right-click in the list area to select options to expand/collapse levels of the
tree.
Target Forest Configuration | Credentials Tab
To view or edit the Credentials tab for target forest configuration: From the Forest view toolbar, select the
previously defined target Forest from the drop-down list, and then click the Credentials tab. On this tab, all options
are displayed whether or not the Advanced checkbox is marked.
The table in this tab shows the credentials that are available for E2E to use for its public folder Workers in the
selected forest. (Source and Target credentials are selected in the Worker’s settings, and the credentials defined
here make up the list of selectable creds for the Workers.)
E2E Complete 4.2 User Guide
39
To define a credential for this forest: Click the Add button (below the table) to open the Forest Credential screen:
... and enter this information:

Domain User: The Domain user (in Domain\Username format).

User Password: The password for the user

User Email: The email address of the user

Mail Profile: The name of the Outlook profile that has been preconfigured on the Worker machine. A
Worker machine without Outlook installed cannot use credentials with Outlook Profiles. This field should
remain blank to create a credential for Workers that do not have Outlook installed.
Then click OK to create a new credentials record and dismiss the Credential screen.
You can also Edit or Delete a previously defined credential.
Tenant Forest (Office 365) Configuration | General Tab
To view or edit the General tab for tenant forest configuration: From the Forest view toolbar, select a previously
defined tenant Forest from the drop-down list, and then click the General tab.
The General tab appears in its default view when the Advanced checkbox option is left unmarked:
Or you can mark the Advanced checkbox to view additional options, although most admins simply accept the
default values for these Advanced settings:
E2E Complete 4.2 User Guide
40
Forest Section
In the default (non-Advanced) view of this tab, the Forest section contains these three settings for the selected
forest:

Office 365 Forest: This checkbox will be marked by default, since a tenant forest is an Office 365 forest.

Auto license O365 users: Displays only for Office 365 Exchange Online. Set this feature to optionally
activate a mailbox for an end user. Mailbox migration will fail if the user is not activated. You can also apply
an existing SharePoint and Lync/Skype for Business license by reviewing the Office 365 License section on
the E2E Settings tab. Click on your license for options.

Allow users to postpone their Mailbox migration: Mark this checkbox if you want users to be able to set
their own migration blackout periods in E2E's User Portal.
The E2E_Schedulers group in Active Directory (if it exists) will override this user-postpone option.
These settings, also in the Forest section, appear only in Advanced mode:

Detect changed public folders: Mark this checkbox if you want E2E to monitor public folders in the
organization to detect forest-level additions, deletions and moves. The option is enabled by default, and we
recommend you leave it enabled. If this feature is turned off, the admin and E2E will not know when public
folders have changed after the initial sync. This would be irrelevant if you do not intend to re-sync public
folders after their initial sync, but would be necessary to permit future syncs.

Change Detection Tolerance: The spinner control lets you set a wait period for E2E's Detect feature (above,
if enabled), specifying a number of seconds for E2E to ignore changes to public folders after the time MAPI
reports the most recent sync. For example, if set to 5 seconds, any changes detected within 5 seconds of
the last sync are ignored. The default (and recommended) value is 2 seconds.

Apply mailbox blackouts to: Blackout periods can be defined in E2E's Blackout Times view (see the
Blackout Times topic for more information). The drop-down list here lets you specify one of three options
for applying blackout times to the forest:

Entire Migration (default, and recommended): All Mailbox jobs are affected by blackouts during the
entire migration.
E2E Complete 4.2 User Guide
41

Initial Migration: Mailbox jobs marked as "Suspend when ready to complete" are affected by
blackouts until the migration reaches 95% complete (pre-AutoSuspend). All other mailbox jobs are
affected by blackouts during the entire migration. Choose this setting when you want blackouts to
be enforced during the pre-staging process, but not for the cutover process.

Final Migration\Cutover: Mailbox jobs marked as "Suspend when ready to complete" are affected
by blackouts after it reaches 95% complete (post-AutoSuspend, cutover). All other mailbox jobs are
affected by blackouts during the entire migration. Choose this setting when you want all mailbox
jobs to be prevented from Cutover during the blackout period, but you want to allow “Suspend Until
Ready to complete” jobs to continue working up to the 95% complete stage (pre-staging).
Exchange Online Section
These settings are required for E2E program access to Office 365.
Enter the User Name and Password for the account E2E should use to access Office 365.
Specify a Public Folders Migration Mode from the drop-down list. PowerShell and MAPI are the two available
methods. If the Migration Mode is not specified here, E2E will use the MAPI migration method by default.
Exchange (MAPI) Section
These settings are required only when migrating public folders in cross-forest migrations where no trusts exist.
Enter the User Name, Password and Email Address for the account E2E should use for program calls to Exchange
(MAPI), and select the Outlook Profile.
If E2E Complete is installed on a Windows 2012 server with Outlook 2010 as the MAPI provider: You
must use an Outlook Profile to connect to a secondary forest.
If the MAPI provider is Outlook 2013: Both trusted and non-trusted Exchange 2013 forests can be
reached without an Outlook Profile.
Tenant Forest (Office 365) Configuration | Sites Tab
To view or edit the Sites tab for tenant forest configuration: From the Forest view toolbar, select a previously
defined tenant Forest from the drop-down list, and then click the Sites tab. On this tab, all options are displayed
whether or not the Advanced checkbox is marked.
The table in this view displays a list of the AD sites that were found in your environment for the selected forest:
Most of the settings in this table can be edited:

Site Name: Displays the name of the migration site.

Site Alias: Displays the user-defined name for the migration site. Actual Site Names are often cryptic or
otherwise difficult to read, so E2E lets you assign "friendlier" shorthand names ("aliases") to identify the
E2E Complete 4.2 User Guide
42
sites within E2E features. This is an optional but popular feature, which can also be useful to differentiate
among duplicate or very similar Site Names—as sometimes occurs if you add external forests to your
project. To edit the alias value, just click inside the cell and the value becomes editable.

Time Zone: Displays the time zone of the migration, which E2E uses to calculate configured blackout
periods for a given site. An AD site may span several time zones, but E2E Complete associates each site with
a single time zone. To change a time zone setting: Click inside the cell to make the value editable (a small
triangle appears), then click the triangle to view a list of available options, and select the time zone you
want to assign to this forest.

MRS Proxy Server(s): Displays the Exchange Mailbox Replication Service (MRS) proxy servers that E2E has
discovered for the site. Server names are separated with commas. You can manually define the publicly
addressable names of the MRS proxy servers for the site. Manually entered server names are not
overwritten by scheduled or manual forest refreshes. To manually define MRS Proxy Server(s): Click inside
the cell to make the values editable, and enter publicly addressable names for the site's MRS proxy servers,
separating multiple names with commas.

O365 Proxy Server(s): This column applies only for a migration to Office 365 from Exchange 2003 or 2007,
which requires an on-premises Exchange 2010 FQDN to be used as a Mailbox Replication Server. Microsoft
uses this server as a connection point to pull your mailbox data into the Cloud. This server usually is the
same as for your Office 365 hybrid system, although larger distributed environments may want to use
different servers in remote sections of their networks. This O365 Proxy Server(s) value lets you define this
on an Active Directory site basis. If no proxy server is specified, E2E uses the on-premises PowerShell host
for this value; therefore, it is important that the name be addressable over the public Internet. The cells in
this column let you specify alternate addressable names if you like, separated by commas. To add or
change these values: Click inside the cell to make the values editable, and enter publicly addressable names
for the Office 365 proxy servers, separating multiple names with commas.
Remember to click Save Forest (in the Forest toolbar above the tabs) to save any changes you make to
these settings.
Tenant Forest (Office 365) Configuration | Licenses Tab
To view or edit the Licenses tab for tenant forest configuration: From the Forest view toolbar, select a previously
defined tenant Forest from the drop-down list, and then click the Licenses tab. On this tab, all options are displayed
whether or not the Advanced checkbox is marked.
This tab lets you select Office 365 license packs and related service plans for E2E to use for auto-licensing Exchange
Online mailbox migrations.
E2E Complete 4.2 User Guide
43
Tenant Forest (Office 365) Configuration | Credentials Tab
To view or edit the Credentials tab for tenant forest configuration: From the Forest view toolbar, select a previously
defined tenant Forest from the drop-down list, and then click the Credentials tab. On this tab, all options are
displayed whether or not the Advanced checkbox is marked.
The table in this tab shows the credentials that are available for E2E to use for its public folder Workers in the
selected forest. (Source and Target credentials are selected in the Worker’s settings, and the credentials defined
here make up the list of selectable creds for the Workers.)
To define a credential for this forest: Click the Add button (below the table) to open the Forest Credential screen:
... and enter this information:

Domain User: The Domain user (in Domain\Username format).

User Password: The password for the user

User Email: The email address of the user

Mail Profile: The name of the Outlook Profile that has been preconfigured on the Worker machine. A
Worker machine without Outlook installed cannot use credentials with Outlook Profiles. This field should
remain blank to create a credential for Workers that do not have Outlook installed.
Then click OK to create a new credentials record and dismiss the Credential screen.
You can also Edit or Delete a previously defined credential.
E2E Complete 4.2 User Guide
44
3. Managing E2E Workers
E2E Complete supports configuration of an AWD (Automated Workload Distribution) process for the migration of
public folders. The AWD process uses multiple workers assigned different roles (multiple computers working in
parallel) in the overall migration process, to scale public folder migration and improve throughput when migrating
larger volumes of public folders. E2E's Workers view lists all installed public folder Workers that are configured to
point to the E2E Complete SQL database. The E2E Complete server automatically becomes the local master worker
when E2E Complete is installed, but additional remote workers can be defined.
The E2E Complete Installation and Configuration Guide documents the installation of E2E public folder Workers.
To open the Workers view in the E2E Admin Portal:

Click the Workers button in E2E's main toolbar.
The E2E Workers view features a table showing the current state and processing statistics of each worker, and this
information can be sorted and filtered as needed:
Enabling/Disabling Workers
You can enable/disable the processing of public folder jobs by a worker. For example, you may want to temporarily
disable a worker to isolate any errors when troubleshooting and issue. To enable/disable the processing of public
folder jobs by a worker (beginning in the Workers view):

Click on a worker in the table to highlight its row, and then click the Enable or Disable button.
A worker can also be enabled or disabled when viewing the E2E Worker detail dialog.
E2E Complete 4.2 User Guide
45
Viewing and Editing Worker Settings
To edit (or just view) the configuration settings of any individual worker in the Workers table:

Double-click on a Worker row in the table (or select a Worker in the table and then click the Modify button)
to open the E2E Worker dialog box for the selected Worker:
In the dialog box above the tabs, you can view and edit these settings:

ID: The worker ID, an arbitrary index number for E2E.

Name: The worker name (also the worker's address).

State: The current state of the worker.

Disable or Enable: Click Disable to disable an enabled worker, or click Enable to enable a disabled worker.
In the Settings tab you can view and edit these settings:

Roles: Select the role(s) you want the worker to perform by marking/unmarking these checkbox options:

Provisioning: If marked, this worker will create the needed public folders on the target. One or more
workers can have this role. We recommend you leave this marked unless you are designating
different workers to different tasks. (You may want to create multiple workers to assign different
types of roles to different workers—for example, to designate a particular set of workers to handle
only the content sync actions.)

Content Sync: If marked, this worker will copy public folder contents. There can be one or more
workers with this role. We recommend you leave this marked unless you are designating different
workers to different tasks. (You may want to create multiple workers to assign different types of
roles to different workers—for example, to designate a particular set of workers to handle only the
content sync actions.)

Change Detection: If marked, this worker will check for changes in public folders. One or more
workers can have this role. We recommend you leave this marked unless you are designating
different workers to different tasks. (You may want to create multiple workers to assign different
types of roles to different workers—for example, to designate a particular set of workers to handle
only the content sync actions.) Note that if Change Detection is not enabled on any workers, Public
E2E Complete 4.2 User Guide
46
Folder Jobs that are created with Sync Interval will not sync again after the initial copy, since no
changes will be detected.


Reporting: If marked, this worker will collect public folder data for reporting. One or more workers
can have this role. Workers assigned this role are the workers that will run the PF Content Analysis
job. We recommend you leave this marked unless you are designating different workers to different
tasks. (You may want to create multiple workers to assign different types of roles to different
workers—for example, to designate a particular set of workers to handle only the content sync
actions.)
Source Credential and Target Credential: The credentials to use for the source and target, respectively.
Credentials are maintained in the Forest Credentials tab.
The selected credentials should not include a Mail Profile (defined in the Forest Credentials tab) if
Outlook is not installed on the Worker.

Use Default Settings: If checked, the worker will use the default Worker settings (and General settings for
Logging Level) configured in the Settings view instead of the settings on the worker detail dialog.

Use Windows Credential Manager: If checked, Worker (MAPI) credentials are cached in Windows
Credential Manager, removing the need to use the saved password that was configured for public folder
migrations.

MAPI Cache Recycle: Number of jobs after which the MAPI cache should be cleared. Larger numbers
increase performance, but may cause instability if too large. The practical limit depends on your local
environment. The default is After 20 jobs.

Logging Level: Determines level of detail in program logging for public folder migrations. Options are:

Off: No public folder messages are logged

Error: Only public folder error messages are logged

Warning: Public folder warnings and error messages are logged

Info: Public folder informational, warnings, and error messages are logged

Verbose: All public folder messages are logged including debug and trace messages

Job Polling Interval: How often the worker should poll for new jobs. We recommend you leave this at the
default is (every 2 seconds) unless this worker is configured for only the Reporting role (see next field
below).

Report Job Polling Interval: How often the worker should poll for report jobs. We recommend you leave
this at the (every 30 seconds) unless this worker is configured for only the Reporting role.

Refresh Interval: How often the worker should look for any changes to its settings in the SQL Worker table.
We recommend you leave this at its default (every 15 seconds).

Max Threads: The number of items that are processed concurrently for a public folder job. The default is 4
threads. For best performance, this setting should not be lower than the number of cores in the Worker
machine, unless the machine will share its resources with other (non-Worker) functions. The setting can be
increased to match the number of cores in a dedicated Worker machine (if greater than the default 4).
The Statistics tab is described in the next subtopic below.
Click the Close button to save any changes and close the E2E Worker dialog box (and return to the Workers table).
E2E Complete 4.2 User Guide
47
Viewing Worker Processing Statistics
To view the processing statistics for an individual worker in the Workers table:

Double-click on a Worker row in the table (or select a Worker in the table and then click the Modify button)
to open the E2E Worker dialog box for the selected Worker, and then click the Statistics tab in the E2E
Worker dialog box.
In the Statistics tab, select a Time Period from the drop-down list to define the scope of the statistics you want to
see. The Totals will display the numbers of migrated folders, items, bytes and elapsed time for the selected time
period, and the average throughput over the period.
To close the dialog box: Click the Close button.
To view aggregate statistics for all E2E Workers:

From the Workers table, click the Statistics button to open the Public Folder Statistics dialog box.
In the Statistics tab, select a Time Period from the drop-down list to define the scope of the statistics you want to
see. The Totals will display the numbers of migrated folders, items, bytes and elapsed time for the selected time
period, and the average throughput over the period.
To close the dialog box: Click the Close button.
E2E Complete 4.2 User Guide
48
Viewing the E2E Worker Application
The E2E Worker application is installed on the worker machine and lets you enable/disable the worker and view its
migration processing logs.
To open the E2E Worker application:

On the machine hosting the worker: Click the E2E Worker desktop shortcut, or right-click on the E2E icon in
the system tray and click Open.
The E2E Worker application then opens the log screen, with four buttons:

Clear Log: The displayed log will be cleared.

Save Log: A text file of the displayed log will appear and can be saved.

Enable: Enables public folder processing for the worker (if disabled). This option is also available by rightclicking on the E2E icon in the system tray and selecting Enable.

Disable: Disables public folder processing for the worker (if enabled). This option is also available by rightclicking on the E2E icon in the system tray and selecting Disable.
To view the worker's configuration settings: Right-click on the E2E icon in the system tray, and select Settings.
E2E Complete 4.2 User Guide
49
4. Managing Configuration Settings
Many E2E configuration settings can be entered, viewed and edited in the tabbed panels of the Configuration
Settings screen.
Click Settings from the main Admin Portal toolbar to open the E2E Configuration Settings screen, which contains
several tabs for different types of settings. The default view of the Settings screen shows only the tabs with settings
that are commonly used in many environments:
The default view hides the tabs that contain settings changed by only a few users from their default values, but you
can mark the [X] Advanced checkbox (in the toolbar) to show the tabs that contain these Advanced settings:
The settings on these tabs are documented separately under these topic headings:
General Tab (Advanced view only)
Activities Tab
Mailboxes Tab (Advanced view only)
Public Folders Tab
O365 Groups Tab
Workers Tab (Advanced view only)
Scripts Tab (Advanced view only)
Notifications Tab
Licenses Tab
Settings | General Tab
This tab is available only in Advanced mode. The tab appears only if the Advanced
checkbox (in the Settings toolbar) is marked.
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit.
To view or edit the General configuration settings (from any other tab on the Configuration Settings screen): Make
sure the Advanced checkbox is marked, and click the General tab.
E2E Complete 4.2 User Guide
50
These General settings let you configure options for logging and the user interface:

Logging Level: Select one of the options for logging levels within the E2E service for both mailbox and
public folder migrations:

Off: No messages are logged.

Error: Only error messages are logged.

Warning: Warnings and error messages are logged.

Info: Informational, warnings, and error messages are logged.

Verbose: All messages are logged including debug and trace messages.

Log Mailbox Job Events: If checked, mailbox job events are saved to CMTEUP_JobEvents.

Log Public Folder Job Events: If checked, public folder job events are saved to
CMTEUP_PublicFolderJobEvents.

Purge Job Events Older Than: Number of days after which job event records should be purged from the
logging database. We recommend you leave this at its default (30 days), to maintain a month's worth of
records in the database but not take up too much space in SQL. A higher setting would generate bloated
records in SQL., while a lower setting may leave too few records to be useful in the event you ever need
them for troubleshooting.

O365 PowerShell Pool: Sets the maximum number of Office 365 PowerShell sessions to establish. The
default is 1. We recommend this value be set to match the number of available Office 365 sessions for your
tenant.

O365 PowerShell Submit Pool: Sets the number of Office 365 sessions to use for PowerShell queries during
mailbox migrations. This feature improves overall migration rates by distributing the workload across
multiple Office 365 sessions running in parallel. The valid range is 1 to 100, and the default is 1. We
recommend a value based on number of available Office 365 sessions for your tenant.

User Portal Url: The URL of the E2E Complete portal.

Show Legacy Source Public Folder Servers: If checked, Exchange 2003/2007/2010 public folder servers are
displayed in the Source folder hierarchy.

Show Legacy Target Public Folder Servers: If checked, Exchange 2003/2007/public folder servers are
displayed in the Target folder hierarchy.
Exchange 2013/2016 public folders can be split across multiple servers and mailboxes and will
not show in a hierarchy. The public folder server and mailbox information will be displayed in the
“hover over” text. The above configuration options allow the Legacy public folders to be
displayed in a hierarchy.
E2E Complete 4.2 User Guide
51

Show Suspend Before Starting Checkbox: If checked, mailbox jobs can be suspended before they start.

Refresh Frequency: How often to automatically refresh E2E's UI. We recommend you leave this at its
default (7 seconds). Changing this to a lower setting poses an increased burden on system resources, while
a higher value diminishes the likelihood that any particular view is current. You can always manually refresh
the screen whenever desired.

Data I/O Timeout: How long E2E should wait for web service calls to complete before timing out. We
recommend the default setting of 15 minutes, although you may want to temporarily set this higher to
overcome a high rate of timeout errors. A lower setting will unnecessarily generate more timeout errors .

PowerShell Query Timeout: How long E2E should wait for an on-premises only PowerShell reply to a query
before concluding the query has failed, and giving up. We recommend you leave this at its default 120
minutes. A higher setting usually would not provide any benefit, since the HTTP request will have already
timed out, while a lower setting may be too short for a PowerShell query to successfully complete,
especially in a large distributed environment.

Resource Forest Permissions: Specifies which trustees to use to apply permissions during a Resource Forest
migration. The default Source Forest option stamps the permissions from the source environment onto the
target mailboxes and public folders. The Target Forest option is typically used only in a non-resource forest
scenario, so that trustees from the Target forest are used to apply permissions.
E2E Complete will always use the target AD user account for GrantSendOnBehalf permissions
regardless of this setting for this Resource Forest Permissions. Therefore all user accounts
that have been specifically provided the delegated GrantSendOnBehalf permission must be
included within the scope of directory synchronization.
Remember to click Save Settings (in the toolbar above the tabs) to save any changes you make to these
settings.
Settings | Activities Tab
This tab is available in both the default and Advanced modes. But some of the fields on this
tab appear only if the Advanced checkbox (in the Settings toolbar) is marked. The field
notes below indicate which fields appear only in the Advanced mode.
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit.
To view or edit the Activities configuration settings (from any other tab on the Configuration Settings screen): Click
the Activities tab.
E2E Complete 4.2 User Guide
52

Populate New Forest: How often to populate new forests with sites, servers, databases, groups, mailboxes,
and mailbox statistics. We recommend the default 30 seconds, which ensures that new forests are
populated relatively quickly.

Update Forest: How often to update existing forests with sites, servers, databases, groups, mailboxes, and
mailbox statistics. This is an "expensive" task (in computing/network resources), since E2E has to explicitly
query AD and Exchange for much information. We therefore recommend the default 60 minutes. A lower
setting (more frequent updates) will tax the GC specified in Forests | Accounts | Active Directory, probably
to the detriment of performance, although the performance hits will likely be less pronounced in smaller
environments (1000 or fewer users). A higher setting may be more appropriate in very large environments
where existing GCs are already taxed and the admin does not require more frequent updates.

Update Mailbox Statistics (appears only in Advanced mode): How often to update mailbox statistics. We
recommend you leave this set at its default 30 minutes. A lower setting may be better suited to an
organization that requires more frequent updates for E2E to intelligently forecast migration times (based
on mailbox size). A higher setting may be more appropriate in very large environments where existing GCs
are already taxed and the admin does not require more frequent updates.

Maintenance Tasks (appears only in Advanced mode): How often to run E2E maintenance tasks in the job
event tables, such as removing (from E2E logs) records of migration events that are older than the Purge
Job Events setting. We recommend you leave this set at the default 1440 minutes (one day), although a
lower setting (more frequent maintenance) may be appropriate if you are writing hundreds of thousands of
events per hour and want to have more control over a rolling purge window in the E2E Log database.

Submit Mailbox Jobs: How often to submit Mailbox Jobs. The default is 20 seconds, but a higher setting
(less frequent submissions) may be better for an Exchange source environment that is older or otherwise
shows performance issues, and the admin wants to stagger the number of jobs submitted.

Update Mailbox Jobs: How often to update/refresh the running Mailbox Jobs view. The default is 20
seconds, but a higher setting (less frequent updates) may be better where larger numbers of jobs are
running and the admin doesn't require frequent updates.

Resume Mailbox Jobs (appears only in Advanced mode): How often the program should look for Mailbox
Jobs that are ready to be resumed. The default is 20 seconds.

Submit Public Folder Jobs: How often to submit new public folder Jobs. The default is 20 seconds, which
ensures new mailbox migration jobs are picked up quickly, but a higher setting (less frequent submissions)
may be better for an Exchange source environment that is older or otherwise shows performance issues,
and the admin wants to stagger the number of jobs submitted.

Update Public Folder Jobs: How often to update/refresh the running public folder jobs view. The default is
20 seconds, but a higher setting (less frequent updates) may be better where larger numbers of jobs are
running and the admin doesn't require frequent updates.
E2E Complete 4.2 User Guide
53

PF Change Detection (appears only in Advanced mode): How often to check for public folder changes. We
recommend you accept the default 30 seconds, although a higher value (less frequent checks) may be more
appropriate if the public folders environment does not have many changes and the data is relatively static
(in the source).

PF Content Analysis (appears only in Advanced mode): Determines how often E2E should check the queue
of pending public folders content analysis jobs. We recommend you accept the default 120 seconds.
Remember to click Save Settings (in the toolbar above the tabs) to save any changes you make to these
settings.
Settings | Mailboxes Tab
This tab is available only in Advanced mode. The tab appears only if the Advanced
checkbox (in the Settings toolbar) is marked.
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit.
To view or edit the Mailboxes configuration settings (from any other tab on the Configuration Settings screen):
Make sure the Advanced checkbox is marked, and click the Mailboxes tab.

Enable Whiteout: If checked, all activities except for mailbox migrations activities are suppressed. This
feature is intended for use during times when active migration is taking place in earnest. This can
significantly improve performance of mailbox migrations during busy times, easing the burden of the
installed E2E machine as well as the Exchange servers.
Be sure to disable this Whiteout option when the period of focused migrations ends, so that E2E
can resume its other background processing.

Enable Mailbox Job Adoption: If checked, enables E2E Complete to find and show mailbox migrations
started outside of E2E Complete. Select this only if migration processes may have been started outside of
the E2E complete environment (not a common occurrence).
E2E Complete 4.2 User Guide
54

Enable Auto Scheduling: This checkbox enables/disables E2E's auto-scheduling feature, which tells E2E to
schedule mailbox migration upon certain conditions being met, as specified by the AD Trigger Field and AD
Status Field:

AD Trigger Field: The AD property used to submit mailboxes during auto-scheduling. For example,
extensionAttribute13.

AD Status Field: The AD property used to store job status for auto-scheduled mailbox migrations.

Apply Default Email Address Policy: If checked, the default email address policy will be applied to the
target mail users before the mailbox is submitted. This is the equivalent of the PowerShell cmdlet string:
Set-MailUser -EmailAddressPolicyEnabled:$true

Restart Queued Office365 Migrations After: If checked, Office 365 mailbox jobs that are stuck in a Queued
state are automatically canceled and resubmitted. The default to restart jobs stuck in a Queued state is
every 20 minutes.

On-Prem Mailbox Query Size: The number of on-premises mailboxes to query at a time for statistics, etc.
The default is 1,000 mailboxes.

Office365 Mailbox Query Size: The number of Office 365 mailboxes to query at time for statistics, etc. The
default is 100 mailboxes.

Office365 Licensing Pause: How long to wait after licensing an Office 365 mailbox before submitting that
mailbox for migration. The default is 30 seconds.

Initial Notification Pause (Exchange 2003): How long to wait after sending the initial notification before
submitting a mailbox for migration. The default is 30 seconds.

Max Submits: The maximum number of requests (per Exchange database) to submit for migration. This
includes jobs that resumed before reaching 95% complete. The default is 50 submissions.

Max Resumes: The maximum number of requests (per Exchange database) to resume for completion. This
only includes jobs that are resumed after reaching 95% complete. The default is 50 resumes.

Batch Submits: The number of requests (per Exchange database) to submit for migration at a time. This
includes jobs that resumed before reaching 95% complete. The default is 10 submissions.

Batch Resumes: The number of requests (per Exchange database) to resume for completion at a time. This
only includes jobs that are resumed after reaching 95% complete. The default is 10 resumes.

Batch Updates: The number of requests (per Exchange database) to update (Get-MoveRequestStatistics) at
a time. The default is 10 updates.

Staged Migration Retries: How many times to re-submit a mailbox for staged migration and how long to
wait before re-submitting. The default is 10 times re-submitted every 120 seconds.

Mailbox Permissions Retries: How many times to retry migrating mailbox permissions and how long to wait
before retrying. The default is 10 times retried every 120 seconds.

Log User Migrations: If checked, logging user migrations is enabled and the Output Folder can be
configured.

Output Folder: The folder where the log user migration reports are saved.
Remember to click Save Settings (in the toolbar above the tabs) to save any changes you make to these
settings.
E2E Complete 4.2 User Guide
55
Settings | Public Folders Tab
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit. On this tab, all options
are displayed whether or not the Advanced checkbox is marked.
To view or edit the Public Folders configuration settings (from any other tab on the Configuration Settings screen):
Click the Public Folders tab.


Synchronization: Select one of the options from the drop-down list.

One Way: Synchronize public folders from source to target. Only the Source to Target options can
be selected. This means that changes made in the target will not be made in the source. Choose this
when you are pre-staging Public folders in your Source environment to your Target environment,
and there is no expectation that there will be any production changes made in the Target that need
to be copied back to the Source.

Bi-Directional: Synchronize public folders in both directions, from source to target and target to
source. The Target to Source options are enabled to allow configuration synchronization in both
directions. Choose this when you expect production changes to occur in both the Source AND the
Target during the migration project. If you choose Bi-Directional, carefully choose your Conflict
Resolution settings (below). This setting means that changes made in the target could potentially
override items in the Source, as determined by the Conflict Resolution settings.
Conflict Resolution: This setting tells E2E how to resolve public folder migration conflicts (when a source
public folder already exists in the target). These conflict-resolution rules are evaluated at the document
level, per folder. We suggest the Skip option if you are unsure.

Skip: E2E will just skip the PF, and do nothing. The source and target PFs will both remain
unchanged.

OverWrite: The source PF contents will overwrite the corresponding target PF contents.

Rename: In a one-way migration, if a target document exists with the same name or subject that
was not placed there by a migration, the target document is renamed by appending or prepending
some string (the Rename Label) to the original target PF name, as specified below. If a target copy
of the document exists from a previous migration, the documents follow the LastModified rule. In
bi-directional migrations, both source and target documents are renamed and migrated in both
directions. If you select Rename as the Conflict Resolution method:

Rename Format: Valid options are Append or Prepend.

Rename Label: The string that E2E should append or prepend to the original target PF name.
E2E Complete 4.2 User Guide
56

Last Modified: The source and target documents are evaluated and then migrated based on which
document is more current.

Rationalization Pool Size: The maximum number of PowerShell sessions to dedicate to public folder
rationalization. The default is 5 sessions.

Target PF Mailbox Quota Percentage: Spinner control to set the percentage of available quota that should
remain in the target mailbox after the migration. Default is 10 percent. This setting ensures that a new PF
migration job will maintain at least the configured percentage of free space based on the existing public
folder mailbox quota. For example, if the defaults are left at 10% then a new PF migration job will not be
scheduled if the result would use at least 90% of the configured quota on the PF mailbox.
Source To Target Section



Folders: Mark and unmark checkboxes to specify which items should be synchronized to the target:

Adds: If checked, new folders in the source are added to the target.

Deletes: If checked, deleted folders in the source will cause corresponding folders in the target to be
deleted during the sync cycle. By default, this is unchecked, to prevent subsequent deletions in the
source from deleting the corresponding folder(s) in the target during the next synchronization cycle.

Renames: If checked, renamed folders in the source are renamed in the target.

Moves: If checked, moved folders in the source are moved in the target.
Items: Mark and unmark checkboxes to specify which items should be synchronized to the target:

Adds: If checked, new folder content in the source is added to the target.

Deletes: If checked, deleted folder content in the source is moved to the Binary Tree Recycle Bin in
the target.

Renames: If checked, renamed items in the source are renamed in the target.
Permissions: Select an option from the drop-down list, and mark/unmark checkboxes to specify how
permissions should be copied to the target (if at all):


Drop-down list options:

Disabled: Folder permissions will never be copied.

Once (default): Folder Permissions will only be copied with the initial sync, any changes after
that will not be copied.

Always: Folder permissions will be copied each time the folder is synchronized.

Anonymous: If checked, “anonymous” user folder permissions are migrated to the target folder.

Default: If checked, “default” user folder permissions are migrated to the target folder.
Mail Enablement: Select an option from the drop-down list, and mark/unmark checkboxes to specify how
mail-enablement should be copied to the target (if at all):

Drop-down list options:

Disabled: Mail-enabled folders in the source will not be mail-enabled in the target.

Once: Mail-enabled folders will be mail-enabled in the target during the initial sync, any
changes after that will not be copied.

Always (default): Mail-enabled folders in the source will be mail-enabled each time the
folder is synchronized.
E2E Complete 4.2 User Guide
57

Email Addresses: If checked, email addresses are copied to the target folder.

Forwarding Address: If checked, the source folder’s forwarding address is copied to the target
folder.

Send/Receive As: If checked, send-as folder permissions on the source are migrated to the target
folder.

Send On Behalf: If checked, send-on-behalf folder permissions on the source are migrated to the
target folder.
Target To Source Section



Folders: Mark and unmark checkboxes to specify which items should be synchronized to the source:

Adds: If checked, new folders in the target are added to the source.

Deletes: If checked, deleted folders in the target are moved to the Binary Tree Recycle Bin in the
source.

Renames: If checked, renamed folders in the target are renamed in the source.

Moves: If checked, moved folders in the target are moved in the source.
Items: Mark and unmark checkboxes to specify which items should be synchronized to the source:

Adds: If checked, new folder content in the target is added to the source.

Deletes: If checked, deleted folder content in the target is moved to the Binary Tree Recycle Bin in
the source.

Renames: If checked, renamed items in the target are renamed in the source.
Permissions: Select an option from the drop-down list, and mark and unmark checkboxes to specify how
permissions should be copied to the source (if at all):

Drop-down list options:

Disabled: Folder permissions will never be copied.

Once (default): Folder permissions will only be copied with the initial sync; any changes after
that will not be copied.

Always: Folder permissions will be copied each time the folder is synchronized.

Anonymous: If checked, “anonymous” user folder permissions are migrated to the source folder.

Default: If checked, “default” user folder permissions are migrated to the source folder.
Enabling target-to-source synchronization of permissions may cause changes to your source
environment or may have other unintended side effects.

Mail Enablement: Select an option from the drop-down list, and mark and unmark checkboxes to specify
how mail-enablement should be copied to the source (if at all):

Drop-down list options:

Disabled: Mail-enabled folders in the target will not be mail-enabled in the source.

Once: Mail-enabled folders will be mail-enabled in the source during the initial sync; any
changes after that will not be copied.
E2E Complete 4.2 User Guide
58

Always (default): Mail-enabled folders in the target will be mail-enabled each time the folder
is synchronized.

Email Addresses: If checked, email addresses are copied to the source folder.

Forwarding Address: If checked, the target folder’s forwarding address is copied to the source
folder.

Send/Receive As: If checked, send-as folder permissions on the target are migrated to the source
folder.

Send On Behalf: If checked, send-on-behalf folder permissions on the target are migrated to the
source folder.
Enabling target-to-source mail synchronization may cause changes to your source environment
or may have other unintended side effects.
Remember to click Save Settings (in the toolbar above the tabs) to save any changes you make to these
settings.
Notes About Public Folder Permissions
Exchange Permissions:

All roles and rights are supported, e.g. Owner, CreateItems, FolderVisible, etc.

On-Prem and Office 365 are supported.
Send-As Permissions:

Only applicable to mail-enabled folders.

Allow\Deny is supported for On-Prem.

Only Allow is supported for Office 365.
Receive-As Permissions:

Only applicable to mail-enabled folders.

Allow\Deny is supported for On-Prem.

Not supported for Office 365.
Send-On Behalf Permissions:

Only applicable to mail-enabled folders.

On-Prem and Office 365 are supported.
Resource Forests:

Target RFPermissionAuthority is supported for On-Prem and Office 365 for all folder permissions shown
above.

Source RFPermissionAuthority is supported for Send-As and Receive-As permissions but is not supported
for Send-On-Behalf and Exchange permissions.
E2E Complete 4.2 User Guide
59
Trustee Cross-Reference: When locating a target trustee, the following properties from the source trustee are used
as a cross-reference. These are the same properties used for mailbox permissions.

Mailbox GUID

E-Mail

Primary SMTP

Common Name

SAM Account Name
Settings | O365 Groups Tab
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit. On this tab, all options
are displayed whether or not the Advanced checkbox is marked.
To view or edit the O365 Groups configuration settings (from any other tab on the Configuration Settings screen):
Click the O365 Groups tab.

Conflict Resolution: This setting tells E2E how to resolve Office 365 migration conflicts (when matching
content already exists in the target). We suggest the Skip option if you are unsure.

Skip: E2E will just skip the public folder (PF) and do nothing. The source and target will both remain
unchanged.

OverWrite: The source PF contents will overwrite the corresponding target contents.

Rename: In a one-way migration, if a target document exists with the same name or subject that
was not placed there by a migration, the target document is renamed by appending or prepending
some string (the Rename Label) to the original target PF name, as specified below. If a target copy
of the document exists from a previous migration, the documents follow the LastModified rule. In
bi-directional migrations, both source and target documents are renamed and migrated in both
directions. If you select Rename as the Conflict Resolution method:


Rename Format: Valid options are Append or Prepend.

Rename Label: The string that E2E should append or prepend to the original target PF name.
Last Modified: The source and target documents are evaluated and then migrated based on which
document is more current.
E2E Complete 4.2 User Guide
60
Settings | Workers Tab
This tab is available only in Advanced mode. The tab appears only if the Advanced
checkbox (in the Settings toolbar) is marked.
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit.
To view or edit the Workers configuration settings (from any other tab on the Configuration Settings screen): Make
sure the Advanced checkbox is marked, and click the Workers tab.

Use Windows Credential Manager: If checked, Worker (MAPI) credentials are cached in Windows
Credential Manager.

Sync Job Polling Interval: How often Workers should poll for new sync jobs. Default is every 2 seconds.

Reporting Job Polling Interval: How often Workers should poll for new reporting jobs. Default is 30
seconds.

Refresh Interval: How often Workers should refresh their status. Default is every 15 seconds.

Max Threads: Number of items that are processed concurrently for a public folder job. Default is 4 threads.

MAPI Cache Recycle: After how many jobs should the MAPI cache be cleared. A larger number will increase
performance, but may cause instability if too large. Default is After 20 jobs.

Status Text Limit: Maximum number of status text displayed in the Worker UI. Default is 5,000 lines.

Max Sync Jobs: Maximum number of sync jobs that should be assigned to each worker. Default is 5 jobs.

Max Reporting Jobs: Maximum number of reporting jobs that should be assigned to each worker at a time.
Default is 5 jobs.

Max Change Detection Jobs: Maximum number of change detection jobs that should be assigned to each
worker at a time. Default is 5 jobs.
Remember to click Save Settings (in the toolbar above the tabs) to save any changes you make to these
settings.
E2E Complete 4.2 User Guide
61
Settings | Scripts Tab
This tab is available only in Advanced mode. The tab appears only if the Advanced
checkbox (in the Settings toolbar) is marked.
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit.
To view or edit the Scripts configuration settings (from any other tab on the Configuration Settings screen): Make
sure the Advanced checkbox is marked, and click the Scripts tab.

Enable External Scripts: If checked, external scripts are enabled and the following options are available:

Scripts Folder: The scripts folder location (e.g. c:\contoso\scripts\ps\ )

Enable Prepare Move Request Script: If checked, enables external CrossForestPrep (to execute PrepareMoveRequest.ps1). The name of the prepare move request script can be configured (e.g., PrepareMoveRequest.ps1).

Enable Prepare Move Request Retry On Failure: If checked, enables retry behavior in cross-forest
preparation, instead of failure.

Schedule Migration Script: Name of the script for scheduled migrations, e.g., ConfirmScheduleMigration.ps1.

Begin Migration Script: Name of the script for started migrations, e.g., Confirm-BeginMigration.ps1.

End Migration Script: Name of the script for completed migrations, e.g., Confirm-EndMigration.ps1.

Failed Migration Script: Name of the script for failed migrations, e.g., Confirm-FailedMigration.ps1.
Remember to click Save Settings (in the toolbar above the tabs) to save any changes you make to these
settings.
Settings | Notifications Tab
E2E Complete helps facilitate sending notification emails to end users, to inform them of the status of their
migration as it progresses through different stages. The program can use email notification templates to generate
"form letters" to end users, with variables that E2E will fill with information such as the recipient's email address,
any cc recipients, the message Subject, and so forth. Other template attributes let you control the message format
and event triggers and so forth. Notifications can be configured in four languages, English, French, German and
Spanish, and languages in the source Exchange environment. By default, the message sent to an end user is
E2E Complete 4.2 User Guide
62
matched to the Culture value present on their mailbox object. If a value cannot be determined, English is used as the
default language. Users can change their notification language by changing the preference on the End User Portal
page.
The Notification templates are configured in this Notifications tab, and in a dialog box accessible from this tab. On
this tab, all options are displayed whether or not the Advanced checkbox is marked.
To view or edit the Notifications configuration settings (from any other tab on the Configuration Settings screen):
Click the Notifications tab.
The table displays a list of available notification templates together with these attributes:

Enabled: Displays whether the template is enabled or disabled by the administrator. By default, Scheduled
notification templates are always enabled.

Name: A descriptive identifying name to distinguish each template from the others in the list.

Event Trigger: Displays the status of the template, such as Scheduled or Completed.

Language: The language of the template. A full list of standard Language/Culture ID mappings is available in
this KnowledgeBase article.

Migration Type: The migration type of the template.

Format: Displays the type of media included in the template that goes out to users, such as Email or SMS.

To: The recipient of the notification.

CC: Any "carbon copy" (CC) recipient(s) of the notification.

Subject: The message Subject of this notification.
E2E Complete ships with five standard notification templates (Scheduled, Started, Completed, Error, and Migration
automatically suspended). You can customize these with the Edit Template feature.
For any selected template (selected row in the table), the buttons across the bottom of the table let you Edit
Template or Copy Template(s) or Delete Template(s). You can also Add Template.
The Add Template and Edit Template buttons open E2E's Notification Template dialog box:
E2E Complete 4.2 User Guide
63
Enter or edit the settings in this dialog box:

Name: The name of the template, as it will appear in the Notifications table and other E2E features.

Enabled (checkbox): Mark or unmark to make this template available (or unavailable) for E2E to run.

Language (drop-down list): Specify the language for this template. Options are: English, French, German,
Spanish, and any additional languages collected from the source mailbox properties.

Send Notifications During: Select an option from the drop-down list to specify the portion of the migration
to which this notification applies. Options are: Entire Migration, Initial Migration, and Final
Migration\Cutover.
Migrations scheduled using the Suspend when ready to complete option can have notifications
defined for the Entire Migration, the Initial Migration or the Final Migration/Cutover. If a
migration is scheduled without the Suspend when ready to complete option, the notifications
will apply to the Entire Migration.

Migration Type: Specify whether this notification is for a Mailbox or Public Folder migration.

Message Format: Specify whether this notification should be formatted as Email (sent as HTML messages)
or SMS (sent as plain text messages). Switching from Email to SMS will erase any body text that may have
already been entered.

Event Trigger: Select one of the two options to specify when this notification will be sent:


Status: If you select Status, then also specify (from the drop-down list) the condition that will trigger
this notification:

Scheduled: Notification is sent to the user when the mailbox’s migration schedule is set.

Started: Notification is sent to the user when the migration begins.

Completed: Notification is sent to the user when the migration completes.

Error: Notification is sent to the user when the migration halts or errors.
Date: Use the controls here to specify a time condition that will trigger sending the emails
generated from this template. You can specify a certain number of hours or days before the start or
completion of the migration:
E2E Complete 4.2 User Guide
64

[spinner control]: The number (of hours or days).

[drop-down list]: Indicate whether the number specifies Days Before or Hours Before.

[drop-down list]: Indicate whether the trigger is relative to the start (Do Not Start Before) or
end (Do Not Complete Before) of the migration.

To: Specify the message recipient(s), either as an SMTP address, or as the variable {User} or {Administrator}
(including the curly brackets). You can specify multiple values here, separated by commas or semicolons or
spaces.

CC: Specify anyone who should receive a copy of this notification, either as an SMTP address, or as the
variable {User} or {Administrator} (including the curly brackets). You can specify multiple values here,
separated by commas or semicolons or spaces.

Subject: Type the Subject of the email.

Body: The body contents of the email. This will be some combination of template text and one or more
variables, as shown in the example below. If the Message Format (above) is set to Email, E2E provides a
rich-text editing bar (also shown in this example) that lets you further customize the appearance of the
body text.
Within the template Body you can use these variables as you compose the text of your message:
Macro (Variable)
Description
{FullName}
{Title}
{FirstName}
{LastName }
{UserPortalLink}
{SAMAccountName}
{ExpectedDuration}
{ScheduledStart}
{ScheduledEnd}
User’s First and Last Name
User’s Title
User’s First Name
User’s Last Name
Link to user portal page
User’s Alias
Expected duration of migration
Scheduled time to start
Scheduled time to end
Do not complete migr before time
{DoNotCompleteBefore} Do not start migration before time
{DoNotStartBefore}
Time migration started
{ActualStart}
Time migration ended
{ActualEnd}
Number of errors during migration
{ErrorCount}
Error message during migration
{ErrorMessage}
E2E Complete 4.2 User Guide
Example
Scott Pepper
Sergeant
Scott
Pepper
scott.pepper
01:04:38.4379257
Tuesday, April 12, 2016 3:30:44 PM (GMT)
Tuesday, April 12, 2016 4:35:48 PM (GMT)
Tuesday, April 12, 2016 3:30:44 PM (GMT)
Tuesday, April 12, 2016 4:35:48 PM (GMT)
Tuesday, April 12, 2016 3:30:44 PM
Tuesday, April 12, 2016 4:35:48 PM
1
Mailbox is full
65
Remember to click the OK button at the bottom of this dialog box to save these notification template
settings. And remember to click Save Settings (in the toolbar above the tabs) to save any changes you
have made to other settings in the Notifications tab.
Settings | Licenses Tab
The Licenses tab is where E2E license keys are registered to the program. On this tab, all options are displayed
whether or not the Advanced checkbox is marked.
To view or edit Configuration Settings (any tab): From the Admin Portal main toolbar, click Settings to open the
Configuration Settings screen. Then click the tab for the settings you want to view or edit.
To view or edit the Licenses configuration settings (from any other tab on the Configuration Settings screen): Click
the Licenses tab.
You can register a license by either of two methods:

Use the Browse... button to find and select the license file from some location on your local computer; or

Copy and paste the license key into the Paste License Key text box, and then click the Add License button.
Remember to click Save Settings (in the toolbar above the tabs) to save any changes you make to these
settings.
E2E Complete 4.2 User Guide
66
5. Mailboxes View
Working in the Mailboxes View
When you launch the Admin Portal for the first time, the Mailboxes view displays as the default view. This view
consists of a list of mailboxes from various Exchange sites and servers. You may recall that while installing, you had
specified the domain name and when the tool launched, it picked up all the mailboxes from all the Exchange server
sites (2003 as well as 2007, 2010, 2013, and 2016) in the specified forest.
This view is considered the most important view as this is where the administrators spend most of their time. From
here, they can select mailboxes that can be added to the migration queue. This view also provides the administrator
all the information that they can possibly need in order to select data for migration.
Before we begin to migrate mailboxes using E2E Complete, let's get familiar with the interface components and how
they are used to view migration data. Please note that even though the Mailboxes view is being used to understand
how to work within a view, the primary format of the data view remains the same for all the other buttons/tabs with
few exceptions, as you will see as we proceed.
Adding and Removing Columns
User data is stored in various attributes in AD. Some of the attributes are displayed by default, such as Site Name,
Source Server, Mailbox Database, and Email Address as shown below. Additional attributes can be added to the list
as desired.
To change the displayed attributes (columns), right-click in the list of user mailboxes:
... and then select Choose columns, to open this dialog box:
E2E Complete 4.2 User Guide
67
This dialog box shows a complete list of attributes. You can select attributes that are not currently displayed, or
deselect attributes to hide them.
Rearranging Columns
You can also change the order in which the attributes are displayed in the view simply by clicking a column,
dragging, and then dropping it where you wish to place it. For example, you can make the First Name column the
first column by clicking it, dragging, and then dropping it in the space before the Site Name column or over the
column.
Group Membership
You can choose a group by selecting the Group Membership option under Advanced Filter. The list of available
groups displays. You may quickly find a group by typing in the first few characters to filter the list. Selecting a group
will limit the display to users possessing that membership.
Sorting Data
By default, the mailboxes are not sorted on any specific column. However, you can sort them by any column that
you want.
To sort data by their First Name, simply click the First Name column header. When the data is sorted, an inverted
triangle appears above the column name. Please notice that the data is now sorted in ascending order in the Data
Panel:
E2E Complete 4.2 User Guide
68
To reverse the sort order, just click the same column header again:
To change sorting, click on a different column header.
To do a hierarchical sort, sort the data on one column, then hold down the Shift key and click the next column by
which you want data sorted. To remove sorting from one of the columns, hold down the Shift key and click the
triangle.
Filtering Data
The filter icon
next to each column header allows you quickly filter any column in view.
Perform the following steps to select the filter criteria.
1.
Click on the filter icon
2.
Click on the down arrows in each field to select the filter criteria.
3.
Click Filter to begin filtering.
4.
Click Clear Filter to clear the filter.
E2E Complete 4.2 User Guide
next to the column header. The filter window appears:
69
Data Panel
The Quick Filters and Quick Search fields display in the Data Panel section when you select the Mailboxes button.
This panel remains the same for all the views, except in some views additional components are available.
Quick Filters options:

Forest: The forest of the mailboxes you want migrated. This is also used to view user mailboxes residing on
Exchange Online.

Site: Displays the list of AD sites.

All Sites: Displays the list of all AD sites.

Exchange Version: The version of the mailboxes you want migrated.

All Versions: Displays a list of all versions.

Advanced Filter (a Forest must be selected before using an Advanced Filter on the Mailbox Jobs view):

Group Membership: Select a group to limit the display to users possessing that membership. Also
provides the functionality to import from a text file to facilitate search for specific users within the
environment.

Accounts: Provides the functionality to import users from a text file to facilitate search for specific
users within the environment.
Quick Search options:

Search: The search engine lets you perform a quick search against any of the mailboxes in the Mailboxes
view or from the Mailbox Jobs view. Any columns displayed in the current view are valid search terms. This
field will return partial matches of search terms.

Refresh: Press Ctrl-Refresh to force a full refresh of the data.

Auto Refresh: If the check box is selected, the data is automatically refreshed.

Export: This function lets you export data to .csv, .html, .txt, and .xml files from either the Mailboxes view
or from the Mailbox Jobs view.
Importing migrated users from a CSV text file
E2E Complete lets you import from a text file to facilitate searches for specific users within the environment. This
CSV import feature is also available in the Group Membership feature from the E2E Complete Admin User Interface.
E2E Complete 4.2 User Guide
70
To import users from a text file:
1.
Click Mailboxes in the main toolbar.
2.
Click the Accounts button to launch the Filter accounts window:
3.
Select the users you want to search on and schedule for migration, and then click the Import button. The
Import account list window displays.
4.
Read the content and click OK. The navigation window displays.
\
E2E Complete 4.2 User Guide
71
5.
Select the user list file and click Open. The Import Account Results window will appear displaying how many
users matched. Click OK to close the window. Click Export Results to save a CSV file of the match results.
6.
The Filter accounts menu displays again so that you can select additional users.
7.
When you have completed the import process, click OK. The following is an example of the input text file
format.
8.
In the Mailboxes view, the selection of users has been filtered down to the specific users from the user list file
and the manual additions selected in the filter accounts menu.
Exporting data to a CSV file
You can export data to a CSV file from either the Mailboxes view or from the Mailbox Jobs view. To export data to a
CSV file:
1.
Click either Mailboxes or Mailbox Jobs in the main toolbar.
2.
Click the drop-down arrow next to the Export button.
E2E Complete 4.2 User Guide
72
3.
If you only want to export certain records to the CSV file, highlight the records you want to export and then
choose selected records from the drop-down list.
4.
If you want to export all records to a CSV file, choose all records from the drop-down list.
5.
Select a location for the file to be saved, and then click the Save button.
Here’s an example of exported data from the Mailboxes view:
Changing Mailbox Properties
You can change certain properties of mailboxes by using the right-click menu. To change the properties of
mailboxes:
1.
Click either Mailboxes or Mailbox Jobs in the main toolbar.
2.
Select the mailboxes you wish to change.
3.
Right-click on the selected mailboxes. A context menu displays.
4.
Click Properties. A dialog window appears allowing you to change the following properties:
E2E Complete 4.2 User Guide
73

Mailboxes
o
o
o

Mailbox Jobs
o
o
o
o
o
o
o
5.
Migration Group
Blackout Profile
Priority
Migration Queue
Blackout Profile
Priority
Do Not Start Before
Do Not Complete Before
Bad Item Limit
Large Item Limit
Check the properties you want to change, change the values and click OK.
An existing Blackout Profile property can be added only to a mailbox or mailbox job. The Blackout
Profile must be created first (see Blackout Times View for information about this feature). The
default (None) Blackout Profile is already applicable to all mailboxes and mailbox jobs.
Adding Mailboxes to the Mailbox Jobs
Once you have configured settings, and reviewed the data you need to migrate, you are ready to start the migration
process. The first step is to add the mailboxes from Mailboxes to the Mailbox Jobs.
But before adding Mailboxes to Mailbox Jobs, run this command to verify the validity of the target:
Get-MailboxDatabase | ft Name,IsExcludedFromProvisioning,IsSuspendedFromProvisioning
If either returns True, E2E will be unable to use it as a target. In that case, run this command to enable the target:
Set-MailboxDatabase MDB01 -IsExcludedFromProvisioning $FALSE
When you have verified the target, this procedure will add mailboxes to the Mailbox Jobs:
1.
Click on Mailboxes in the main toolbar.
2.
Select the mailboxes from a site that you wish to migrate. You may consider employing groups to view
mailboxes based on either their Mailboxes Database name or the Source Server name or you can use the
Show Filter tool.
3.
o
To select multiple mailboxes from non-adjacent regions, click the first item in the range; hold down
the Ctrl key as you click other items in the range.
o
To select multiple mailboxes from adjacent regions, click the first desired item in the range; hold
down the Shift key as you click the last item in the range.
Right-click on the selected mailboxes, and select Add selection to queue from this context menu:
E2E Complete 4.2 User Guide
74
If these mailboxes are scheduled to migrate at a future time, such as the start of a weekend, mailboxes will
be migrated based on priority group when the future time begins. The smallest mailboxes within a priority
group are migrated first.
If these mailboxes are scheduled to migrate immediately, the migration will begin as soon as the mailboxes
are the highest priority in the migration queue, unless another mailbox is already being migrated (in which
case this new migration will begin when the in-progress migration completes).
The Add mailboxes to migration queue dialog box displays:
The options in this dialog box:

Bad item limit: You can assign a limit to the number of bad items that are acceptable for the
migration to keep running. A bad item is one that cannot be successfully migrated. The default
number is zero and means no bad items will be skipped. The valid input range is from 0 through
2147483647. If a value above 50 is entered for either the Bad Item Limit, E2E Complete will
automatically pass a True value for the AcceptLargeDataLoss parameter for the New-MoveRequest.
E2E Complete 4.2 User Guide
75







Ignore Rule Limit Errors (only applies when using Exchange 2003 as a destination): This box only
applies when using Exchange 2003 as a destination. Exchange 2003 has a lower limit on the
maximum size of mailbox rules. Check this box to ignore errors caused by moving data from an
Exchange 2010 database to Exchange 2003.
Large item limit (only displays when migrating to Office 365 or Exchange 2013 or 2016 on-premise.):
You can assign a limit to the number of large items that are acceptable for the migration to keep
running. We recommend setting this limit to allow mail items larger than 25 MB to be migrated. If a
value above 50 is entered for the Large Item Limit, E2E Complete will automatically pass a True value
for the AcceptLargeDataLoss parameter for the New-MoveRequest.
Priority: The priority of the migration. The lower the number equals the higher priority. The Priority
setting is secondary to the Do not start before and Do not complete before values. Valid values are
1-100 with 10 set as the default.
Do not start before: You can select date and time by clicking on the calendar icon. Setting this value
instructs the migration engine to NOT submit mailboxes to the destination Exchange server until
after the specified date and time. Use this to manage when a group of users will be migrated.
Do not complete before: Setting this value instructs the migration engine to NOT complete the
migration (cutover) before the specified date and time.
Suspend when ready to complete: Check this box to suspend the item when ready to complete
(although this feature is not supported for Exchange 2003). This allows administrators to migrate
mailboxes 95% of the way, and then complete the final cutover at a later time which can be set by
the Do not complete before option or manually triggered by the administrator. This allows you to
pre-stage the mailboxes, and then cut them over all at the same time. Note that if you override a
blackout and scheduled mailbox migration with the Migrate Now option, the migration will
complete without suspending the item.
Apply blackout profile: Dropdown list lets you select a Blackout profile to apply to this migration
job. The list of available profiles is drawn from the CMTEUP_Blackout table, and also offers a None
option (the default). The selection here will supersede any existing blackout values set on the
mailboxes subject to the migration action.
A Blackout Profile must be created before it can be applied (see the Blackout Times View
section below for information about this feature). The default (None) Blackout Profile is
already applicable to all mailboxes and mailbox jobs.

Target Delivery Domain: Displays the name of the domain to which the mailboxes are being
migrated. This option is enabled only in cross-forest (inter-org) migrations.

Auto License (appears only for Office 365 Exchange Online): Set this feature to optionally activate a
mailbox for an end user. Mailbox migration will fail if the user is not activated. You can also apply an
existing SharePoint and Lync/Skype for Business license by reviewing the Office 365 License section
on the E2E Settings tab. Click on your license for options.
Override usage Location (appears only for Office 365 Exchange Online): Check this box and enter a
different location to override the default usage location set in the Tenant Forest General Settings.
Auto select databases for: Check the boxes to automatically rotate among Exchange 2010, Exchange
2013, and Exchange 2016 databases. (If you want to exclude a specific database, use this PowerShell
command: Set-MailboxDatabase <NAME> - IsExcludedFromProvisioning $TRUE)
Select target database(s): Displays a list of destination sites, servers, databases, and Exchange
servers. (Databases that are excluded from provisioning are grayed out and cannot be selected.)



When the settings appear as you want them, click Add to Migration Queue.
E2E Complete 4.2 User Guide
76
Within a few seconds, the selected mailboxes disappear from the Mailboxes view as they are moved into the
Mailbox Jobs view. If a large number of databases then display in the selection window, you can reduce the size by
clicking on the appropriate filter icon.
E2E Complete utilizes the New-MoveRequest PowerShell command to migrate mailboxes. The Microsoft Exchange
Mailbox GUID value is used as the identity parameter.
A CSV file of mailbox migration jobs can be imported from the command line. See Appendix F for more information.
Permissions that are inherited (set at the Exchange Org\Server level) are not read from the source or migrated to
the target mailbox.
E2E Complete 4.2 User Guide
77
6. Mailbox Jobs View
To view the mailbox jobs, click the Mailbox Jobs button in the Main Toolbar.
1.
In this view, the migration queue of the initial home forest displays. Regardless of the direction of
migration, an Exchange Client Access Server in the home forest (where E2E is installed) is responsible for
processing the mailbox migration.
2.
Select your site of choice (All Sites is the default) from the drop-down menu, and the migration queue from
the destination server site displays:
Active migrations can be suspended when 95% complete by selecting Suspend when ready to complete
option on the right-click menu. This option is not available for active migrations to Exchange 2013,
Exchange 2016, or Microsoft Online (Office 365).
The menu options related to the mailboxes in the migration queue:

Cancel: Removes the selected item(s) from the Active queue and places them into the History queue. The
MCP Service cancels the job and the mailbox is returned to the Mailboxes list.

Resubmit: Resubmits the item(s) that previously failed with an error with the originally selected migration
options. This option appears only if a selected item failed with an error.

Suspend: Suspends the selected items(s). In Progress item(s) can be suspended.

Migrate now: Resumes previously suspended item(s)

Suspend when ready to complete: Automatically suspends when 95% complete. This option is not
available for in-progress migrations to Exchange 2013, Exchange 2016, or Microsoft Online (Office 365).
See Appendix J for information about how mailbox permissions are migrated.
Adding Mailboxes to the Mailbox Jobs
To check the validity of a mailbox database as a target, you can run this PowerShell cmdlet:

Get-MailboxDatabase | ft Name,IsExcludedFromProvisioning,IsSuspendedFromProvisioning
E2E Complete 4.2 User Guide
78
If any return with a value of True, E2E Complete won’t use it as a target.
You can modify this with the PowerShell cmdlet:

Set-MailboxDatabase MDB01 -IsExcludedFromProvisioning $FALSE
… replacing MDBO1 with the name of your database.
Mailbox Jobs History
The default view is set to Active; however, when you select the History tab on the Mailbox Jobs screen, the view
displays different information as well as migrations that have already completed and are not Submitted, Scheduled,
In Progress or Suspended.
Migration Status
As the migration proceeds, the status changes in the Status column from Scheduled to Submitted to Queued to
Started to In Progress to Completed. If the migration job encounters an error, the status changes to Error or
Suspended.
You can refer to the logs to understand the error and resolve it. A brief error message is displayed in the Error
column.
Migration Status designations are:

Scheduled: A migration time has been scheduled, but the job has not yet started.

Submitted: When the migration request flows from the E2E queue to the Exchange server.

Queued: When the user mailbox is added to the migration queue.
E2E Complete 4.2 User Guide
79

Started: When the user mailbox migration is waiting to be processed by Exchange.

In Progress: When the user mailbox migration is in progress.

AutoSuspended: When the user mailbox migration is suspended automatically at 95% because the Suspend
when Ready to Complete option was selected.

AutoSuspend: When the user mailbox migration is in the process of auto-suspending.

BlackoutSuspended: When the user mailbox migration is suspended due to blackout period.

Suspended: When the user mailbox migration is suspended.

Suspending: When the user mailbox migration is in the process of suspending.

Resuming: A previous suspended mailbox migration has been resumed. Mailboxes automatically
suspended and resumed or suspended due to a blackout period and automatically resumed after the
blackout period are migrated before new mailbox migrations.

Completed: When the user mailbox migration is complete.

Error: When the user mailbox migration halts or errors.
E2E Complete 4.2 User Guide
80
7. Blackout Times View
Blackout profiles can be created to include blackout periods during which no mailboxes assigned to the selected
blackout profile will be migrated, even though schedule. Typically, blackout periods are set to correspond with the
users’ working hours.
If the mailboxes reside on Exchange 2003, and you migrate them during working hours, user mailboxes
will be taken offline for the migration to take place.
If user mailboxes reside on Exchange 2007, and you migrate them during working hours, it may severely
affect the performance of the production server and the network.
Setting up these blackout profiles gives the administrator the flexibility to keep scheduling migrations without
disrupting users’ workflow and affecting the production server performance.
For more information about how blackout times are applied to forests, see the field notes for the Apply mailbox
blackouts setting, in the forest-configuration General tabs (for source, target and tenant forests).
Applying Blackout Times to the Forest
To set blackout times with blackout profiles:
1.
Click Blackout Times in the main toolbar.
2.
Select a blackout profile from the Profile drop-down list. All user mailboxes are initially set to the default
blackout profile. If needed, click Add Profile to create additional blackout profiles.
3.
Select a time zone from the Profile Time Zone drop-down list. This setting helps you set blackout periods
based on your local time. (All blackout time periods are stored in UTC.)
4.
Select the calendar format. Click the Day, Week, or Month button to view a daily, weekly, or monthly
calendar, respectively. If you click the Month button, the format will vary as it is displayed in a month
format as shown below.
E2E Complete 4.2 User Guide
81
You can also navigate to different dates, months, or years using the time navigation tool located in the right corner
of the UI. The behavior of the tool changes to reflect your current format.
The calendar icon in the middle of the navigator lets you view a calendar where you can select a different date or
even a month.
To start adding a blackout period, double-click a time or a day in the calendar depending on whether you are
viewing a daily, weekly, or monthly calendar. If you are in the Timeline format, double-click in the cell just below the
date.
The Appointment dialog box appears. Setting a blackout period is like setting up a meeting appointment in Outlook.
It is a detailed Appointment setting tool making it a full-fledged free/busy scheduler. You can also categorize, color
code, and assign priorities as well.
In the Appointment dialog box, specify what you would like to call these blackout periods, and provide a description
in the Description field.
Specify a Start time and End time, or you can select the All day event checkbox if blackout is to be exercised the
entire day.
If you wish to repeat this setting for other days, click the Edit recurrence tab to open the Appointment Recurrence
dialog box:
E2E Complete 4.2 User Guide
82
And specify the recurrence pattern:

Specify whether the specified blackout period will recur daily, weekly, monthly, or yearly.

For a Weekly recurrence, then also specify the frequency at which it will occur, and the day(s) of the week.
For example, the blackout period will occur every week or every two weeks, on Tuesdays.

Specify a Start date for the blackout recurrence periods.

Specify an end date for the blackout recurrence periods.
Click OK to save your recurrence pattern, and the Appointment dialog box reappears. Click Save & Close to save all
the settings:
The blackout periods are set in the calendar as shown below.
E2E Complete 4.2 User Guide
83
The default blackout profile is initially applied to all user mailboxes. To set user mailboxes to a different blackout
profile, select one or more mailboxes in the Mailboxes or Mailbox Jobs view and edit the Properties in the rightclick menu.
Manually suspended migrations ignore blackout periods if they are manually resumed, and will begin
migrating immediately.
Overriding Blackouts or Scheduled Migrations
E2E Complete provides the functionality to override blackouts which are in place, or migrations that have been
scheduled for a future time. Once you have scheduled a blackout, or have scheduled users for a migration, the
following type of information displays in the Mailbox Jobs of the Admin User Interface:
To override blackouts or future scheduled migrations: Select the user, then right-click and select Migrate now:
E2E Complete 4.2 User Guide
84
8. Migration Summary View
The Summary view is accessed when you want to find out the status of all the migrations from all the sites.
You can sort and group these items based on the available attributes to create a view that will give you a clear
picture of what is going on with the migration on all the migration sites.
E2E Complete 4.2 User Guide
85
9. Migration Schedule View
The Schedule view is a read-only and displays mailboxes in all statuses throughout a migration.
By default, it displays the user mailboxes from the migration site that is currently selected in the Site box. To review
the schedule of user mailboxes from another migration site, you must select it in the Site box. E2E Complete uses
the Destination site whenever it displays data.
If you hover over a user, it will display information, such as the status, data migrated in bytes, number of items
migrated from a mailbox, time the migrated started, and time when it ended.
Select the View Blackouts in schedule check box to display the appropriate blackout schedules listed in the
Schedule view. Deselect this check box to remove the blackouts from the view.
If you change to the Week view, you can see the same information.
Based on the information you specified when adding mailboxes to the migration queue and the information from
previously scheduled mailboxes, this view even anticipates when a user mailbox might be migrated.
E2E Complete 4.2 User Guide
86
10. Migration Metrics View
This view lets you depict the amount of data that has been migrated and number of mailboxes that have been
migrated during a specific time graphically.
1.
In the Report field, click the down-arrow select a report. Four reports are available:

Migration Totals

Data Throughput

Status Summary

Mailbox Locations
2.
Select a Forest. All forests are selected by default.
3.
Select a Site. All sites are selected by default.
4.
Select or enter a time range for the report in the Range date selector fields.
5.
Once the graph is displayed, you can do the following:

Pause on (hover mouse over) a bar (or circle graph sector) to view statistics.

Use the zoom icons on bar graphs to increase or decrease the size of the graph.

Use the horizontal scroll bar and scroll arrows at the base of bar graphs to view the sections of the
graph not visible on the screen.

Export the graph to a PNG, BMP, Xlsx, or Xps format file and use it in your report. After you have
selected the format, it opens a Save As dialog box for you specify the location for saving the exported
graph.
Data Throughput
In the Report field, select the Data Throughput option. Data Throughput is selected by default.
E2E Complete 4.2 User Guide
87
Migration Totals
In the Report field, select the Migration Totals option:
Mailbox Locations
In the Report field, select the Mailbox Locations option:
Status Summary
In the Report field, select the Status Summary option:
E2E Complete 4.2 User Guide
88
11. Public Folders View
Note that migrating public folders to Exchange Online requires the use of a built-in wizard. Refer to the topic
Migrating Public Folders to Exchange Online (in the Public Folder Jobs View section) for more information.
Public folder migration to Exchange 2013 requires Exchange 2013 CU5+.
E2E Complete supports only uni-directional (source to target) synchronization if the Source Public Folder
server is Exchange 2003 or 2007. To synchronize public folder bi-directionally in this scenario, a replica
resident on Exchange 2010 must be selected as the Source.
E2E may encounter issues when migrating public folder to Exchange 2013 using bi-directional
synchronization if an Outlook Profile is not used. This problem can be resolved by configuring an Outlook
Profile for the public folder migration to Exchange 2013.
The Global Catalog Server value should not be changed in the Forest Setting during public folder
migration to ensure Email Address changes will be detected by E2E Complete
Adding Public Folders to the Public Folder Jobs
The Public Folders view lists public folders from all sites in the specified domain. In addition, it lets you search and
select public folder to add to the public folder Jobs.
To add public folders to the Public Folder Jobs:

Click Public Folders in the main toolbar. The screen displays Source Folders on the left side and Target
Folders on the right. All items in the Source and Target Folders in this view are periodically refreshed
automatically. However, you can manually refresh all items in the Source or Target Folders at any time by
clicking Refresh under the Actions menu. Individual items are updated after migrations and can be updated
at any time by right-clicking on an item and clicking Refresh.
Exchange 2013 and 2016 public folder hierarchies can be split across multiple servers and mailboxes so
the public folder listed under Server and Mailbox are not displayed. For Exchange 2013 and 2016 public
folder the Server and Mailbox information is displayed in the “hover over” tool tip.
E2E Complete 4.2 User Guide
89
E2E Complete will synchronize Send-As and Receive-As public folder permissions for non-mail-enabled
groups. Note, however that Receive-As is not supported by Exchange Online (Office 365). Also, other
public folder permissions (e.g. Owner, FolderVisible, and so on) are only supported by Exchange for mailenabled groups.
Anonymous and default permissions are migrated if enabled in the Public Folders settings.
Source and Target folders can be searched for by using the search box above the folder lists. Also, a folder list can be
collapsed or refreshed by selecting an option from the Actions drop-down menu above the folder lists.
Click on the forest, server, and/or folders you want to send to the migration queue and drag them to the Target
Folders pane.
The following screen displays in the Add folders to migration queue view. The Binary Tree Knowledge Base article
link will display if migrating Schedule+ Free/Busy. Click the link for more information on how to support Schedule+
Free/Busy coexistence between Exchange 2003 and Exchange 2010/2013. (This information is also available in
Appendix E of this document.)
Indicate the settings you want to apply to the job by selecting the options on the screen:

Source: The path to the location from which the folders are being migrated.

Target: The path to the location to which the folders are being migrated.

CAS Server: If the destination server does not include the "Client Access Server"(CAS) role, you must select
a CAS that can access the target server. You can select a valid CAS server using the drop down list or type in
the logical name of your CAS array. The specified CAS should be in the same Active Directory site as the
target public folder server.

PF Mailbox (appears for Exchange 2013 and higher targets): The public folder Mailbox to migrate to in the
target. The drop-down list includes all public folder mailboxes available in the target. The default is Auto
select, which will be the smallest target PF mailbox.
E2E Complete 4.2 User Guide
90
If PF Mailbox is set to Auto select, and two or more PF mailboxes meet the criteria, E2E
selects the PF mailbox with the largest percentage of quota remaining.
If no PF mailbox meets the criteria, E2E notifies you in a dialog box and lets you choose
between continuing with the selected target PF mailbox (only if the job would fit within the
quota), or creating a new PF mailbox:

Scheduled Start: Select date and time by clicking on the calendar icon. Setting this value instructs the
migration engine to NOT submit folders to the Target until after the set time condition is met. Use this to
manage when a group of folders are being migrated.

Sync Interval: Enter the interval at which you want E2E Complete to copy new or changed folders to the
target folders. Valid values are any time interval from 0 seconds to 24 hours. Syncs will not continue if a
migration error is encountered during a sync. Syncs will not continue if a migration error is encountered
during a sync.

Folder options: Select one of the following options: All sub folders, No sub folders, or Custom.
Then select the folders you want to copy to the migration queue., and click the Add to Migration Queue button to
add the selected folders to the Public Folder Jobs.
When you click Add to Migration Queue, E2E verifies the aggregate size of all public folders to be migrated from
the source. The program also verifies that a public folder exists in the target that can accommodate the source
folder(s) without exceeding 90% of the available quota configured for the PF mailbox.
If PF Mailbox is set to Auto select, and two or more PF mailboxes meet the criteria, E2E selects the PF
mailbox with the largest percentage of quota remaining.
If no PF mailbox meets the criteria, E2E notifies you in a dialog box and lets you choose between
continuing with the selected target PF mailbox (only if the job would fit within the quota), or creating a
new PF mailbox.
How Rename Conflict Resolution Works
The following public folder migration rules apply when using the Rename Conflict Resolution option. These rules
assume that before the initial migration (sync), there is an existing public folder on the Target with the same name
as a Source public folder.
During an initial one-way sync:

If there are document(s) on the Source and Target with the same name, the source document will be
synced to the Target and renamed with the Rename Mask.

When the one-way sync is completed, the Target will contain both the renamed source document and the
original target document.
E2E Complete 4.2 User Guide
91
During continual one-way syncs after the initial sync:

If a source document, that has a corresponding renamed document on the Target, is modified on the
Source, the corresponding renamed document on the Target will be updated (overwritten).

The renamed document on the Target is never evaluated again in a one-way sync. Any changes made to the
target document will be overwritten if the original source document is modified.
During an initial bi-directional sync:

If there are document(s) on the Source and Target with the same name, the source document will be
synced to the Target and renamed with the Rename Mask and the target document will be synced to the
Source and renamed with the Rename Mask.

When the bi-directional sync is completed, the Target will contain both the renamed source documents and
original target documents, and the Source will contain both the renamed target documents and the original
source documents.
During continual bi-directional syncs after the initial sync:

After the initial bi-directional sync, the source and (renamed) target document can be considered a 'pair'.
Changes to either document will be resolved using 'last modified' conflict resolution.
New public folder jobs are always completed before re-synchronization jobs are started.
If the Domain Name and SMTP Namespace Are Different
E2E Complete copies Free Busy messages from the source to the target, and renames the subject header so that it
matches the Legacy Exchange DN of the target object. In environments where the domain name and the SMTP
name space are different, Exchange must be directed to browse the Schedule+ Free Busy folder to discover this
information. To do this:

Open the Exchange Management Shell on Exchange and execute the following command where
“ForestName” is set to the *PrimarySMTP* namespace of the contact objects residing in the target.
Add-AvailabilityAddressSpace –ForestName contoso.com –AccessMethod PublicFolder
As Exchange 2013 no longer supports Schedule+ Free/Busy, the functionality included in E2E Complete is not
sufficient to provide cross-forest Free/Busy lookups during your migration. To achieve this, you will have to manually
configure “Availability Service Sharing” within your environments. Please see Appendix E for some basic guidance, or
contact your Binary Tree sales representative about engaging with our consulting services group.
E2E Complete 4.2 User Guide
92
How Public Folder Mail-Enablement Works
BTMailEnableService is a separate service that executes the sequence of calls necessary to mail-enable public folder.
In complex Exchange environments, it can take a significant amount of time for information about a new public
folder to propagate and for Exchange’s addressing policies to create the initial proxy address structure. The public
folder engine offloads this process to the BTMailEnableService and continues with data migration.
BTMailEnableService is started the first time a Mail-Enabled public folder is migrated and writes output to the
application log.
E2E Complete 4.2 User Guide
93
12. Public Folder Jobs View
The Public Folder Jobs view lets you manage the sequence of migration requests for the selected migration
destination.
E2E logs an error message if a source folder is moved to a new location and the associated target folder
already exists. For example, if \folderB is moved to \folderA\folderB in source, and a different
\folderA\folderB already exists:
Failed to move folder '\folderB' to '\folderA\folderB' on server 'MyTargetServer1'
System.Runtime.InteropServices.COMException (0x80040604): Error in
IMAPIFolder.CopyFolder(FOLDER_MOVE): MAPI_E_COLLISION
1.
Click Public Folder Jobs in the main toolbar. The screen displays a list of folders ready for migration:
2.
This view provides a number of details about the public folders being migrated.
3.
If you want to move one of the public folder migration jobs to the top/bottom of the migration queue,
right-click on the selected public folder migration job, then click the Move to top of queue or Move to
bottom of queue option, as desired.
4.
If you want to move one of the public folder migration jobs by one, click Move up one or Move down one,
as needed.
The above options have no effect on Active or In-Progress migration jobs.
E2E Complete 4.2 User Guide
94
The Sync Interval, Bi-Directional, and Conflict Resolution settings for a job can be changed in the table:
You can also choose to Cancel selected jobs, Export information about selected jobs to a CSV file and change the
columns in the view.
Public Folder Jobs History
The default view is set to Active; however, when you select the History tab on the Public Folder Jobs screen, the
view displays different information as well as migrations that have already completed and are not Submitted,
Scheduled or In Progress.
Public Folder Migration for Non-Trusted Environments
E2E supports Outlook 2013 for public folder migration only to public folder, not to Office 365 Groups.
Also, note that Outlook 2013 32-bit can connect only to Exchange 2007, 2010, 2013, 2016 and Office
365, not to Exchange 2003.
To install and configure Outlook 2010 or 2013 32-bit:
1.
Install Microsoft Outlook (32-bit) and then run “Microsoft Updates” to install applicable updates and
patches.
2.
Use the Control Panel/Mail (32-bit) applet to configure a profile for the untrusted domain.
E2E Complete 4.2 User Guide
95
3.
Select the Manually configure server settings or additional server types option and click Next.
E2E Complete 4.2 User Guide
96
4.
Select the Microsoft Exchange or compatible service option and click Next:
5.
Enter the server name for your account, uncheck Use Cached Exchange Mode and click Next:
E2E Complete 4.2 User Guide
97
6.
Select the profile for the target public folder account and click OK:
7.
Launch Outlook using the account profile:
8.
Enter the account login information and select the Remember my credentials checkbox:
9.
In E2E Settings, select one of the Outlook profiles that were set up for connectivity and credentials when
migrating public folder in a non-trusted environment.
E2E Complete 4.2 User Guide
98
Migrating Public Folders to Exchange Online
E2E can migrate public folders to Exchange Online using either PowerShell or MAPI. The PowerShell option or MAPI
option is selected from the Public Folders Migration Mode drop-down list on the General tab of the Office 365
Forest Configuration Settings screen.
When using PowerShell, in order to migrate Exchange 2003 public folder to Microsoft Online (Office
365), you must first replicate the Exchange 2003 public folder to either Exchange 2007 or 2010. Then,
the 2003 replicas must be removed and the 2003 public folder database dismounted. Finally, the public
folder can be migrated from Exchange 2007 or 2010 to Office 365. Note that migration of public folder
hosted on Exchange 2013 using the New-PublicFolderMigrationRequest PowerShell command to Office
365 is not supported. The MAPI migration engine does not have this limitation.
To Migrate Public Folders to Exchange Online Using PowerShell
1.
Click Public Folders in the main toolbar. The screen displays Source Folders on the left side and Target
Folders on the right.
2.
Click on the folders you want to send to the migration queue and drag them to the Target Folders pane.
3.
The Migrate Public Folders wizard appears. Follow the instructions on the first screen to ensure that routing
to the Exchange Online domain is configured correctly. When finished, click Next.
E2E Complete 4.2 User Guide
99
4.
The On-Premise Folders screen appears. Select the folders to migrate and then click Next.
5.
The Size Limits screen appears. Enter a Large Item Limit and Bad Item Limit. You may enter 0 to allow an
unlimited number of large or bad items. Click Next.
E2E Complete 4.2 User Guide
100
6.
[Conditional Step.] If a backslash character occurs in the filename of any folder to be migrated, this Rename
Public Folders screen appears so that the folder(s) can be renamed. Enter a character that E2E should use to
replace the backslash character when renaming the folder(s), and click Next.
7.
The Clear Exchange Online screen appears. Review the changes and select the I understand checkbox to
confirm that you understand the changes to the Exchange Online environment cannot be undone. Click
Next.
E2E Complete 4.2 User Guide
101
8.
The Public Folder Mailboxes screen appears. Specify the Maximum Size for the public folder Mailboxes and
click Next.
9.
The Start Migration screen appears. Click Finish to begin migration.
E2E Complete 4.2 User Guide
102
10.
The Starting Migration screen appears. The successful processes are marked with a green checkmark when
complete. When complete, Click Next.
The migration will automatically be suspended at 95%. Once suspended, the migration can do the final
cutover by resuming the migration.
When there is a PowerShell failure and less than 10% of the known public folders for a public folder
server are returned, E2E Complete will not mark them all as deleted. A message stating the number of
returned folders will appear in the log.
To Migrate Public Folders to Exchange Online Using MAPI
Click Public Folders in the main toolbar. The screen displays Source Folders on the left side and Target Folders on
the right.
Click on the folders you want to send to the migration queue and drag them to the Target Folders pane. Unlike
PowerShell, using MAPI allows for public folders to be migrated one at a time.
When using MAPI, public folders can only be migrated to a public folder Mailbox existing on the target
Office 365 forest. The MAPI migration mode does not have the ability to create public folder Mailboxes
on the target, so the PowerShell migration mode should be used in these scenarios.
E2E Complete 4.2 User Guide
103
Indicate the settings you want to apply to the job by selecting the options on the screen:
The settings on this screen:

Source: The name of the public folder that is being migrated.

Target: The destination path of the Office 365 public folder mailbox.

CAS Server: Since the destination is an Office 365 tenant, the CAS Server entry should be pointed to the
Office 365 remote PowerShell host.

PF Mailbox: The public folder mailbox to migrate to in the target. The drop-down list includes all public
folder mailboxes available in the target. The default is Auto select, which will be the smallest target PF
mailbox.

Scheduled Start: Specify the date and time you want the job to start.

Sync Interval: Select or enter the interval in minutes at which you want E2E Complete to copy new or
changed folders to the target mailbox. Valid values are any value in the range from 0 to 24 hours. Syncs will
not continue if a migration error is encountered during a sync. Note also that, while this Sync Interval sets
up sync jobs, a sync job will not start to copy new items unless Change Detection is running.

Folder options: All sub folders, or No sub folders, or Custom. Note that if Custom is selected, only folders
that are selected in the UI will be migrated.
Then click Add to Migration Queue to add the selected folders to the Public Folder Jobs.
The folder will appear in the Target Folders pane.
To Rollback Exchange Online Folders
1.
Click Public Folders in the main toolbar. The screen displays Source Folders on the left side and Target
Folders on the right.
2.
Click on the folders you want to rollback and drag them to the Source Folders pane.
E2E Complete 4.2 User Guide
104
3.
The Rollback Public Folders wizard appears. Follow the instructions on the first screen to ensure that you do
not lose any email and content received after migration. When finished, click Next.
4.
The Clear Exchange Online screen appears. Review the changes and select the check box to confirm that
you understand the changes to the Exchange Online environment cannot be undone. Click Next.
E2E Complete 4.2 User Guide
105
5.
The Start Rollback screen appears. Click Finish to begin the rollback, and the Rollback Complete! screen
appears when the rollback finishes. Click Close to close the window.
Migrating Public Folders to Office 365 Groups
E2E can migrate public folders to Office 365 Groups using the MAPI protocol, but not by PowerShell. The MAPI
option is selected from the Public Folders Migration Mode drop-down list on the General tab of the Office 365
Forest Configuration Settings screen.

Migration of public folders to Office 365 Groups requires the E2E Worker be configured with the
Provisioning role.

Only Mail, Appointments, Posts and Documents (IPM.Document types) can be migrated to an
Office 365 Group. An IPM.Document that is directly stored in a public folder is migrated to an
Office 365 Group as a new conversation (IPM.Note).
You must use a cloud mailbox originally created in Office 365 (not a federated account or an account
that was migrated) as your MAPI account. E2E Complete will be unable to open the Office 365 Group
mailbox if a cloud mailbox is not used. The account must also be a Global Office 365 administrator. This
account can be configured in the Exchange (MAPI) section of the General tab of E2E’s Office 365 Forest
Configuration Settings screen.
E2E Complete 4.2 User Guide
106
To migrate public folders to Office 365 Groups using MAPI:
1.
Click Public Folders in the main toolbar. The screen displays Source Folders on the left side and Target
Folders on the right.
2.
On the right (target) side, select the Target Folders drop-down and select Target Groups:
3.
On the left (Source) side, click on the public folders you want to send to the migration queue, and (one at a
time) drag them to the Target Folders pane. This approach lets you migrate source public folders one at a
time to different Office 365 Groups.
You can choose to copy a top-level public folder and all subfolders to a single Office 365 Group. This
means (for example) that if you have multiple calendars configured as subfolders, all items contained in
the different calendars will be consolidated into the single calendar contained within the target Office
365 Group.
With MAPI, public folders can be migrated only to an existing Office 365 Group in the target Office 365
forest. The MAPI migration mode cannot create Office 365 Groups in the target.
E2E Complete 4.2 User Guide
107
4.
5.
Indicate the settings you want to apply to the job by specifying your choices on this screen:

Source: The name of the public folder that is being migrated.

Target: The name of the Office 365 Group that represents the desired migration endpoint.

CAS Server: Since the destination is an Office 365 tenant, the CAS Server entry should be pointed to
the Office 365 remote PowerShell host.

Scheduled Start: Specify the date and time you want the job to start.

Sync Interval: Select or enter the interval in minutes at which you want E2E Complete to copy new
or changed folders to the target Groups. Valid values are any value in the range from 0 to 24 hours.
Syncs will not continue if a migration error is encountered during a sync. Note also that, while this
Sync Interval sets up sync jobs, a sync job will not start to copy new items unless Change Detection
is running.

Folder options: All sub folders, or No sub folders, or Custom. Note that if Custom is selected, only
folders that are selected in the UI will be migrated.
Click the Add to Migration Queue button to add the selected folders to the Public Folder Jobs.
E2E Complete 4.2 User Guide
108
13. Content Analysis View
Content Analysis lets you collect information about the public folder environment and utilize SQL to analyze and
remediate before migration. Review Appendix H for more information about content analysis.
At least one Worker must be assigned the Reporting role for this purpose.
To collect information for a forest, click Content Analysis in the main toolbar. Then select a Forest and click Submit
(button at the bottom of the Data Table):
To change the information collected, select a Forest and click the Properties button. Then you can edit the
properties on the Report Run Settings screen:
The options on this screen:

Forest Name: The name of the forest for which you want to collect data.

Permissions: Tells E2E Complete to collect public folder permissions.

Items: Tells E2E Complete to collect information about items stored in public folders.

Attachments: Tells E2E Complete to collect information about public folder item attachments. In order to
collect attachment information, you must collect information about public folder items.

Number of retries: How many times E2E Complete should attempt to collect information about a public
folder if it initially fails. The default is 1 time.
Once Submit is clicked, E2E Complete assigns reporting jobs to any worker with the Reporting role. You can assign a
worker to the Reporting role from the Workers tab.
E2E Complete 4.2 User Guide
109
14. The User Portal
The User Portal can be accessed in two different ways. The first is by the Administrator selecting the Mailbox Jobs
button, and then clicking on the job status for that user's mailbox. The second way is through the notification emails
sent to the user. This is how users will always access the User Portal.
The purpose of this portal is to allow end users to participate in a migration project. Prior to migration, the user can
set an external email address to receive notifications, an SMS mobile number, blackout dates, and notification
options.
During migration, the User Portal indicates the migration status and the anticipated completion time to the user.
After migration, it also indicates the results of the migration. From the Admin Portal, you can access the User Portal
for the user by clicking on the link on Scheduled in the Status column.
Opt Out Option
By default, with E2E Complete you have the ability to turn on the Opt Out option or turn this off for all users.
However, in some cases you may want to limit the scope of this functionality. Administrators can establish a security
group to determine which users can see the Opt Out option and select alternative migration times. The User Portal
will look for an AD group named E2E_Schedulers to determine whether the group exists and then check if the
logged-in user is a member. If they are not a member, they will not be able to reschedule a migration. Note that the
location of the E2E_Schedulers group is not critical and can be placed anywhere in AD that the configured
administrator account can access.
The following is a display of a User Portal.
E2E Complete 4.2 User Guide
110
The fields on this screen:



Migration Schedule:

Status: Status of the user mailbox.

Source Server: Name of the Exchange server from where the user mailbox is being migrated.

Destination Server: Name of the Exchange server to where the user mailbox is being migrated.

Mailbox Owner: Displays the email of the mailbox owner.

Mailbox Size: Displays the total size in of the user mailbox.

Mailbox Items: Number of items in the user mailbox.
Timeline:

Start Date: Date on which the user migration is expected to begin.

Completion Date: Projected date on which the user migration will complete.

Time to Complete: Estimated time (in hours and minutes) to complete the user migration.
Preferences:
E2E Complete 4.2 User Guide
111

Phone Number: Allows user to specify the phone number to send SMS notifications.

Phone Service Provider: Allows the user to specify the phone service provider used by E2E to send
notifications to the user’s phone. The AT&T, Sprint and Verizon providers are recommended for US
customers. Many other providers are available, but they have not been tested.

Email Address: The alternate email that will be used while the mailbox is migrated.

Notification Language: Select the language in which you want to receive notifications.

Do not move my mailboxes between these days: Allows user to specify blackout dates. If the
administrator has selected Do not let users postpone their migration option (in Migration Options),
then users will be unable to customize their migration by setting blackout periods.
After all the settings are specified, click the Save button located in the lower left of the form. Or you can click Cancel
to cancel the settings.
Windows Authentication is enabled for this virtual application. When performing cross forest migrations,
if the users in the source forest attempt to connect to the E2E server in the target forest and a trust has
not been established between the two forests, the users will be prompted for their target credentials.
Multi-lingual Support
Click on English (United States) at the top right of the screen, and then select More choices to view a list of
available languages. If a user changes their default language, all future End User notifications will be sent in this
language.
E2E Complete 4.2 User Guide
112
15. Troubleshooting
Browser-Based Help Fails to Load
If the online browser-based Help doesn’t load correctly after an E2E Complete upgrade, clear the temporary files in
the browser. We recommend you set your browser to clear temporary files and history upon exit.
Public Folder Migration Error
Problem:
When migrating public folders, the following error message is received:
Error: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
There are a number of steps to correct this issue below. Necessary steps are marked as required. The other steps
may or may not be necessary to resolve this issue.
Resolution:
1.
Configure Outlook Anywhere (required).
2.
Open RPC ports 6001, 6002, 6004 (required).
3.
Start RPC Locator service.
4.
Update SSL certificate to include autodiscover.domain.com in the subject.
5.
Open MRS ports 808, 135.
6.
Delete\dismount the Exchange 2003 replicas (required).
Problem with Production Licenses After Upgrading from Trial Licenses
Problem:
There's an issue with E2E Complete when you try to implement a new production license key after running E2E
Complete with free trial licenses.
The system doesn't let you mix license key domains. If you implement the solution with the trial keys, you will not be
able to easily upgrade to a production license.
You would be required to uninstall and re-install the product which removes all their metrics from running the pilot
migrations.
Workaround:
1.
Open the E2E Complete SQL database.
2.
Go to the CMTEUP_Checksum table.
3.
Delete the current row listed in this table.
4.
Now you can apply a new license from within the E2E Complete UI..
E2E Complete 4.2 User Guide
113
Mail Delivery Getting Stuck in a Loop
Problem:
When migrating a Resource Forest mailbox to an Exchange server in a different domain than where the Global
Catalog and PowerShell host reside, Exchange may periodically fail to clear the targetAddress. This results in mail
delivery getting stuck in a loop.
Resolution:
Clear the targetAddress for any target mailbox when this occurs.
Conflict Resolution Issues with Bi-Directional Public Folder Synchronization
Problem:
If a public folder is initially migrated using a one direction synchronization, and a customer then decides that they
want to setup a scheduled bi-directional synchronization job, conflict resolution does not work properly.
Resolution:
The original records of the one direction synchronization should be deleted. This will ensure that conflict resolution
works properly in the bi-directional synchronization.
This is done by clearing the bt_tracdoc table in the E2E SQL database and can be done with the following query:
delete FROM [ ].[dbo].[BT_TracDoc]
For More Troubleshooting Information
Refer to the Binary Tree E2E Complete Knowledge Base:
https://www.binarytree.com/support/search-knowledge-bases/
E2E Complete 4.2 User Guide
114
Appendix A: About Inter-Org Migrations
E2E Complete has the ability to migrate mailboxes between two or more Exchange organizations. From the E2E
Complete Settings page, you can easily add additional organizations whose mailboxes you want migrated to your
target. However, for this function to work there must be a mail-enabled (not mailbox-enabled) account in the target
forest to receive the migrated mail content. In addition, this target account must have the msExchMailboxGuid
attribute copied from the Source to the Target account. E2E Complete and Microsoft PowerShell use this attribute
to authoritatively identify the relationship between the source and target objects.
E2E Complete has no particular preference on how this relationship is established. To perform this association, you
can use Binary Tree’s SMART Directory Sync product, the Prepare-MoveRequest.ps1 script located on your Exchange
2010/2013 server, Forefront Identity Manager, or any other product capable of creating a Mail-Enabled user object
and stamping the correct msExchMailboxGuid value. This flexibility makes for an easier implementation as you
develop your migration project plan.
Getting Mailbox Statistics
When performing Inter-org (cross forest) migrations, mailboxes housed on source forest Exchange 2007, Exchange
2010, and Exchange 2013 servers do not display mailbox sizes and item counts within the E2E Administrative and
User portals.
E2E Complete uses native Exchange protocols to query mailbox sizes and item counts. Unlike Exchange 2003,
Exchange 2007, 2010 and 2013 do not support Windows Management Instrumentation (WMI) as a method for
gathering this information. Instead, either Exchange Web Services (EWS) or Remote PowerShell must be utilized to
gather this information.
Perform either of the following two procedures to gather mailbox size and item count information from these
platforms.
Option 1:
Open the Exchange Management Shell on either Exchange 2007, Exchange 2010, or Exchange 2013 and execute the
following command. This must be executed only once for each messaging server version, to allow E2E to query
mailbox size information from these systems. For Exchange 2007 type the following command:
Get-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission Identity $_.distinguishedname -User (Get-User -Identity Domain\Administrator | select-object).identity extendedRight ms-Exch-EPI-Impersonation}
For Exchange 2010/2013, type the following command:
New-ManagementRoleAssignment -Name:ImpersonationAssignmentName -Role:ApplicationImpersonation User:Domain\Administrator
Option 2:
Identify an Exchange 2010/2013 Server with a valid (non self-signed) trusted SSL certificate that has the IIS service
assigned to it. Open the Exchange Management Shell on this Exchange 2010/2013 server and type these two
commands:
E2E Complete 4.2 User Guide
115
Enable-PSRemoting
Set-PowerShellVirtualDirectory "$env:COMPUTERNAME\PowerShell (Default Web Site)" BasicAuthentication $true
Once completed, open the E2E Admin Portal and click Forests:
... and select the desired source forest in the Forest drop-down list (shown here in the red box):
Then, on the Accounts tab, clear the checkbox for Auto-detect the PowerShell Hosts for this Forest, and type the
appropriate value into the appropriate PowerShell Host field (Exchange 2010, 2013 or 2016):
And then click Save Forest (in the toolbar above the tabs).
To Update Outlook 2003 Clients for Inter-Org Migrations
See Appendix K of this User Guide.
E2E Complete 4.2 User Guide
116
Appendix B: Migrating Mailboxes to Office
365
Mailbox migrations to Office 365 are processed the way that Intra-Org and Inter-Org migrations are executed, by
using the New-MoveRequest PowerShell cmdlet. This enables us to use the same Project Management and
Workflow features of the E2E Complete application available to Intra-Org and Inter-Org migration projects.
For these commands to function, your source environment must meet certain requirements. While this document
does not seek to provide guidance on how to successfully enable a hybrid coexistence strategy, E2E Complete
requires the following two conditions to be true.

There must be an internet facing Exchange 2010 Client Access Server (CAS) running the MRSProxy service.
The CAS is used to upload data from your Exchange 2003, 2007 and 2010 mailboxes.

The environment must be synchronizing its users with Office 365 by way of the Microsoft Online Services
Directory Synchronization tool. The Microsoft Online Services Directory Synchronization tool is used to
create accounts with the proper msExchMailboxGuid values.
For cross-forest migrations with E2E Complete, the home forest where you configure E2E usually is also
the Target forest. However, in the case of Office 365 migrations, it becomes your source.
The AD groups that are in the Office 365 target environment will be rationalized in E2E when the Office
365 forest is added, but the members of those groups will not be rationalized in E2E until the second
rationalization pass has occurred. By default, rationalization updates occur every 60 minutes. The
Update Forest setting in the Activities settings can be set for shorter time periods (fewer minutes)
between updates. However, it is not recommended to set for less than 10 minutes depending on the size
of your Exchange environment.
A staging server is not required to migrate from Exchange 2003 to Office 365. A staging server is
required, however, if rolling back from Office 365 to Exchange 2003.
On-premises Exchange mailboxes and archives migrate to Office 365 with no issues. There is no need to
enable the archive feature in Office 365. If the on-prem mailbox has a server-based archive associated
with it, the New-MoveRequest will enable the archive feature in Office 365 and migrate the on-prem
archive to the Office 365 archive.
Migrations of on-premise Exchange mailboxes to Office 365 will fail and log an error if the source site's
Office 365 proxy servers are not set.
E2E Complete Office 365 Migration License Options
You can either manually license users in the Microsoft Online Services portal before selecting them for migration in
E2E Complete, or allow E2E Complete to auto-license them automatically.
To allow E2E Complete to auto-license users:
1.
Within the Admin Portal, go to the Settings view.
2.
Click the Licenses tab to select Office 365 license packs and related service plans to use for auto-licensing
Exchange Online mailbox migrations.
E2E Complete 4.2 User Guide
117
Appendix C: Diagnostic and Operational
Report Scripts
E2E uses PowerShell as a platform to extend the product and provide external functionality that can be integrated
with other applications and services. E2E's PowerShell scripts let you:

Diagnose connection and configuration problems

Extract operational reports in .csv format

Customize and extend the migration pipeline functionality

Trigger auto-migrations outside of the E2E Complete Admin Portal

Export and import group information between disconnected forests
The E2E Diagnostic scripts are installed in C:\Program Files\Binary Tree\Scripts\E2E\Diagnostic, and include:

Get-BTForest.ps1

Test-ExchangePowerShellHost.ps1
The E2E Operational Report scripts are installed in C:\Program Files\Binary Tree\Scripts\E2E\Report), and include:

Get-BTMigrationReport.ps1

Get-BTBlackoutReport.ps1

Get-BTThroughputReport.ps1
Diagnostic Report Scripts

Get-BTForest.ps1 : Used to quickly scan a forest, validate credentials and access via Active Directory.
PowerShell Command:
.\get-btforest.ps1 –<parameter>

Test-ExchangePowerShellHost.ps1 : Used to validate the PowerShell host connection in the forest using
specified credentials. This is a thorough diagnostic tool to aid in configuring the environment for initial
Exchange / PowerShell / E2E usage.
PowerShell Command:
.\test-exchangepowershellhost.ps1 –<parameter>
Operational Report Scripts

Get-BTMigrationReport.ps1 : Provides reports on the Mailbox Jobs, and the migrations which have been
completed. These reports can be displayed on the screen or output to a CSV file.
PowerShell Command:
.\get-btmigrationreport.ps1 –<parameter>
E2E Complete 4.2 User Guide
118

Get-BTBlackoutReport.ps1 : Provides reports on the blackouts which have been defined in E2E Complete.
These reports can be displayed on the screen or output to a CSV file.
PowerShell Command:
.\get-btblackoutreport.ps1 –<parameter>

Get-BTThroughputReport.ps1 : Provides reports on the Throughput results for completed migrations.
These reports can be displayed on the screen or output to a CSV file.
PowerShell Command:
.\get-btthroughputreport.ps1 –<parameter>
Executing Diagnostic and Operational Report Scripts
To execute a script:
1.
Open the Windows PowerShell command prompt.
2.
Navigate to the location of the scripts.
3.
Enter the name of the script and provide any additional parameters. For example:
.\Get-BTMigrationReport.ps1 –archive –csv c:\migrationreport.csv
E2E Complete 4.2 User Guide
119
The –csv parameter lets you output a report to a new .csv file on the local drive:
You can use the -? parameter to get additional information on the script and available parameters:
E2E Complete 4.2 User Guide
120
Appendix D: Migration Processing Scripts
The Migration Processing Scripts include these MCP scripts:

Confirm-ScheduleMigration.ps1

Confirm-BeginMigration.ps1

Confirm-EndMigration.ps1
Enabling Migration Customization Scripts
Perform the following steps to enable the migration scripts to be called from E2E Complete.
1.
Click Settings in the main toolbar.
2.
Click the Scripts tab. The script settings are displayed.
3.
Check Enable External Scripts.
4.
Set the Scripts Folder location. For example, c:\contoso\scripts\ps\
5.
Enter the script file name for the Migration Script you want to be called. For example: In the End
Migration Script field, enter Confirm-EndMigration.ps1
Failures designed to halt the migration can be expressed as thrown exceptions or as calls to Write-Error
in the confirmation scripts. Both the Schedule and Begin confirmations can halt the migration by failing
in this manner. The End confirmation cannot cause the migration to fail if the mailbox is already
complete, but it can cause a warning to be reported.
Because the confirmation script runs in a non UI environment, calls in PowerShell such as Write-Host will
cause faults and should not be used. Write-Error, Write-Warning, and Write-Verbose are acceptable to
use, since they write to specific pipelines which are redirected in PowerShell.
E2E Complete 4.2 User Guide
121
Migration Customization Scripts
If enabled, the Migration Customization scripts are called by the MCP during mailbox migrations. These scripts are
installed to C:\Program Files\Binary Tree\Scripts\E2E\Extension; however, they are not usually run manually from
the PowerShell console. The files in the Extension folder are not removed during an uninstall.
Confirm-ScheduleMigration.ps1
This script is called when a mailbox has been scheduled for migration, and can be used to perform any custom
actions prior to submitting the mailbox to Exchange.
<add key="Confirm-ScheduleMigration" value="$null"/>
The MCP will not execute any custom scripts for the Schedule Migration step of a mailbox. This is the default entry
in the MCP configuration file.
<add key="Confirm-ScheduleMigration" value="Confirm-ScheduleMigration.ps1"/>
The MCP will execute the Confirm-ScheduleMigration.ps1 script located in the defined script folder for the Schedule
Migration step of a mailbox.
<add key="Confirm-ScheduleMigration" value=""/>
The MCP will execute the default script (named Confirm-ScheduleMigration.ps1 in this example) located in the
defined script folder during the Schedule Migration step of a mailbox.
<add key="Confirm-ScheduleMigration" value="MyCmdlet"/>
The MCP will execute the specified cmdlet during the Schedule Migration step of a mailbox.
E2E Complete 4.2 User Guide
122
Confirm-BeginMigration.ps1
This script is called before a mailbox is migrated, and can be used to perform any prep-work necessary prior to the
submission of the mailbox to Exchange.
<add key="Confirm-BeginMigration" value="Confirm-BeginMigration.ps1"/>
The same values listed above for the Confirm-ScheduleMigration script can be used for the Confirm-BeginMigration
script.
Confirm-EndMigration.ps1
This script is called after a mailbox is migrated, and can be used to perform any post-processing work necessary
after the mailbox has been migrated by Exchange. Note however that this script is only called if the migration job is
Completed or CompletedWithWarning.
<add key="Confirm-EndMigration" value="Confirm-EndMigration.ps1"/>
The same values listed above for the Confirm-ScheduleMigration script can be used for the Confirm-EndMigration
script.
Script Parameters
All scripts include the following parameters:

$SourceCredential : The source forest PS credentials defined in E2E settings

$SourceForest : Source forest name

$SourceServer : Source server FQDN

$SourceDatabase : Source database DN

$SourceMailbox : Source mailbox DN

$TargetCredential : The target forest PS credentials defined in E2E settings

$TargetForest : Target forest name

$TargetServer : Target server FQDN

$TargetDatabase : Target database DN

$TargetMailbox : Target mailbox DN (not mandatory for the Confirm-BeginMigration.ps1 script)

$Status : Current job status string

$ControllingForest : optional, not used
E2E Complete 4.2 User Guide
123
Appendix E: How to Support Schedule+
Free/Busy Coexistence Between Exchange
2003 and Exchange 2010/2013
If your project requires Free/Busy coexistence between Exchange 2003 and Exchange 2010 or 2013 you will need to
configure the Exchange availability service for cross-forest topologies.
Binary Tree recommends that you follow Microsoft’s best practices for setting up the required infrastructure. More
information may be found at this link: http://technet.microsoft.com/en-us/library/bb125182(v=exchg.141).aspx
While this document is unable to provide specific instructions for your environment, we would like to share some
general guidance that can be used to establish Free/Busy sharing between Exchange 2003 and Exchange 2010 or
2013.
To provide some background, the central challenge is as follows: Exchange 2003 does not natively support the
availability service, while Exchange 2013 does not natively support Schedule+ public folder data. The resolution is to
add a component which can bridge the gap between these two environments. In this case it involves adding an
Exchange 2010 SP2 RU5 server (or greater) installed in the Exchange 2003 source organization. Once this has been
established, the Exchange 2010 server can be used to proxy this information from Exchange 2003 to the Exchange
2010 or 2013 server in the target environment.
This general outline assumes that a two-way trust is in place:
1.
Define DNS conditional forwarders so that servers from either side are resolvable in the opposing forest.
2.
On the source forest, create a DNS A Record for autodiscover.source.com and direct it to the source
Exchange 2010 server.
3.
Verify that autodiscover.source.com resolves to a trusted certificate from every Exchange server in the
target (valid SSL cert, either public or private).
4.
Establish directory coexistence with a process creating the mail-enabled user objects in a manner compliant
with the Exchange availability service, such as Binary Tree DirSync.
5.
On the source Exchange 2010 server, add a local replica of the Schedule+ folder.
6.
On the source Exchange 2010 server, open the Exchange Management Shell and execute this command:
Set-WebServicesVirtualDirectory -identity “Source2010\EWS (Default Web Site)” -ExternalURL
https://source2010.source.com/ews/Exchange.asmx
7.
On the source Exchange 2010 server, open the Exchange Management Shell and execute this command:
Get-ClientAccessServer | Add-ADPermission -AccessRights ExtendedRight -ExtendedRights "ms-exchepi-token-serialization" -User "TargetDomain\Exchange Servers"
8.
On the source Exchange 2010 server, open the Exchange Management Shell and execute this command:
$a = Get-Credential (Type "Target\Administrator")
Export-AutodiscoverConfig -TargetForestDomainController "targetDC.target.com" TargetForestCredential $a -MultipleExchangeDeployments $true
E2E Complete 4.2 User Guide
124
9.
If the source is Exchange 2003, open the Exchange Management Shell on the target Exchange 2010 or 2013
server, and execute this command:
Add-AvailabilityAddressSpace -ForestName SourcePrimarySMTP.com -AccessMethod PublicFolder
If the source is Exchange 2010, on the target Exchange 2013 server, open the Exchange Management Shell
and execute the following command:
Add-AvailabilityAddressSpace -ForestName SourcePrimarySMTP.com -AccessMethod OrgWideFB
10.
On the target forest, create a DNS A Record for autodiscover.target.com and direct it to the target
Exchange 2010 or 2013 server.
11.
Verify that autodiscover.target.com resolves to a trusted certificate from every Exchange server in the
source (valid SSL cert, either public or private).
12.
On the target Exchange 2010 or 2013 server, open the Exchange Management Shell and execute this
command:
Set-WebServicesVirtualDirectory -identity “Target2013\EWS (Default Web Site)” -ExternalURL
https://target2013.target.com/ews/Exchange.asmx
13.
On the target Exchange 2010 or 2013 server, open the Exchange Management Shell and execute this
command:
Get-ClientAccessServer | Add-ADPermission -AccessRights ExtendedRight -ExtendedRights "ms-exchepi-token-serialization" -User "SourceDomain\Exchange Servers"
14.
On the target Exchange 2010 or 2013 server, open the Exchange Management Shell and execute this
command:
$a = Get-Credential (Type "Source\Administrator")
Export-AutodiscoverConfig -TargetForestDomainController "sourceDC.source.com" TargetForestCredential $a -MultipleExchangeDeployments $true
15.
On the source Exchange 2010 server, open the Exchange Management Shell and execute this command:
Add-AvailabilityAddressSpace -ForestName TargetPrimarySMTP.com -AccessMethod PerUserFB UserServiceAccount $true
At this point users from opposing forests should be able to request Free/Busy information from their Outlook or
OWA clients.
E2E Complete 4.2 User Guide
125
Appendix F: E2E Mailbox Job Importer
The Binary Tree E2E Mailbox Job Importer utility is installed as part of E2E Complete. The Binary Tree E2E Job
Importer allows you import a CSV schedule file of mailbox migration jobs from a command line. A CSV file can also
be used to update existing mailbox migration job values. A CSV cancel file can be used to cancel mailbox migration
jobs.
Migration jobs that are in AutoSuspended or BlackoutSuspended state (only if Suspend When Ready to Complete
flag was set) can be modified. For these jobs, only the Do Not Complete Before Date, Do Not Start Before Date,
Migration Group, and Priority fields will be updated.
The Auto license 0365 users and Default Usage Location settings in the Tenant Forest General Settings are used by
the E2E Job Importer when scheduling mailbox migration to Office 365.
CSV Schedule File Format
The CSV schedule file of mailbox migration jobs must meet the following requirements:

The file should not contain headers.

No values can be blank except for the Do Not Start Before Date, Do Not Complete Before Date,
Communication Language, Migration Group and Blackout Profile.

All columns must be included.
The CSV schedule file must include these columns:
Col
Field
Example
Req’d?
Description
Saved To
Matched Against
1
User
[email protected] Yes
Principal
Name
(UPN)
User Principal Name of
desired mailbox.
CMTEUP_PersonAD
Data.user
PrincipalName
2
Target
Forest
Name
Yes
Name of target forest.
CMTEUP_Forests.F
orestName
3
Target root1.contoso.com
delivery
domain
Yes
Name of target domain for CMTEUP_Job.param_
mailbox.
Target
DeliveryDomain
4
Target primarymailbox1
Mailbox
Database
Name
No
Name of target mailbox
database. Should be blank
if target is an O365 forest.
contoso.com
E2E Complete 4.2 User Guide
CMTEUP_ServerDat
abase.
ServerDatabaseNa
me
126
Col
Field
Example
Req’d?
10/15/2015 09:00AM No
Description
Saved To
5
Do not
start
before
date
6
Suspend "true" or "false"
when
ready to
complete
.
Yes
Indicates if migration
should be suspended
before cutover.
7
Bad Item 10
Limit
No
Indicates how many bad
CMTEUP_Job.param_
mailbox items are allowed BadItem
before the migration is
Limit
failed. Must be a valid
number >= 0.
8
Large
Item
Limit
75
No
Indicates how many large CMTEUP_Job.param_
mailbox items are allowed LargeItemLimit
before the migration is
failed. Must be a valid
number >= 0.
9
Ignore
Rule
Limit
Errors
"true" or "false"
Yes
Indicates whether mailbox CMTEUP_Job.param_
rules should be moved to Ignore
target.
RuleLimitErrors
10 Do not 10/15/2015 09:00AM No
complete
before
date
Indicates when to
CMTEUP_Job.param_
complete the migration. If SuspendWhenReadyT
specified, must be a valid oComplete
date/time string AND
Suspend when ready to
complete must be "true".
11 Communi 0 or "en" or "English" No
cation
Language
Number or name of a valid CMTEUP_UserMailbo
culture. This must match a x.Culture
culture using CMTEUP_Cul ID
ture.CultureName, CMTE
UP_Culture.CultureDisplay
Name or CMTEUP_Culture.
CultureID. Addtionally,
E2E Complete 4.2 User Guide
Matched Against
Indicates when to start
CMTEUP_Job.DoNotS
migration, if not
tar
immediately. If specified, tBefore
must be a valid date/time
string.
CMTEUP_Job.param_
SuspendWhenReadyT
oComplete
127
Col
Field
Example
Req’d?
Description
Saved To
Matched Against
when specified CMTEUP_
UserMailbox.CultureIDLock
ed=1 is set to prevent
subsequent updates to this
value from the E2E
rationalization process.
12 Migration MyMigrationGroup1
Group
No
Name of a migration
CMTEUP_UserMailbo
group. This will either
x.Migra
match an existing group on tionGroupID
CMTEUP_
MigrationGroups.Migration
GroupName or create a
new group if no match can
be found.
13 Priority
No
Relative priority used to
schedule the mailbox
migration. Must be a
number between 1 and
100. If not specified, a
default priority of 10 is
used.
No
The name of a Blackout
CMTEUP_UserMailbo Matched Against
profile to use. This will
x.BlackoutProfileID
either match an existing
profile on CMTEUP_Black
outProfiles.BlackoutProfile
Name or create a new
profile if no match can be
found. If not specified, the
default blackout profile will
be assigned.
5
14 Blackout MyBlackoutProfile1
Profile
CMTEUP_UserMailbo
x.Priority
An example of a valid row in the CSV schedule file looks like:
[email protected],targetForest.dom,TargetDeliveryDomain.dom,Mailbox Database 12345678,0325-2014 04:12 pm,true,0,0,true,04-01-2014 05:52 pm,en-US,Group1,10,Profile 1,
E2E Complete 4.2 User Guide
128
CSV Cancel File Format
The CSV cancel file used to cancel mailbox migration jobs must meet the following requirements:

The file should not contain headers.

The file must include column 1: User Principal Name (UPN).
An example of a valid row in the CSV cancel file looks like:
[email protected]
To convert an Excel document to a CSV text file:
1.
Open your Excel file.
2.
Remove any existing header rows.
3.
Format all cells as text by selecting all columns and then right-click > Format Cells > Text.
4.
Save the document as a CSV.
Importing the CSV Schedule File of Mailbox Migration Jobs
To schedule or reschedule mailbox migration jobs by importing the CSV schedule file in the command prompt:
1.
Open a command prompt.
2.
Run C:\Program Files\Binary Tree\E2E\bin>BinaryTree.E2E.JobImporter /s [CSV schedule file].
3.
The schedule file is validated and saved to the database. If one or more error is encountered, no jobs are
saved.
To review and correct import errors:
1.
Errors will be displayed below the import command in the command prompt window.
2.
Optionally, you can run C:\Program Files\Binary Tree\E2E\bin>BinaryTree.E2E.JobImporter [CSV schedule
file] > OutputReport.txt to generate a text file containing the errors.
3.
Correct the errors in the CSV schedule file and attempt the import again. Optionally, you can validate the
CSV schedule file without importing the CSV schedule file (see steps below).
E2E Complete 4.2 User Guide
129
To validate the CSV schedule file without importing:
1.
In the command prompt, run C:\Program Files\Binary Tree\E2E\bin>BinaryTree.E2E.JobImporter /v [CSV
schedule file]
2.
The number of valid rows and rows with errors are displayed. The CSV schedule file is not imported.
To view the Help file:
1.
In the command prompt, run C:\Program Files\Binary Tree\E2E\bin>BinaryTree.E2E.JobImporter /? or /help
2.
The help message is displayed.
Cancelling Mailbox Migration Jobs using the CSV Cancel File
Mailbox migrations jobs can be cancelled using a CSV cancel file that contains a list of UPNs associated with
migration jobs.
To cancel mailbox migration jobs by importing the CSV cancel file in the command prompt:
1.
Open a command prompt.
2.
Run C:\Program Files\Binary Tree\E2E\bin>BinaryTree.E2E.JobImporter /c [CSV cancel file].
3.
The migration jobs for the UPNs are cancelled.
Usage Summary
BinaryTree.E2E.JobImporter [[/s <schedule file>] | [/v <schedule file>] | [/c <cancel file>]] [/?] or [/help]
/s <file> : Schedule (or re-schedule) mailboxes for migration. See JobImporter-ReadMe.txt for details on the format
of <schedule file>.
/v <file> : Validate the contents of <schedule file>. Any errors found are reported, but no migration jobs are
scheduled.
/c <file> : Cancel mailbox migrations for the list of UPNS found in <cancel file>.
/? or /help : Display this help message.
E2E Complete 4.2 User Guide
130
Appendix G: E2E Public Folder Job
Importer
The Binary Tree E2E Public Folder Job Importer utility is installed as part of E2E Complete. The utility will create a
job for each row of the input file. If a job already exists with the same source server name and folder path and same
target server name and folder path, the information from the input file will update the existing job instead of
creating a new one.
If the user elects to add subfolders for a given row, only subfolders that do not have a job will be added. The utility
will not update subfolder job settings based on a parent job.
When the utility creates a job and a user does not specify a value for an optional field, the utility will use the same
default as the Add folders to migration queue dialog.
CSV File Format (Scheduling New Jobs and Rescheduling Existing Jobs)
Col Field
Example
Req’d? Description
1
Source
folder
path
\TestFolder
Y
Path of job’s source
folder
CMTEUP_PublicFolder.
FolderPath
2
Source
folder
server
name
E2E-Ex10-1
Y
Server name where
job’s source folder
resides
CMTEUP_Server.ServerNam
e
3
Target
folder
parent
path
\
Y
Path of target’s parent
folder
CMTEUP_PublicFolder.
FolderPath
4
Target
folder
server
name
QA-E2E-EX10-1 Y
Server name where
job’s target folder
resides
CMTEUP_Server.ServerNam
e
5
Target
public
folder
mailbox
UPN
[email protected]
N (only UPN of mailbox
for
where target public
Exchg folder will reside
2013+)
6
Add or
Modify
True / False
N
E2E Complete 4.2 User Guide
Saved To
Matched Against
CMTEUP_PersonAD
Data.userPrincipalName
Specifies if importer
should add or modify
131
subfolder
jobs
jobs for subfolders.
Defaults to “true”
7
Sync
Seconds
30
N
8
Scheduled 3-25-2015 4:12 N
Start Date pm
Sets interval for sync
job. If value is 0 or
omitted, job will only
run ONCE
CMTEUP_PublicFolderJ
ob.SyncSeconds
Scheduled start date for CMTEUP_PublicFolderJ
the job. If omitted, then ob.ScheduledStart
defaults to current
time.
Example valid lines:
\TestFolder,E2E-EX10-1,\,QA-E2E-EX10-1,,true,0,3-25-2015 04:12 pm
\TestFolder,E2E-EX10-1,\,QA-E2E-EX13-1,[email protected],true,0,3-25-2015 04:12 pm
CSV File Format (Cancelling existing jobs)
Col Field
Example
Req’d?
Description
Saved To
Matched Against
1
Source folder \TestFolder
path
Y
Path of job’s source folder
CMTEUP_PublicFolder.
FolderPath
2
Source folder E2E-Ex10-1
server name
Y
Server name where job’s
source folder resides
CMTEUP_Server.Server
Name
3
Target folder \
parent path
Y
Path of target’s parent
folder
CMTEUP_PublicFolder.
FolderPath
4
Target folder QA-E2E-EX10-1 Y
server name
Server name where job’s
target folder resides
CMTEUP_Server.Server
Name
5
Target public pfmailbox@qa- N (only UPN of mailbox
folder
e2e.dom
for Exch where target public folder
mailbox UPN
2013+) will reside
6
Cancel
subfolder
jobs
True / False
N
CMTEUP_PersonAD
Data.userPrincipalName
Specifies if importer should
cancel jobs for subfolders.
Defaults to “true”
Example valid lines:
\TestFolder,E2E-EX10-1,\,QA-E2E-EX10-1,,true
\TestFolder,E2E-EX10-1,\,QA-E2E-EX13-1,[email protected],true
E2E Complete 4.2 User Guide
132
Command Line
Available command line switches:
BinaryTree.E2E.PFJobImporter [[/s <schedule file>] | [/v <schedule file>] | [/c <cancel file>]] [/? or /help]

/s <file> : Schedule (or re-schedule) public folders for migration.

/v <file> : Validate the contents of <schedule file>. Any errors found are reported, but no migration jobs are
scheduled.

/c <file> : Cancel public folder migrations for the list of folders found in <cancel file>.

/? or /help : Display this help message.
Example command line for scheduling (or re-scheduling) a set of public folder jobs:
BinaryTree.E2E.PFJobImporter.exe /s jobfile.csv
Sample output:
Example command line for cancelling a set of public folder jobs:
BinaryTree.E2E.PFJobImporter.exe /c jobfile.csv
Sample output:
Example command line for validating a set of public folder jobs:
BinaryTree.E2E.PFJobImporter.exe /v jobfile.csv
Sample output:
E2E Complete 4.2 User Guide
133
Appendix H: Public Folder Analysis and Job
Administration
This appendix provides scripts and information for managing public folder migrations and querying collected data
about public folders in E2E Complete.
To run the SQL scripts in this file, open SQL Server Management Studio and connect to your E2E
database. Right-click on the E2E database and select New Query to open the New Query window. Then
paste the SQL script into the query window, update the parameter values (if any), and execute the SQL
script.
Public Folder Analysis Scripts
For many of the public folder analysis scripts to function correctly, you must perform a public folder
content analysis on a forest at least once.
Below is a list of SQL scripts that can be used to query data collected about public folders. The SQL scripts can be
downloaded from the Binary Tree FTP folder where the GA E2E Complete install files and documentation are
located. Download the file SQL Queries.zip and extract the files to the SQL server being used for E2E Complete
public folder migrations. The following scripts are also available in the file PF Analysis Queries.sql. You can either
open this file in SQL Server Management Studio or copy and paste the query text below into a query in SQL. Some
of these queries need to be modified before executing. A good understanding of SQL is recommended before
proceeding.
Find the 10 largest public folders by folder size
To find the 10 largest public folder by folder size, run this SQL command:
SELECT TOP 10
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
f.[MaxPFSizeBytes]
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
ORDER BY f.MaxPFSizeBytes DESC;
E2E Complete 4.2 User Guide
134
Find the 10 largest public folders by item count
To find the 10 largest public folders by item count, run this SQL command:
SELECT TOP 10
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
i.ItemCount
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
INNER JOIN (SELECT PublicFolderID, COUNT(*) AS ItemCount FROM CMTEUP_PublicFolderItem
GROUP BY PublicFolderID) i ON f.PublicFolderID = i.PublicFolderID
ORDER BY i.ItemCount DESC;
Find public folders with more than x items
To find all the public folders with more than x items, run this SQL command (change "1000" to your own limit
number):
DECLARE @numItems INT
SET @numItems = 10000
SELECT f.PublicFolderID,
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
i.ItemCount
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
INNER JOIN (SELECT PublicFolderID, COUNT(*) AS ItemCount
FROM CMTEUP_PublicFolderItem
GROUP BY PublicFolderID) i ON f.PublicFolderID = i.PublicFolderID
WHERE i.ItemCount > @numItems
ORDER BY ItemCount DESC;
E2E Complete 4.2 User Guide
135
Find public folders where content has not changed in the last x days
To find all the public folders where content has not changed in the last x days, run this SQL command (change "90"
to your own value for "x"):
DECLARE @daysSinceLastContentChange INT
SET @daysSinceLastContentChange = 90
SELECT
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
f.[ContentChangeDate]
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
WHERE f.ContentChangeDate <= GETUTCDATE()-@daysSinceLastContentChange;
Find public folders where attributes have not changed in the last x days
To find all the public folders where attributes (e.g., permissions) have not changed in the last x days, run this SQL
command (change "90" to your own value for "x"):
DECLARE @daysSinceLastAttributeChange INT
SET @daysSinceLastAttributeChange = 90
SELECT
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
f.[AttributeChangeDate]
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
WHERE f.ContentChangeDate <= GETUTCDATE()-@daysSinceLastAttributeChange;
E2E Complete 4.2 User Guide
136
Find public folders where a specific user has any permission
To find all the public folders where a specific user has any permission, run this SQL command (change
“'[email protected]” to the user’s UPN):
DECLARE @userAnyPermission NVARCHAR(2000)
SET @userAnyPermission = '[email protected]'
SELECT
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
p.AccessRight
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
INNER JOIN [dbo].[CMTEUP_PublicFolderPermission] p ON f.PublicFolderID = p.PublicFolderID
WHERE p.TrusteeIdentity = @userAnyPermission;
Find public folders where a specific user has a specific permission
To find all the public folders where a specific user has a specific permission or role, run this SQL command (change
“[email protected]” and “Contributor” to the user's UPN and the permission or role you want to find):
DECLARE @user NVARCHAR(2000)
SET @user = '[email protected]'
DECLARE @permission NVARCHAR(100)
SET @permission = 'Contributor'
SELECT
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
p.AccessRight
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
INNER JOIN [dbo].[CMTEUP_PublicFolderPermission] p ON f.PublicFolderID = p.PublicFolderID
WHERE p.TrusteeIdentity = @user AND p.AccessRight = @permission;
E2E Complete 4.2 User Guide
137
Find Public Folders by email address
To retrieve a list of public folders by Email Address, run the following SQL command.
SELECT TOP 10
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
f.[Email]
f.[MaxPFSizeBytes]
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
ORDER BY f.MaxPFSizeBytes DESC;
Find Public Folders that have been processed by Content Analysis
To see a list of public folders that have been processed by the Content Analysis, run the following SQL command.
Select f.folderpath,f.email,f.targetaddress, j.starttime as ReportingJobStarted, j.endtime as
ReportingJobFinished
FROM cmteup_publicfolderreportjob j
INNER JOIN cmteup_publicfolder f
ON j.publicfolderid = f.publicfolderid
Find the 10 largest public folder items by item size
To the find the 10 largest public folder items by item size, run this SQL command:
SELECT TOP 10
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
i.ItemName,
i.ItemType,
i.ItemSize AS ItemSizeInBytes
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
INNER JOIN [dbo].[CMTEUP_PublicFolderItem] i ON f.PublicFolderID = i.PublicFolderID
ORDER BY i.ItemSize DESC;
E2E Complete 4.2 User Guide
138
Find public folder items larger than x MB
To find all the public folder items larger than x MB, run this SQL command (change "10" to the limit size, in MB):
DECLARE @sizeInMB INT
SET @sizeInMB = 10
SELECT
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
i.ItemName,
i.ItemType,
CONVERT(decimal(10, 3), (i.ItemSize / 1048576.0)) AS ItemSizeInMB
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
INNER JOIN [dbo].[CMTEUP_PublicFolderItem] i ON f.PublicFolderID = i.PublicFolderID
WHERE (i.ItemSize / 1048576.0) > @sizeInMB
ORDER BY i.ItemSize DESC;
Find total number of public folder items by item type
To find the total number of public folder items by item type, run this SQL command:
SELECT
[ItemType],
COUNT(*) As NumberOfItems
FROM [dbo].CMTEUP_PublicFolderItem
GROUP BY [ItemType]
ORDER BY [ItemType];
Find total number of public folder item attachments by type
To find the total number of public folder item attachments by type (extension), run this SQL command:
SELECT
[AttachmentExtension],
COUNT(*) AS NumberOfAttachments
FROM [dbo].CMTEUP_PublicFolderAttachment
GROUP BY [AttachmentExtension]
ORDER BY [AttachmentExtension];
E2E Complete 4.2 User Guide
139
Find total size of public folder item attachments by type
To find the total size of public folder item attachments by type (extension), run this SQL command:
SELECT
[AttachmentExtension],
SUM(AttachmentSize) AS TotalSizeInBytes
FROM [dbo].CMTEUP_PublicFolderAttachment
GROUP BY [AttachmentExtension]
ORDER BY [AttachmentExtension];
Find public folder item attachments larger than x MB
To find all the public folder item attachments larger than x MB, run this SQL command (change "10" to your limit
size, in MB):
DECLARE @attachmentSizeInMB INT
SET @attachmentSizeInMB = 10
SELECT
s.[ServerName],
f.[Name],
f.[EntryID],
f.[FolderPath],
a.AttachmentName,
a.AttachmentExtension,
CONVERT(decimal(10, 3),(a.AttachmentSize / 1048576.0)) AS ItemSizeInMB
FROM [dbo].[CMTEUP_PublicFolder] f
INNER JOIN [dbo].[CMTEUP_Server] s ON f.ServerID = s.ServerID
INNER JOIN [dbo].[CMTEUP_PublicFolderAttachment] a ON f.PublicFolderID = a.PublicFolderID
WHERE (a.AttachmentSize / 1048576.0) > @attachmentSizeInMB
ORDER BY a.AttachmentSize DESC;
Public Folder Job Administration Scripts
These PowerShell and SQL scripts can be used to manage public folder migrations. The SQL scripts can be
downloaded from the Binary Tree FTP folder where the E2E Complete install files and documentation are
located. Download the file SQL Queries.zip and extract the files to the SQL server being used for E2E Complete
public folder migrations. The following scripts are also available in the file PF Job Administration Queries.sql. You
can either open this file in SQL Server Management Studio or copy and paste the query text below into a query in
SQL. Some of these queries must be modified before executing. A good understanding of SQL is recommended
before proceeding.
E2E Complete 4.2 User Guide
140
Count folders in Exchange
To count the total number of folders in Exchange for a subtree (e.g. \RootFolder1), run thisw PowerShell command
from the Exchange server (change "\RootFolder1" to your root folder):
Get-PublicFolder –Recurse "\RootFolder1" | Select Name | Measure-Object
Count folders in E2E
To count the number of folders in E2E for a subtree (e.g. “\RootFolder1”), run the following SQL command (change
"\RootFolder1" to the desired root folder, and change "ServerID = 1" to the ID of the desired source server as found
in CMTEUP_Server):
SELECT COUNT(*) from CMTEUP_PublicFolder
WHERE (FolderPath like '\RootFolders\%' or FolderPath = '\RootFolders')
AND ServerID = 1
Find folder in Exchange
To look up a folder subtree in Exchange, run the following PowerShell command from the Exchange server (change
"\RootFolder1" to the desired root folder, and change "Server1" to the desired Exchange Public Folder server name):
Get-PublicFolder –Recurse "\RootFolder1" –Server "Server1"
Compare jobs and folders
To compare the number of folders in a subtree to the number of jobs created, run the following SQL command
(change "\2007Folders" to the desired root folder):
SELECT count(1)
FROM CMTEUP_PublicFolder
WHERE FolderPath like '\2007Folders%'
SELECT count(1)
FROM CMTEUP_PublicFolder fs
inner join CMTEUP_PublicFolderjob jt on jt.SourcePublicFolderID = fs.PublicFolderID
WHERE fs.FolderPath like '\2007Folders%'
E2E Complete 4.2 User Guide
141
Find all folders in source forest without Jobs
Change “airbus.corp” to the desired forest name:
SELECT f.FolderPath, *
FROM CMTEUP_PublicFolder f
inner join CMTEUP_Server s on s.ServerID = f.ServerID
inner join CMTEUP_Site i on i.SiteID = s.SiteID
inner join CMTEUP_Forest o on o.ForestID = i.ForestID
where o.ForestName = 'airbus.corp'
and f.FolderPath not in
(
SELECT DISTINCT(f.FolderPath)
FROM CMTEUP_PublicFolder f
inner join CMTEUP_PublicFolderJob j on j.SourcePublicFolderID = f.PublicFolderID
inner join CMTEUP_Server s on s.ServerID = f.ServerID
inner join CMTEUP_Site i on i.SiteID = s.SiteID
inner join CMTEUP_Forest o on o.ForestID = i.ForestID
where o.ForestName = 'airbus.corp'
)
Check folder provisioning progress
To check the folder provisioning progress for all jobs, run the following SQL command. See Appendix B for more
information on job states.
SELECT count(1) as JobCount, s.JobStatus, j.SyncCount
FROM CMTEUP_PublicFolderJob j
inner join CMTEUP_JobStatus s on j.JobStatusID = s.JobStatusID
WHERE j.SyncCount = 0
GROUP BY s.JobStatus, SyncCount
Sample Output
... which tells us that 8 jobs have been scheduled, but are not yet started, and 1 job folder sync has started (folder
creation and attribute sync).
E2E Complete 4.2 User Guide
142
Find empty folders
To find folders (with or without jobs) that don’t have any items, run the following SQL command.
SELECT f.FolderPath, f.ItemCount, f.ByteCount, f.PublicFolderID
from CMTEUP_PublicFolder f
where f.ItemCount = 0
order by f.ItemCount desc
Sample Output
Find empty folders with jobs
To find folders (with jobs) that don’t have any items, run the following SQL command.
SELECT f.FolderPath, s.JobStatus, f.ItemCount, f.ByteCount, f.PublicFolderID, j.PublicFolderJobID
from CMTEUP_PublicFolderJob j
inner join CMTEUP_JobStatus s on j.JobStatusID = s.JobStatusID
inner join CMTEUP_PublicFolder f on j.SourcePublicFolderID = f.PublicFolderID
where f.ItemCount = 0
order by f.ItemCount desc
Sample Output
E2E Complete 4.2 User Guide
143
Find Large Folders
To find folders (with or without jobs) that contain a large number of items, run the following SQL command.
-- The max number of folder items
declare @maxItems int = 500
SELECT f.FolderPath, f.ItemCount, f.ByteCount, f.PublicFolderID
from CMTEUP_PublicFolder f
where f.ItemCount > @maxItems
order by f.ItemCount desc
Sample Output
Find large folders with jobs
To find folders (with jobs) that contain a large number of items, run this SQL command.:
-- The max number of folder items
declare @maxItems int = 500
SELECT f.FolderPath, s.JobStatus, f.ItemCount, f.ByteCount, f.PublicFolderID, j.PublicFolderJobID
from CMTEUP_PublicFolderJob j
inner join CMTEUP_JobStatus s on j.JobStatusID = s.JobStatusID
inner join CMTEUP_PublicFolder f on j.SourcePublicFolderID = f.PublicFolderID
where f.ItemCount > @maxItems
order by f.ItemCount desc
Sample Output
E2E Complete 4.2 User Guide
144
Reschedule Large Folders
To postpone the processing of large folders, run the following SQL command.
NOTE: if this is run for jobs that have not yet finished provisioning, the provisioning process will also be
postponed. See script #3 to determine the state of the desired folders (change “2015-06-22” to the rescheduled
date and time):
-- The max number of folder items
declare @maxItems int = 500
-- The desired reschedule date
declare @rescheduleDate datetime2(7) = '2015-06-22'
update CMTEUP_PublicFolderJob
set ScheduledStart = @rescheduleDate
where PublicFolderJobID in
(
SELECT j.PublicFolderJobID
from CMTEUP_PublicFolderJob j
inner join CMTEUP_PublicFolder f on j.SourcePublicFolderID = f.PublicFolderID
where f.ItemCount > @maxItems
)
Find source folders with jobs not yet processed by change detection
select j.PublicFolderJobID, j.SourcePublicFolderID, sfs.ServerName AS SourceServerName, sf.Name AS
SourceName, sf.FolderPath AS SourceFolderPath, j.LastChangeDetectionDate, sf.ContentChangeDate AS
SourceContentChangeDate
FROM CMTEUP_PublicFolderJob j
INNER JOIN CMTEUP_PublicFolder sf
ON j.SourcePublicFolderID = sf.PublicFolderID
INNER JOIN CMTEUP_Server sfs
ON j.SourceServerID = sfs.ServerID
WHERE j.LastChangeDetectionDate IS NULL
Sample Output
E2E Complete 4.2 User Guide
145
Find Target Folders with Jobs not yet processed by change detection
-- Change detection only checks target folders if bi-directional syncing is enabled
declare @bidi INT
set @bidi = (select PFCoexistenceMode from CMTEUP_Settings)
select j.PublicFolderJobID, j.TargetPublicFolderID, tfs.ServerName AS TargetServerName, tf.Name AS
TargetName, tf.FolderPath AS TargetFolderPath, j.LastChangeDetectionDate, tf.ContentChangeDate AS
TargetContentChangeDate
from CMTEUP_PublicFolderJob j
INNER JOIN CMTEUP_PublicFolder tf
ON j.TargetPublicFolderID = tf.PublicFolderID
INNER JOIN CMTEUP_Server tfs
ON j.TargetServerID = tfs.ServerID
where j.LastChangeDetectionDate IS NULL AND @bidi = 1
Table Definitions
Below is a description of the noteworthy columns for the Public Folder and Public Folder Job tables.
CMTEUP_PublicFolder
This table includes all Rationalized public folders from the Source and Target forest:

PublicFolderID: Unique public folder ID

Name: Name of the public folder

FolderPath: Full Folder Path

ParentFolderID/ParentPath: These two columns will reference to the Parent Folder. If this reference is out
of sync, Child folder will not be visible in the UI.

AttributeChangeDate/AttributeChanged: Indicate when a folder attribute (proxy address, permissions) has
changed.

ContentChangeDate/ContentChanged: Indicate when new contents were added to the folder.

IsDeleted: This will be set to 1 if the folder was deleted.
E2E Complete 4.2 User Guide
146
CMTEUP_PublicFolderJob
This table includes all the Active public folder jobs. See CMTEUP_PublicFolderJobArchive for all complete jobs.

PublicFolderJobID: Unique Job ID for each job

ScheduleStart: This column determine when the job will be submitted by MCP service.

SourceServerID/TargetServerID: Identify the source and target Exchange Server

SourcePublicFolderID/TargetPublicFolderID: These two columns will reference the respective public folder
ID in the CMTEUP_PublicFolder table.

BiDirectional: Bi-Directional Setting

SyncCopy: True/false flag.

SyncCount: Number of times a Sync Copy has completed.

Result_ErrorMessage: Last Error message will be recorded here.

Result_ErrorCount: Number of Errors observed.

JobStatusID: Job Status description can be found in CMTEUP_JobStatus table.

LastChangeDetectionDate: The last time the change detection worker processed this job.
Job States
Public Folder Job Status
E2E Complete 4.2 User Guide
147
Public Folder Migration Job flow

Scheduled: Job has been scheduled, but not yet started.

Started: Folder sync (if necessary, create folder and sync folder attributes and permissions) has started.

Provisioned: Folder sync has completed and content sync is ready to start.

In Progress: Folder item copy has started.

Completed: Folder item copy is done.
Public Folder Migration Engine Folder Handling Notes
If the public folder does not contain any items, the public folder migration engine will skip the folder except when
Source to Target Content Deletes are selected to be synced in the E2E Public Folder Settings. If Source to Target
Content Deletes are checked then the engine will check for deleted items in source and delete them in target
accordingly.
E2E Public Folder Migration Child Job Management
When an administrator creates a public folder migration job using the E2E administrative UI or the public folder Job
Importer utility, E2E will check if a job already exists for the source folder or any child of the source folder. A child
folder will belong to the same forest as its parent and reside on the same server (or mailbox in the case of Exchange
2013). If a child folder with an existing migration job is detected (in the case of a drag and drop in the UI E2E will
display a warning dialog asking the user if they want to modify the child jobs) E2E will update the job’s target folder
and target server as well as the job’s sync interval and scheduled start fields. Finally, E2E will reset the modified job’s
status to Scheduled and its sync count to zero (0).
E2E Complete 4.2 User Guide
148
Appendix I: E2E Connectivity Test Results
Section
Error Result
MAPI Connection IMsgServiceAdmin::ConfigureMsgService:
and Profile
MAIL_E_NAMENOTFOUND (or WSAECONNRESET)
Probable Causes
User name is incorrect. A mailbox for the
specified user cannot be found
IMAPISession::OpenMsgStore:
MAPI_E_FAILONEPROVIDER
The Exchange Server is offline
IMsgServiceAdmin::ConfigureMsgService:
MAPI_E_NETWORK_ERROR
Exchange server name is incorrect or
cannot be resolved.
The Exchange Information Store is offline
User name or password is incorrect.
Exchange 2010 Address Book service is
not running
Hosted Exchange MAPIConnectHosted:
GetAutodiscoverForEmailAddress: There are no
autodiscover servers in the AD for this address
MAPIConnectHosted: Error in
IMAPISession::OpenMsgStore:
MAPI_E_LOGON_FAILED
The Exchange Server is offline
User name or password is incorrect
Password has expired
Certificate issue
E2E Complete 4.2 User Guide
149
Appendix J: Mailbox Permissions Migrated
When a mailbox is submitted for migration, the Submit Pending Jobs activity will read the following mailbox
permissions:
Exchange Permissions:
ChangePermission
DeleteItem
ReadPermission
ChangeOwner
FullAccess
Send On Behalf
NT Permissions:
Send-As
Receive-As
Mailbox Folder Permissions:
All mailbox folders
All trustees, except Default and Anonymous
All rights including: Owner, PublishingEditor, PublishingAuthor, Editor, Author, NoneditingAuthor,
Contributor, Reviewer, CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems,
FolderContact, FolderOwner, FolderVisible and ReadItems
Mailbox folder permissions are automatically migrated by Exchange. However, to enable Exchange to do
so successfully, the following must be done prior to moving the mailbox:

For Resource Folder migrations the msExchMasterAccountSID must be set on each target trustee
before moving the user.

For non-Resource Forest migrations an X500 address must be added to each source trustee that
points to the target trustee before moving the user.
Once the mailbox migration has completed, the permissions found in the CMTEUP_UserMailboxPermissions table
are processed. For each permission, the trustee is opened in the Source AD and a matching Target trustee is located
using:
Mailbox GUID
E-Mail
Primary SMTP
Common Name
sAMAccountName
If no match is found, the MCP waits and retries applying the permission. This retry process can be configured in the
Mailbox Settings with the Mailbox Permissions Retries setting.
E2E Complete 4.2 User Guide
150
Appendix K: Updating Outlook 2003
Clients for Inter-Org Migrations
When executing an Inter-Org migration, an Outlook client loses its association with the user’s mailbox. While
Outlook 2007, Outlook 2010 and Outlook 2013 automatically reconfigure through the AutoDiscover service, Outlook
2003 does not have this ability.
System Requirements

NET 2.0

Outlook 2003 client

The UAC (User Account Control) must be set to Never notify in User Accounts on each end user’s machine
for OPUS to work. OPUS needs to update the registry and this will fail if the user does not have the proper
permissions.
The Outlook Profile Update Service (OPUS)
The Outlook Profile Update Service (OPUS) is included with E2E Complete. OPUS can be executed at the
workstation’s startup to detect whether this Outlook client should be updated. In interactive mode, OPUS prompts
for the URL to the E2E Complete User Portal, and gives you the option of defining a particular CAS. OPUS uses this
information to reconfigure your Outlook 2003 profile, if the migration of the user has successfully completed.
The following are two ways that OPUS can be executed:
1.
End User execution of OPUS using the GUI wizard mode.
2.
The Administrator can choose to execute OPUS via the command line. A silent update mode can be used to
update an Outlook profile without a UI. However, a prompt for credentials will still be shown if one is
needed.
BinaryTree.E2E.OPUS /silent /endpoint {E2E server endpoint (optional)} /server {mailbox server name
(optional)}
If updating Outlook 2007, Outlook 2010, or Outlook 2013 clients Inter-Org, consider:

Every time Outlook 2007/2010/2013 launches, it reads in the location of the mailbox as stored in its profile
and tries to re-open this connection. That host server accepts the connection and serves the mailbox
content, or it uses an Exchange mailbox referral process to redirect the client request to a different mailbox
server within the organization. However, in this case the mailbox has been moved outside of the existing
Exchange organization. Failing to find its mailbox in the organization, Outlook queries the TargetAddress
attribute of its profile user.

When a mailbox is migrated by E2E Complete, the TargetAddress value in the source forest is updated so
that it now points to the target forest. Outlook 2007/2010/2013 then makes a query to
autodiscover.target.com and identifies itself to this target organization by forwarding its mailbox GUID.
Outlook is then successfully directed to an appropriate Client Access Server and is connected to the users
migrated mailbox. This process occurs without any agents or additional processing required.
E2E Complete 4.2 User Guide
151
End-User Execution of OPUS
End users who have access to the E2E server endpoint can execute OPUS through a GUI wizard. They will receive an
email with a link that lets them download and run OPUS.
Exchange 2013 does not support Outlook 2003.
To execute OPUS:
1.
Click Next to begin the E2E Outlook profile update service process.
2.
Enter the E2E Endpoint information on the screen and click Next to continue.
E2E Complete 4.2 User Guide
152
3.
Click Next to update your Outlook profile.
4.
The following screen displays when E2E is updating your Outlook profile.
E2E Complete 4.2 User Guide
153
5.
If the mailbox information cannot be found, the following screen displays. Otherwise, this screen does not
display.
6.
If Outlook is open, it will close and re-open with the new profile. Click Finish to complete the process.
E2E Complete 4.2 User Guide
154
Command line execution of OPUS
This section details the Administrator process to execute OPUS via the command line when end-user client
machines do not have connectivity to the E2E server endpoint or when the Administrator prefers that the end users
have no interaction with the process.
From the command prompt, navigate to c:\Program Files\Binary Tree\E2E\Downloads and run the
BinaryTree.E2E.OPUS command with the following parameters.
BinaryTree.E2E.OPUS
/silent
/oldservers {comma-separated list of source mailbox servers}
/server {target mailbox server name}
/cas {target CAS server name (optional, defaults to same as /server)}
This parameter is necessary only when the CAS server name differs from the mailbox server
name (/server parameter).
This parameter is necessary only when the subject of the SSL certificate on the CAS server differs
from the CAS server name (/cas parameter).
/upn {user principal name (optional, defaults to existing upn in profile)}
This parameter should be omitted if the intent is for this to be used for multiple users. OPUS will
maintain the same user name that was created in the profile before migrating, if this parameter
is omitted
This allows bulk updates of many Exchange 2003 client machines, without customizing the .config file for a specific
UPN without access to the E2E web service, and also allows specification of multiple source servers.
Allowing for local override when E2E web service is
unavailable
There are circumstances where the client box that needs to upgrade an Outlook 2003 profile has no access to the
E2E box and cannot resolve the web service endpoint.
The BinaryTree.E2E.OPUS.exe.config file for OPUS located in c:\ProgramFiles\BinartyTree\E2E\Downloads typically
looks like this:
<applicationSettings>
<BinaryTree.E2E.OPUS.Properties.Settings>
<setting name="E2EEndPoint" serializeAs="String">
<value/> (notice the absence of this value)
</setting>
</BinaryTree.E2E.OPUS.Properties.Settings>
</applicationSettings>
E2E Complete 4.2 User Guide
155
To override the remote configuration in favor of a local one, the .config would look like this:
<applicationSettings>
<BinaryTree.E2E.OPUS.Properties.Settings>
<setting name="E2EEndPoint" serializeAs="String">
<value /> (notice the absence of this value)
</setting>
<setting name="MailboxServer" serializeAs="String">
<value>Ex2010-mbx.contoso.com</value>
</setting>
<setting name="CASServer" serializeAs="String">
<value>Ex2010-cas.contoso.com</value>
</setting>
</BinaryTree.E2E.OPUS.Properties.Settings>
</applicationSettings>
<userSettings>
<BinaryTree.E2E.OPUS.Properties.Settings>
<setting name="UserPrincipalName" serializeAs="String">
<value>[email protected]</value>
</setting>
<setting name="SourceMailboxServer" serializeAs="String">
<value>Ex03legacy.contoso.com</value>
</setting>
</BinaryTree.E2E.OPUS.Properties.Settings>
</userSettings>
The following table provides a description for each OPUS application configuration setting.
Name
Description
E2EEndPoint
A URL to the E2E server for your installation. http://server.contoso.com/e2e/user/default.aspx
MailboxServer
The name of the new (target) Exchange
mailbox server.
CASServer
The name of the new (target) Exchange CAS Ex2010CAS.contoso.com
server. Defaults to the MailboxServer if not
supplied.
UserPrincipalName The UPN (alias) of the mailbox user.
Example
Ex2010MBX.contoso.com
John.smith
SourceMailboxServer The name of the source Exchange mailbox Ex2003.contoso.com
server as found in the user’s Outlook profile.
For the E2EEndPoint setting, the URL is only needed if the administrator is not providing all of the setting
values for OPUS.
E2E Complete 4.2 User Guide
156
">