On This Page

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. These child jobs inherit configurations from the parent job. The Network Home Drive Mapping job can be controlled and manipulated just like a transfer job, but when executed, it will not transfer data. Instead, each execution creates, modifies, or deletes its child jobs, which are then responsible for the transfer of data. 

Adding Locations

In addition to choosing the source and destination platforms that will be used for the Network Home Mapping job, you need to specify the impersonation options and paths that should be used when creating the child jobs.

Run as user (Impersonation)

The ability to impersonate users is required for folder mapping jobs. Impersonation allows the connection to access all folders on a site. To enable impersonation, the given connection must be configured using an administrator account. Only some supported platforms support impersonation. They include

• Box

• Dropbox for Business

• Google Workspace

• Google Team Drives

• Microsoft Office 365

• Microsoft OneDrive for Business

• Microsoft SharePoint. 

Only connections created for these platforms are listed in the Locations step when creating a Network Home Drive Mapping job. For the most current support list, refer to the Platform Comparison within DryvIQ Platform. 

Source and Destination Path

If you wish to transfer all content, leave the source path blank. A child job will be created for every top level folder. If a folder is selected for the source path, a child job will be created for every sub folder within the parent folder. 

Child Job Source and Destination Path

This directory within each folder will be used as the source.

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

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

Setting the Job Schedule

After configuring policies, behaviors, and advanced features, you will be prompted to schedule the job. This schedule will be applied to the child jobs. The parent job will run immediately to 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.

Configuring Mappings for the Network Home Drive Mapping Job

Before you can run a Network Home Drive Mapping job, you must 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 Running 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 Maps 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 Mapping Import CSV File 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. 

Running 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.