File Share Configuration

This guide will show how to configure multiple File Shares as a source configuration

A File Share configuration is defined by the following requirements:

  1. Migrating to Google or M365
  2. Authentication Method
  3. Active Directory Access
  4. Document Options
  5. Migrating File ACL’s
  6. Mapping File Shares
  7. Supported Features by Destination

Migrating to Google or M365

File stored in a local network file share can be migrated to Google Drive, Microsoft OneDrive or a SharePoint Teams Site. CloudM Migrate will need to be installed on a server in the network. Once completed the server will need to have the desired shares mapped to the CloudM Migrate server. If using a Cluster, each Secondary server will need the drive mappings done the same as the Primary server.

Authentication Method

Once all the file shares are mapped as drives the account used to logon to the server(s) will need to have READ access to all files in scope for a migration.

Active Directory Access

The server and account used to access the CloudM Migrate server will need access to Active Directory (AD) to look up the users SMTP address to apply on the destination. If AD access is not available to the account or server then uncheck the option Resolve Email Addresses in CloudM Migrate.

With no AD access a address replacement file will need to be used where column A is domain/username and column B is UPN address.

Document Options

By default CloudM Migrate will have Migrate Top Level Folder enabled which will collapse the source folder structure into one top level folder that can be specified under the Project Advanced Options. Uncheck Migrate Top Level Folder to preserve the existing folder structure.

Migrating File ACL’s

To migrate permissions select either Shared Documents or Shared Documents and Send Notification Email under the File System Document Sharing dropdown.

Mapping File Shares

All source file shares need to be mapped as network drives to the CloudM Migrate server. If using a cluster all Secondary nodes will also need the same drives mapped.

The file share mappings will need to done using the server/node System account and made persistant. This will require the machine to be domain joined.

Use the following steps to map the drives:

  1. Download the SysInternals tool PsExec to the server/node. Extract the zip file to a working directory such as Temp.
  2. Open a Command Prompt as Administrator.
  3. Navigate to the working directory and enter psexec -i -s cmd.exe
  4. In the new command prompt from PsExec enter net use e: \\servername\sharedfolder /persistent:yes
  5. Each file share will need to be mapped in turn with the same drive letters used on any additional nodes.

Note: The mapped drives will appears as disconnected when viewed from File Explorer.

Supported Features by Destination

Feature Google Drive Microsoft OneDrive / SharePoint Team Sites
Folder Hierarchies and Files Yes Yes
Truncate Oversize Paths No Yes
Rename Illegal File Names N/A Yes
Preserve File Dates Yes Yes
Folder and File ACLs Yes Yes
Active Directory Permissions Yes Yes
File Type Filters Yes Yes
Copy Empty Folders Yes Yes
Simultaneous Migrations Yes Yes
Provision Destination Account Yes Yes
Warn on Size Limits No Yes
Full Reporting Yes Yes
Was this article helpful?
0 out of 0 found this helpful