ST PST files with size exceeding the PST file contents size limit value may still be migrated, since Migration Manager checks the currently processed file size only after each items. For more information about the LmCompatibilityLevel parameter, see the article available at http: This also applies to the Calendar Synchronization Agent.
When clocks are adjusted for autumn daylight saving change, then files created during 1 hour after adjustment may be processed the incorrect order, because files order by the date modified parameter does not match the actual order by files creation. It is not recommended to perform initial synchronization during this time period. ST Mailbox Synchronization After a mailbox move operation or the creation of a new Exchange mailbox during the migration process, the mailbox does not immediately become available for login.
The Mail Target Agent will record login errors until the mailbox is ready this can take up to 20 minutes. In these situations, login errors can be safely ignored. To workaround the issue, set the option value to more than 0. ST , ST If a mailbox is processed by the agents in a job, and then you add the mailbox to another job with a different target server, Mail Target Agent may experience the following error when logging in to the mailbox: Your profile is not configured.
The issue is resolved automatically after several unsuccessful logon attempts. This may be caused by excessive size of the 0x61AF property value. If you encounter this issue, contact Quest Support. ST Mail agents may not work correctly if the target Exchange x mailbox is modified before the mailbox switch.
The mail agents will consider such appointments to be in sync. This is how Exchange x works. The workaround is to set the target mailbox size limit not less than the size limit of the source mailbox or set it after migration is completed.
This is an issue with Outlook Web Access. ST Migration of public folder rules is not supported for Exchange Server. ST Mail-enabled root public folders become mail-disabled after the synchronization.
ST Folder hierarchy synchronization may fail, if more than 40 rules are assigned to one of the folders and folder size exceeds KB.
ST Irrespective of the type of the source synchronization root folder, the folder is copied to the target server as an IPF. It is recommended that the network administrator manually create the 'Aelita EMW Recycle Bin' folder and replicate it to all the organization servers involved in the public folder synchronization.
The agents automatically create this folder, but it is not replicated to other servers. The information about user-defined views is stored in the mailbox and is not synchronized by the Migration Manager agents. The user will have to configure the views for each public folder again after mailbox switch. During two-way synchronization, the deleted source messages will be moved to the source folder corresponding to the target folder where the messages were moved.
During one-way synchronization, only the target messages will be moved. During two-way synchronization, the modifications made on the source folder will be applied to the target folder, and the modifications made on the target folder will be applied to the source folder. During one-way synchronization, the modifications made on the source folder will be applied to the target folder, and the agent will consider the folders to be in sync.
During one-way synchronization, the messages will be duplicated on the target only. The root folder you specify for a public folder synchronization job and all its subfolders should be replicated to the agent's server.
This public information store should be associated with the private information store where the Administrator mailbox resides. The setting can be verified in the properties of the Private Information Store.
Otherwise the folder created by the agents will be invalid and may be inaccessible. Also the same warning will be displayed, if Global Catalog server does not exist in the domain in which Exchange server is located. ST If a source public folder has no local replica on the server involved in synchronization but is included in the collection, its deletion will be synchronized even though the folder cannot be synchronized.
That is, the corresponding target public folder will be deleted by the agent. For more information, see the Microsoft KB article available at http: ST Calendaring agent may fail when processing mailboxes synchronized by the Calendar Synchronization Agent.
Error message will appear in the Event log. ST If a two-way calendar job is set up after a one-way calendar job began running, the calendar synchronization agent will copy to the source all the target messages, including those already synchronized. The Calendar Synchronization Agent will then synchronize these appointments. Thus, appointments created in different environments may result in different resource request items in the resource mailbox's schedule.
The Calendar Synchronization Agent will synchronize such a deletion and the item will be lost. Once deleted, the folder cannot be restored due to the tombstone created by Exchange Server. When the user logs on to the target mailbox, he or she will not see the appointments. The appointments will be later synchronized by the agent to the new mailbox. The mailbox in the old store will be marked as reconnected and assigned to both the old and the new information stores.
This mailbox cannot be purged. To avoid this, configure calendar synchronization jobs for two-way synchronization. The workaround is to restart the Calendar Synchronization Agent. ST Public Folder Rules Synchronization The Forward to public folder rules are not synchronized correctly, if the corresponding target folder is not mail-enabled.
ST , ST Source public folder rules that forward mail to an address of a synchronized source object do not work after the migration. ST If any link in a rule's conditions such as 'From: For more information, please see the Microsoft article at t http: If a mailbox is explicitly added to a collection and the collection is disabled, the mailbox will be skipped during processing of all other collections in which this mailbox is also a member, no matter if the collection is enabled or disabled.
For more information on full resynchronization, please refer to the appropriate Quest Migration Manager documentation. This behavior is by design. ST If a mailbox is moved in the target organization using native Exchange management tools while the mailbox is being processed in a Remote Users Collection, the Mail Source Agent will not be able to copy the contents of the source mailbox to the target mailbox.
The error is resolved automatically in the next session. To recreate this mailbox, you will have to first remove it using Exchange Tasks and then perform a full directory resynchronization. Otherwise, when a full resynchronization is performed for an ordinary collection that includes such a mailbox, all messages created by the user when working offline and copied by the mail agents from the source mailbox to the target mailbox will become conflict messages after the target mailbox has been synchronized with the OST file.
The issue relates to Exchange mailboxes only. If a remote user works offline, Favorites may still be present. However, as soon as the user synchronizes OST with his or her mailbox, the Favorites will be lost. If a user is working online, Microsoft Outlook will not operate while the mailbox is being processed. After mailbox processing has been completed, a user must log off and log back on to the mailbox. For example, if the agent was scheduled not to work from 1 am through 6 am and at 1 am the agent is processing a mailbox, it will not stop until the mailbox processing completes.
Otherwise, the MSA will repeatedly attempt to copy the source mailbox to the target server when migrating a mailbox within a Remote Users Collection. If the mailbox size limit has been exceeded, the mailbox will not be copied to the target server. The mailbox profile will not be updated if you switch this mailbox within a regular collection. The following error will appear in the Mail Source Agent log file: OpenMailbox Error File: To workaround the issue, specify correctly Mailbox Migration Administrator Mailbox for Exchange server you work with and perform the Undo Switch operation from the Migration Manager console for affected mailboxes.
ST Using Alternate Hosts If two Exchange servers use the same alternate host, you cannot set separate switch notification for each Exchange server. ST If you plan to set up an alternate host for migration to Exchange , use a computer with bit Windows Server This requirement is due to the Exchange Attendant component. This component uses Exchange Administrative Tools, which support only the bit architecture and cannot be installed on Windows based computers.
ST If you set up an alternate host server for an Exchange CCR Cluster server for the first time, all configuration data related to synchronization jobs will be deleted from the configuration databases located on the active cluster node only. After that the agent must be started and changes of configuration data related to synchronization jobs must be replicated successfully to the passive node as well to avoid processing of synchronization jobs using obsolete configuration data in case of unexpected failover.
ST If during two-way public folders synchronization either of the following changes related to alternate hosts associated with the Exchange servers are made: The same host server is configured for both source and target Exchange servers Source and target Exchange servers associated before with the same host server, are configured not to use this host server as common, then Public Folder Target Agent may process the PUB files with the PSTFile:: PUB' was not found error displayed in the log file, because such files were created before configuration changes described above.
To workaround the issue, delete these PUB files manually and perform resynchronization if needed.