Overview

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. DryvIQ will automatically create a unique job for each home drive that can be matched to users between the source and destination connections.

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

Create a Network Home Drive Mapping Job

Network home drive mapping job supports impersonation on the source only. All job features defined while creating the parent job will be applied to the child jobs it creates.

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, DryvIQ 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.

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.

Configure Network Home Drive Mapping Job - Settings

Configure the settings that 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. The job status and button you see on this screen vary based on the settings for the job. If you have not selected a user map for the job, the job status will be “Awaiting user interaction,” and you will see a Return to job button. You will not be able to run the job until you add a user map.

Once a user map has been assigned to the job, the status will be “Paused,” and you will see a Run job button so you can run the job. See Run a Network Home Drive Mapping Job below for more information.

Configurations

Map specific users to one another: Select this option to use an existing account/user map you already created to map users. Select the map you want to use for this job from the list.
Create new user map policy: Select this option to create a new user map. Refer to Permission | Account Map/Group Map for more information about the options used to create the user map.
User Account Job Generation: Use this section to identify which connection should be used to determine user accounts. If you select Source, DryvIQ will use the source connection as the source of user accounts when generating user account jobs. If you select Destination, DryvIQ will use the destination connection as the source of user accounts when generating user account jobs.
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 Network Home Drive 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."
Import user filters: Import an inclusion or exclusion mapping file that should be applied to the job. You can upload the file from your computer or use a file on the source platform. (See Account Map/Group Map CSV Guidelines for information about generating mapping files used to include or exclude users.)
An inclusion map specifies users to include when generating child jobs. Child jobs are only created for users in the map that can be matched. All other users will be excluded.
An exclusion map specifies users to exclude when generating child jobs. Child jobs will not be created for the users in this map. Jobs will be created for all other users.

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.

Creating a Network Home Drive Mapping Job Using the REST API

In the example below, the child jobs and parent job (the convention job itself) are set to use different schedule modes. The schedule in the transfer block is for child jobs. In this case, all child jobs would be on auto schedule. The schedule outside transfer block is for convention job itself. In this case, the convention job would be on manual schedule. Note that “convention.match” setting uses “container.” This defines it as a Network Home Drive Mapping job and matches the folder name on source to users on destination.

POST /jobs

{
	"name": "NFS box to OD4B",
	"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"
	}
}

Network Home Drive Mapping Configuration

Network Home Drive Mapping shares the same configuration options as User Job Mapping.

DryvIQ Migrate

Network Home Drive Mapping