Syncplicity Support

Search our knowledgebase to get the help you need, today

Submit a request
Follow

Network home-drive mapping

Map Network home drives to users on another connection. Individual jobs will be generated to transfer items between the source folder and destination account.

Network home drive mapping jobs are ideal for migrations where you wish to control the transfer at a granular level without the effort of creating individual jobs. DataHub will automatically create a unique job for each home drive that can be matched to users between the source and destination connections.

Important! Network home drive mapping jobs require connections with the ability to impersonate other users.

Related: Create New Job | Transfer Direction

User-Interface - Create a Network Home Drive Mapping Job

Network home drive mapping job supports the following:

Impersonation on the source only

All job features defined while creating the parent job, will be applied to the child jobs it creates

Important! Network home drive mapping jobs require connections with the ability to impersonate other users

User-Interface - Define your Source and Destination Paths

If you are an administrator using Impersonation, enable Run as user... and choose the user you wish to access

Source / Destination Path: If you wish to transfer all content, leave the source path blank. A child job will be created for every home drive. If a directory is selected for the source path, a child job will be created for every home drive within the parent directory. 

Child Job Source / Destination Path: This directory within each folder will be used as the source. If the directory does not exist on the destination, DataHub will create it.

Target the root of each folder: The child job will be created for the first level folder/account relative to the source path

Target a specific directory within each folder: If there is a folder that is exists in every user account, you can define it with this option

User-Interface - Save and Configure Mappings for the Network Home Drive Mapping Job

After configuring policies, behaviors and advanced features, select the option to save and configure the parent job. You will be prompted to schedule the job. This schedule will be applied to the child jobs.

User-Interface - Configure Network Home Drive Mapping Job - Settings

Configure the settings which will determine the general rules for how the child jobs are generated. The user mappings and filter tabs allow you to override automatic user mapping rules and filter out users by explicitly including or excluding them

Remove user account jobs that are no longer valid: This is an on/off setting that deletes jobs that are no longer valid

Email Domain: Specify an email domain to limit the generation of user account mapping child jobs to only users with this email domain. For example, enter 'example.com' to create a job for the user 'test@example.com', but not for the user 'test@something.com'

Mapping policy: Users can be automatically mapped from one platform to another. Select the rules to be used for attempting a match

Unmapped User Policy: What should be done if the user source account is not found on the destination?

User-Interface - Configure Network Home Drive Mapping Job - User Mappings

On the settings tab, you are able to create rules to automatically map folders from one platform to the other for child job generation. Here, you can override those general rules by specifically mapping one folder to another.

Import mappings: Upload a CSV file to create explicit user mappings

Network Home Drive Mappings - CSV Import Sample

Create User Mapping: Manually match each user through the DataHub user-interface

User-Interface - Configure Network Home Drive Mapping Job - Filters

Here, you can specify a list of folders to include or exclude from child job generation. The configuration defined on the other tabs will determine how matching is done from one connection to another, but these filters will remove some of the matches from generating jobs.

Folder Filter Policy: Child jobs are generated from the folders within the path. You can explicitly include or exclude folders when creating child jobs.

Inclusion: Specify folders to include when generating child jobs. When matched, only include folders in this list. All other folders will be excluded.
Exclusion: Specify folders to exclude when generating child jobs. When matched, exclude folders in this list. All other folders will be included.

Network Home Drive Mappings - Filter Import Sample

User-Interface - Run Network Home Drive Mapping Job

After configuring your network home drive mapping job, run the job. This will execute the parent which will create the child jobs

  • After the child jobs are created, the default schedule is set to run every 6 hours so it can review the source for any new content
  • The parent and child job schedules can be changed at any time

DataHub API - Creating a Network Home Drive Mapping Job

Container would match folder name on source to users on destination – Network Home Drive Mapping

Account would match users on source to destination – User Account Mapping

POST /jobs

{
    "name": "personal_drive box to o365",
    "kind": "personal_drive",
    "transfer": {
        "transfer_type": "copy",
        "source": {
            "connection": {
                "id": "{{cloud_connection_source}}"
            }
        },
        "destination": {
            "connection": {
                "id": "{{cloud_connection_destination}}"
            }
        },
        "schedule": {
            "mode": "auto"
        }
    },
    "schedule": {
        "mode": "manual"
    },
    "convention": {
        "match": "container",
        "map_by": {
            "email": true
        },
        "users": "source",
        "remove_invalid": true,
        "unmapped_policy": "warn",
        "type": "personal_drive"
    }
}

DataHub API - Network Home Drive Mapping Configuration

Network Home Drive Mapping shares the same configuration options as User-Drive / User Account Mapping. 
Powered by Zendesk