Chat now with support
Chat mit Support

Metalogix Essentials for Office 365 2.8 - User Guide

Tool Overview
General Tool Configuration Profile Manager Proxy Mode Azure Turbo and CSOM Creating User Mapping Creating User and Template Reports Support and Troubleshooting Activation Modes of Migration
Home Tab Migration Analysis Tab Migrator Tab
Interface Connect to Resources Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts In-Place Tagging of SharePoint Items Incremental and Delta Copy Forms Migration Workflow Migration Save Site to XML
File Manager Tab Drives Tab
Interface Overview Migration Job Structure Connecting to Resources Copy Google Drive Copy File Share Copy My Sites to OneDrive for Business Copy Tenant Copy Box Copy Dropbox Nintex Deployment
Security Manager Tab Term Store Manager Tab Administrator Tab Backup Tab
Interface Overview Backup Job Structure Advanced Search Retention Policies Storage for Backup Import/Export Backup Archives Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper vs Classic Backup Setup Hyper SharePoint Online Backup Hyper OneDrive Backup Hyper Office 365 Groups Backup Smart Backup Classic SharePoint Online Backup Classic OneDrive Backup Classic Office365 Groups Backup Classic Mailbox Backup Change Properties for Backup Admin Management Scheduling Backup Jobs Backup Project Conversion
Help Tab View Tab Architect Tab Public Folders for SharePoint Tab Informant Tab Scripts Appendix

Hyper Mode FAQ's

What is hyper migration?

Hyper migration uses parallel threads that the tool will run to read from the source and then upload to the target. The default number is 35. This value is used for both 'Read from source' and 'Write to target' operations while in CSOM mode, and only for Read operations when in Azure Turbo mode.

 

What migration path does hyper migration support?

Migrate SharePoint Online sites (Classic Team Sites and Modern Team Sites - not connected to Office 365 groups) between tenants.

 

Does hyper migration support OAuth?

OAuth is only supported for Hyper Migration and Hyper Backup.

 

Does hyper migration support GCC High tenant?

Support in hyper migration for GCC High Tenant using OAuth via claims connection was added in the 2.5 release.

OAuth Framework Authentication

In order to use OAuth Framework Authentication, you must have Metalogix Essentials installed on the tenant where you plan to use OAuth. Please note: OAuth Framework Authentication only works in Hyper Mode for Hyper Migration and Hyper Backup.

OAuth is enabled by default upon installation of Essentials - if you have left OAuth enabled, start with step 4, in the event that you have manually disabled OAuth, start with Step 1: :

1.In Essentials, select that Help tab, and then click Profile Manager.
oauth01

2.Select Migration from within the Profile Manager and Navigate to Hyper Mode Settings.
 

3.Oauth is enabled by default when Essentials is first installed, unless you have manually disabled it previously.
oauth enabled 1

4.Open any hyper migration wizard or the Drives' tab Connect to Office 365 wizard. When connecting to a tenant (source or target) that does not have OAuth authenticated, you will be asked if you would like to authenticate the app upon clicking Connect in the connection portion of the wizard.
connect Oauth1

info

NOTE: If the tenant you are connecting to already has OAuth authenticated you will not be required to authenticate again, and therefore can skip the following authentication steps.

5.Once prompted whether you want to authenticate OAuth for this tenant, Select OK. In the window that opens, log into the tenant. 

6.Give the app permissions.
oauth5

7.Once you have completed the above steps, the App is added and you will not need to repeat this process again for this tenant.
oauth6

info

NOTE: the application must be added to all tenants if you want to use OAuth (source and target tenant).

Users will be able to see if Oauth is being used, as It will be indicated on the connection wizard.
oauth8

OAuth and Claims

By Default, the Essentials tool uses Classic Office365 Authentication. After your credentials have been provided (claims or direct), Essentials uses the generated cookies in various requests. This method of work is similar to the one used when logging into a browser with credentials - it works well for small activities but does not work well when performing bulk operations, as Office365 is throttled a lot in this scenario.

 

OAuth authentication uses bear tokens when working with SharePoint. This token is generated by the App, which was added to the tenant. This form of performing allows Essentials to avoid throttling during bulk migrations.

 
Work with OAuth and Claims

Once you have performed the steps in the previous topic, to set up OAuth, continue with the following steps to set up OAuth with Claims:

 

1.Navigate to the Drives tab and open a migration wizard (in this example we use the OneDrive to OneDrive migration wizard).
copy one drive to one drive 1

2.In the wizard, provide a URL for the source and click Connect. Within the Connect to SharePoint window enter your credentials and click Connect.
oauth and claims 6

3.Provide a URL for the target, and click Connect
oauth and claims 6

4.Within the Connect to SharePoint window, click Claims.
oauth and claims 7

5.In the window that opens, login to the tenant.
oauth and claims 3

6.Consent to the permissions and click Accept.
oauth and claims 4

7.A dialogue box for the connection to the required services is opened. Login with your user information, click Connect.
oauth and claims 5

8.Complete your work within the Copy Tenant wizard and begin your migration.

info

NOTE:

·If you have already installed the Essentials application in the tenant, you will still get two connection dialogues. This will simply give the tool the ability to check all the settings.

·If you do not use OAuth but use Claims, you will still be asked to log in twice, because the tool uses various services and we require authentication for these services.

OAuth Limits

info

NOTE:

·OAuth is only supported for Hyper Migration and Hyper Backup.

·OAuth doesn’t work with SSO.

·"resume" will automatically use the original mechanism of authentication when resuming a job.

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen