Chat now with support
Chat mit Support

Metalogix Essentials for Office 365 2.9 - 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 Hyper Mode Classic Mode Copy Alerts Orphaned Users Copy 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

Supported Specification for Essentials Azure Turbo Mode

Essentials' Azure Turbo Mode utilizes Microsoft API, as Microsoft updates the API for both optimization as well as additional support, so too will Essentials be updated.

Currently supported and required:

·Azure Storage Account

oAn Azure Storage Account of your own is required.  If you already have a subscription then you can utilize it, however if you do not this may require an additional license that would be purchased from Microsoft.  Some Office 365 plans include Azure Storage, so check with your Plan or IT manager first.

·Content Only (but the rest still migrates too)

oThe SharePoint Online Migration API at this time is designed to handle content and content related attributes (metadata and item permissions) only.  Site creation, permissions, views, workflows, content types and countless other objects that makeup SharePoint will still be created using a number of other available APIs outside of this new functionality.  This means you should not expect to see an increase in performance around these other objects, but they will still be migrated the same as they were before or without the Azure Turbo Mode option.

·Queue Times and Processing

oWe don’t control the process, order or operation of the Azure queue.  Once Essentials submits the job to the queue, it has been completely handed over to the Microsoft function and we no longer have any ability to predict the order or processing times of any job.  In fact, once the Essentials log appears letting you know they have been queued, you can shut down our application and the queue will still process in Azure.  This means the job may immediately be picked up and processed or it may sit and wait for its turn before beginning (could be minutes or hours).

·File Size Limitation

oAt present the SharePoint Online Migration API only supports files up to 15GB in size.

Synchronous and Asynchronous mode

Users can select whether Azure Turbo Process is performed in Synchronous or Asynchronous mode. To change this setting to one or the other, do the following:

1.Within Essentials, go to the Help tab, and select Profile Manager.
azure turbo and csom 3

2.In the profile manager, navigate to Global Variables, and use the drop down beside the Azure Turbo Process option to select Synchronous or Asynchronous.
asynchronous mode 1

When in Asynchronous mode, the job is reported as finished when all packages created from the source are uploaded to Azure, and added to the import queue. The job completion is not an indication that all content is copied to the target library. The log viewer in Asynchronous mode will display the status of items during the package creation and upload to Azure Pipeline. This option is recommended when a speedier migration is important. To view the actual status of the item when the azure batches are processed there is an option of ‘refresh logs’ from the azure turbo window to check statuses at the end of the work day, therefore allowing you to manually refresh azure logs and synchronize them with essential's post-migration logs, or use Azure Logs Refresh Policy for Hyper Mode jobs.

When in Synchronous mode, the job is reported as finished when all packages created from the source are uploaded to Azure, and all azure batch processing statuses are returned as complete. However, the job progress will take longer in this mode, but when it has finished it is an indication that all content is copied to the target library. The log viewer in Synchronous mode will display the status of items during package creation and the migrated content on the target.

Note:  The next job created in a Hyper migration will start once the previous job operation along with logs update is complete.  Therefore it is considered a slower process vs Asynchronous mode and recommended as the option when there is a need to monitor individual migrations before starting a new one.

Creating User Mapping

Very often migration scenarios require migrating between different domains. In various scenarios users may not be found and will require a user mapping file.

 

Scenario 1

When performing a migration between resources located in one domain - the user and group accounts are the same, which means you do not need a user mapping file.

 

Scenario 2

When performing a migration between resources with different domains but the same user accounts (for example source jjohnson@contoso-source.com and target is jjohnson@contoso-target.com), you do not need a user mapping file. This is because Essentials will use automated mapping where users are verified on the target via their user account name (jjohnson).
 
However, you would require a mapping file for domain groups, as they use two different syntax forms (for example c:0t.c|tenant|ff6207ef-2987-45ee-bd8f-8011b22bd755), even if the names are the same, the guids are different. As a result, you will be required to create a file where groups will be mapped directly  using wildcard mapping (*@contoso-source.com, *@contoso-target.com).
creating user mapping 1
 

Scenario 3

When performing a migration between resources with different domains and different user accounts (for example your source is jjohnson@contoso-source.com and target is john.johnson@contoso-target.com) you will require a user mapping file for users and groups. Note: if you have a few users with the same user name, you can still use the wildcard mapping format (*@contoso-source.com, *@contoso-target.com)
creating user mapping 2

 

Mapping for copy from File Share

This option allows administrators to create a mapping report, matching the source file share with Target Office 365 users.

This operation has the following requirements for use:

·The account used to perform the report needs to be a Global Administrator in this Office 365 tenant.

To create a mapping report, perform the following:

1.On the Drives tab click Mapping Report.
Mapping Report 1
The Mapping Report wizard opens.

2.In the wizard, select the File Share tab.
Mapping Report File Share 1

3.Enter your Domain Controller, domain\login, and password for your file share location. Click Connect.

4.Enter your SharePoint Admin URL for the Target Office 365 connection and click Connect.  On the Connect to SharePoint popup, enter your SharePoint credentials and click Connect. If you receive any message other than "Successfully connected to SharePoint Admin URL", please double check your credentials or contact support. If you would like to add additional Administrator accounts to this report, click Admin+.
user mapping report 4

5.Click the Select button to specify a location and a name for this report.
analyze dropbox4

6.Click Finish to begin the analysis.

7.The report generated will folllow the following rule:
userloginname@*.*, userloginname@*.*
user mapping report 5

8.In order to use the mapping report generated within Essentials, open it in excel, delete the source and target workbook sheets, and the first line with the headers from the user mapping report worksheet. Go to File > Save As> Select file type as CSV UTF-8.

9.You can now use the .csv file in the Copy Tenant wizards, and the Copy My Sites to OneDrive for Business wizard, by selecting Load from CSV on the wizard's first page.
user mapping report 6
 

Please visit the following link for an overview on how to script and schedule jobs such as User Mapping Report.

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen