The Public Folder Jobs view lets you manage the sequence of migration requests for the selected migration destination.
Migrator Pro for Exchange 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 the target, and a different \folderA\folderB already exists:
The above options have no effect on Active or In-Progress migration jobs.
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.
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.
Migrator Pro for Exchange 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.
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, Migrator Pro for Exchange will not mark them all as deleted. A message stating the number of returned folders will appear in the log.
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.
Indicate the settings you want to apply to the job by selecting the options on the screen:
The settings on this screen:
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.
Migrator Pro for Exchange 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.
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. Migrator Pro for Exchange 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 Migrator Pro for Exchange’s Office 365 Forest Configuration Settings screen.
To migrate public folders to Office 365 Groups using MAPI:
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.
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:
Once Submit is clicked, Migrator Pro for Exchange assigns reporting jobs to any worker with the Reporting role. You can assign a worker to the Reporting role from the Workers tab.
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.
By default, with Migrator Pro for Exchange 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:
The fields on this screen:
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 Migrator Pro for Exchange 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.
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.
The User Portal web page can be customized by modifying the C:\Program Files\Exchange Pro\User\Default.aspx configuration file that resides on the Migrator Pro for Exchange server. For example, an administrator may want to hide the Outlook Profile information that appears on the User Portal page after a migration has completed:
If you want to hide that information, you can comment out the OutlookProfile ID line in the Default.aspx file. The line appears like this (marked by the red arrow) by default:
To comment out this line, add the "%" character at the beginning and end of the line:
<%--<uc3:OutlookProfile ID="OutlookProfile1" runat="server" />--%>
If the online browser-based Help doesn’t load correctly after an Migrator Pro for Exchange upgrade, clear the temporary files in the browser. We recommend you set your browser to clear temporary files and history upon exit.
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.
There's an issue with Migrator Pro for Exchange when you try to implement a new production license key after running Migrator Pro for Exchange 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.
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.
Clear the targetAddress for any target mailbox when this occurs.
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.
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 Migrator Pro for Exchange SQL database and can be done with the following query:
delete FROM [ ].[dbo].[BT_TracDoc]
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책