Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration for Email Current - User Guide

Introduction Preparing Migrations Test and Pilot Migrations Configuring and Running Migrations Post Migration Third Party Assessments and Certifications Glossary

Client Profile Updating Utility

Consider the following limitations when using ODME together with Client Profile Updating Utility (CPUU):

  • Migration from Exchange/Microsoft 365: ODME needs that the target Autodiscover service is functioning correctly in order to put the hidden "switch message" for CPUU. The requirement is actual regardless of whether the Use Autodiscover option is enabled or not on the plan’s Connections page.

  • CPUU does not process shortcuts for folder in other user mailboxes and Public Folders due to the following reasons:

    • Public Folder migration is not supported.

    • There is no matching information for source and target users.

  • CPUU does not process Contact folders in Public Folders because the migration of Public Folders is not supported.

  • CPUU does not process address books in other user mailboxes because there is no matching information for source and target users.

  • CPUU does not process recipients, folders in other mailboxes and Public Folders, and links to reply templates due to the following reasons:

    • There is no matching information for source and target users.

    • Associated content is not migrated.

    • Public Folder migration is not supported.

  • CPUU does not update names of Public Folders because the migration of Public Folders is not supported.

  • CPUU does not process Folder Views which have filtering by the From and Sent To attributes because there is no matching information for source and target users.

  • CPUU does not process Search Folders which have filtering by the From and Sent To attributes because there is no matching information for source and target users.

  • These following CPUU features are not supported because there is no matching information for source and target users: "Other User's Folder Shortcuts", "Delegates", "Additional Mailboxes", "Distribution Lists", "Contact Nicknames".

  • This "Group Schedules" feature is not supported due to the following reasons:

    • There is no matching information for source and target users.

    • Associated content is not migrated.

    • There is no matching information for messages.

  • The "Preserve Offline folders (OST files)" feature is not supported. Offline folders are recreated after the mailbox switch.

  • To enable the CPUU integration feature on the source Exchange Server 2007, you should turn on and configure the WebDAV API access for your Exchange Server 2007.

To configure ODME to work together with CPUU, please see http://documents.quest.com/on-demand-migration-for-email/user-guide/configuring-and-running-migrations/selecting-migration-options/updating-outlook-client-profiles.

For the full list of CPUU features, refer to http://support.quest.com/technical-documents/client-profile-updating-utility/5.7.4/administration-guide/.

Microsoft Exchange

General

  • When viewing migrated data in OWA, there may be slight differences in the received time of emails when comparing the source to the time recorded in the target. This affects all Exchange source environments and Exchange 2013/2016/2019 target email services.
  • When migrating from an Exchange server, any email addresses associated with existing users will be converted to SMTP addresses based on the source system. This means that X500 addresses will not be migrated for items, and the SMTP address on the migrated items will not be updated to the new SMTP address. In order to get Exchange to update to the new address the primary SMTP address on the source system should be an alias on the target system.
  • For appointments migrated from Exchange 2007 to Microsoft 365, the acceptance date on the target will be the date/time of the migration. Also, appointment owners will see “invitation not sent” for appointments with multiple attendees.
  • For Exchange-based targets, Groups are treated as Distribution Lists and cannot contain a contact with no email address. Because of this, any group members that do not have an email address on the source will not be migrated as a member of that group on an Exchange/O365 target. The contact will still migrate, it just cannot be a member of a group without an email address.
  • InfoPath items are not migrated from Microsoft 365 and Exchange server.

Rules

For information about the supported types of rule's condition or action, see Migrating Rules.

  • For the source Exchange 2010, ODME migrates OWA Inbox rules only to the target, and:
    • Rules with the action "Delete message" will have the option Stop processing more rules selected on the target after migration.
  • Autodiscover must be enabled on your target for successful rules migration.
  • During the migration, the name of a group participating in a source rule will be converted to an SMTP email address. The address is retrieved from the mailbox list of the migration plan, and will be used in the corresponding target rule.
  • Migration of rules from or to personal archives is not supported.

Delegates

  • Migration of security groups as delegates is not supported for Exchange 2013 or earlier.
  • For migrations from Exchange server and Microsoft 365, migration of customized set of delegate permissions is currently not supported:
    • Custom folder permissions are migrated as None (lack of any permissions) when the target delegate does not exist.
    • In case when the target delegate exists, source and target delegate permissions are merged and the predefined Roles (Editor, Author, Reviewer and None) take precedence over any Custom permission set.
    • In case when the target delegate exists and both source and target permissions are set to Custom, the target permissions will be set to None.

    See Migrating Delegate Access Permissions for details.

Folder Permissions

  • Migration of folder permissions for Recoverable Items is not supported.

  • Migration of folder permissions from personal archive and to personal archive is not supported.

Microsoft 365

General

  • If a user's Calendar is shared with people outside the organization, On Demand Migration for Email migrates shared Calendar permissions only for internal users and ignores users outside the organization.
  • The Use Modern Authentication option is supported for connections to the Microsoft 365 Worldwide. The option is not supported for connections to the Microsoft 365 hosted in the Germany, China or US Government environments (Microsoft 365 GCC High).
  • For Microsoft 365/Exchange 2010, or Microsoft 365/Exchange 2013, or Microsoft 365/Exchange 2016, or Microsoft 365/Exchange 2019 hybrid deployments, if your Microsoft 365 configuration utilizes a shared domain configuration, On Demand Migration for Email will not able to locate your mailboxes.
  • InfoPath items are not migrated from Microsoft 365 and Exchange server.
  • ODME does not migrate retention policies and retention tags from one Microsoft 365 tenant to another Microsoft 365 tenant.

  • ODME does not migrate some Contact fields from G Suite to Microsoft 365.
    Fields that are currently supported:

    • Name

    • Job title, Company

    • Phone Numbers

    • Picture

    • Notes

    • Email Address

    • IM

    • Birthday

    • Relationship

    Custom G Suite fields that cannot be migrated from G Suite to Microsoft 365:

    • Phonetic Last

    • Phonetic First

    • URL

    • Internet Call

    • Custom Fields

Rules

See the Rules section of Microsoft Exchange.

Delegates

  • Migration of security groups as delegates is not supported for Exchange 2013 or earlier.
  • For migrations from Exchange server and Microsoft 365, migration of customized set of delegate permissions is currently not supported:
    • Custom folder permissions are migrated as None (lack of any permissions) when the target delegate does not exist.
    • In case when the target delegate exists, source and target delegate permissions are merged and the predefined Roles (Editor, Author, Reviewer and None) take precedence over any Custom permission set.
    • In case when the target delegate exists and both source and target permissions are set to Custom, the target permissions will be set to None.

    See Migrating Delegate Access Permissions for details.

Folder Permissions

  • Migration of folder permissions for Recoverable Items is not supported.

  • Migration of folder permissions from personal archive and to personal archive is not supported.

POP/Windows Live Hotmail

  • Only content located in the source inbox is accessible and migrated.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation