Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.2.3 - User Guide

Metalogix Essentials for Office 365 User Guide
Administrator Architect Backup
Interface Overview Common Functions
Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper Backup Creating a Full Backup Creating an Update Backup Creating an Exchange Online Mailbox Backup Creating an Office 365 Group Backup Creating a OneDrive for Business Backup Backup Resume Backup Search Restore from Backup Scheduling Backup Jobs Import/Export Backup Archives Moving the Backup Location Backup Project Conversion
Drives
Interface Overview Common Functions
Connecting to Drives Copy Google Drives to OneDrive for Business Copy Google Drive to an Office 365 Group Copy Google Drive to Microsoft Teams Copy File Shares to OneDrive for Business Copy File Shares to SharePoint Online Copy File Shares to an Office 365 Group Copy File Share to Microsoft Teams Copy My Sites to OneDrive for Business Copy OneDrive for Business to OneDrive for Business Copy Box to OneDrive for Business Copy Box to SharePoint Online Copy Box to an Office 365 Group Copy Box to Microsoft Teams Copy Dropbox Business to OneDrive for Business Copy Dropbox to an Office 365 Group Copy Dropbox to Microsoft Teams OneDrive Management Progress Tab Hyper Migration Path Length Overflow
File Manager Informant Migrator
Interface Common Functions
Connect to SharePoint and OneDrive for Business Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts Pre-Migration Analysis Azure Turbo Mode In-Place Tagging of SharePoint Items Incremental Copy Nintex Workflow Migration Orphaned Users Copy Preserving Content Authorship and Approve/Reject Statuses Reprocess Failed Items Save Site to XML Using Scripts and Integration With Windows Task Scheduler
Profile and Global Variables Public Folders for SharePoint Reporting and Re-Mapping Users and Templates Security Manager Term Store Manager Scripts Wizards Appendix

Columns for Copying E-Mail and Public Folder Objects using CSV

1.Item Name - Generally this is the subject of the e-mail

2.Outlook Path - Identifies the location of the e-mail in the source

3.Entry ID - This is a reserved field.

4.Target SharePoint Site - Identifies the target site for the file listed in the source file column. The field is left blank by default but may be specified to upload content into different sites and lists using the same CSV file.

info

NOTE: In order to take advantage of this feature the CSV file must be uploaded on a site not a list level.

5.Target SharePoint List - Identifies the target list for the import

6.SharePoint File Name - Identifies the SharePoint item name that will be used for the import ( "/" is used to identify folders)

7.Content Type - Identifies the SharePoint content type that will be used for the import.

info

NOTE: This content type should already exist within the target SharePoint list and must be spelled exactly the same way to avoid errors.

8.Custom Fields - Any custom fields would be listed following the content type.

info

NOTE: These fields must already exist within the target SharePoint list (and content Type). The values entered here must also pass any SharePoint validation or restrictions for the corresponding field.

9.Created At - Identifies the content creation date which is extracted from the file system. If left blank the value will be set to the current date and time.

10.CSV ID Col - This is a reserved field utilized for incremental copy functionality. Do not enter anything into this field.

11.Modified At - Identifies the last content modification date which is extracted from the file system. If left blank the value will be set to the current date and time.

12.Created By - Identifies the user who created the content. If left blank the value will be set to the user currently logged into SharePoint.

13.Modified By - Identifies the user who last modified the content. If left blank the value will be set to the user currently logged into SharePoint.

14.Mark Version - For versioned libraries, identifies the version level for the item being imported ("Major" or "Minor"). If a quasi-versioning system was used in the file system, this field along with the SharePoint File Name can be used to recreate the versions in SharePoint. In order to implement this functionality, use the same file name in the SharePoint File Name field and then specify the appropriate version level in this field. If left blank, the default version level will be used during import.

15.Version Comment - Specifies the comment that will be used when importing items

info

NOTE: When copying/tagging a library with versioned documents, using the csv option will apply the information entered for the file to each of the versions. If your versions contain unique information, you will want to put the following mapping command in the column that contains unique information on the versions: where "SOURCE" is the display name of the column.

Experience Data

Essentials for Office 365 submits user experience data to our internal telemetry servers.  This information is used by management to better understand how the software is being used for the sole purpose of product planning and development.

The information collected includes, but is not limited to:

·Software version

·Framework version

·Operating System

·SharePoint version

·Session data

·Activated software license key

If you do not wish to participate, you may disable this in the following location:

Help > Profile Manager > Global Variables > Submit Experience Data > False

How to Import Projects into Metalogix Essentials for Office 365

Importing projects into a workplace is useful if you want to move a project between installations of Metalogix. This operation connects Metalogix with the project folder that is generated when you connect to a site collection, farm, or tenant. It can also import collected data projects, google drives and backups.

1.Right Click in the Navigation pane and select 'Import'.
Import1-23-2015

2.Pick 'Existing Projects into Workplace'.
ExistingProjects1-23-2015

3.Select the 'Browse' button next to 'Select root directory'.
SelectRootDirectory1-23-2015

4.Select the folder that you want to import the projects from.
metavisfolder1-23-2015

5.Select the projects that you want to import. If you check the 'Copy Projects into Workplace' Metalogix will copy the projects from wherever they are into the current Metalogix workspace folder. Sometimes it makes sense to have a reference to an external project, such as when you have a Backup and sometimes it makes sense to copy the files into the new workplace so that you have all your projects in one place rather than linking back to the original location.
FinishScreen1-23-2015

6.Your projects should now be imported in the Navigator pane.
Result1-23-2015

Password Encryption

Any credentials that are entered through the Metalogix interface and used in a script or scheduled operation are automatically encrypted, but there may be times in which you need to encrypt a password outside of this operation.

If you need to encrypt a password, you can do it through one of two methods - through the Essentials Console, or through Command Script.

Related Documents