...
User Job Mapping jobs are ideal for migrations where you wish to control the transfer at a granular level without the effort of creating individual jobs. SkySync DryvIQ will automatically create a unique job for each user account that can be matched between the source and destination connections. Users on the destination are matched to either users on the source, folder names on the source, or LDAP records on the source.
...
Child Job Source / Destination Path: This directory within each user account will be used as the source. If the directory does not exist on the destination, SkySync DryvIQ will create it.
Target the root of each user account: The child job will be created for the first level folder/account relative to the source path.
...
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, SkySync DryvIQ will use the source connection as the source of user accounts when generating user account jobs. If you select Destination, SkySync 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 User job 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."
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.
...
if the Ldap setting is omitted, SkySync DryvIQ will default to account if account querying is supported by source connection; otherwise, it will default to container.
...
Option | Values | Description |
|---|---|---|
default | true/false | Optional. Enables default mapping by all fields. Equivalent to setting all the the following to true: id, name, username, caption and email |
id | true/false | Optional. Match accounts by id. |
name | true/false | Optional. Match accounts by name. |
username | true/false | Optional. Match accounts by username. |
caption | true/false | Optional. Match accounts by caption / display name. |
true/false | Optional. Match accounts by email. | |
fuzzy | true/false | Optional. Allows for partial match on supported platforms. This would apply to all selected fields. |
built_in | true/false | Optional. Allows to use built_in accounts on supported platforms. |
passthrough | true/false | Optional. Allows to create child jobs for folders for which SkySync DryvIQ couldn't match an account (FS or NFS; both sides only) |
external_passthrough | true/false | Optional. Allows external emails that have never been associated as a guest account to get passed through Note: External email already associated as a guest account in OfB/O365 will work regardless of whether external_passthrough is on |
ldap | true/false | Not fully supported |
...