1. Home
  2. Account and Permissions Mapping
  3. Account Mapping – Path-Based Mapping

Account Mapping – Path-Based Mapping

Path-based mapping does a couple things:

  • It generates a list of folders that are reported to the Paths tab of your spreadsheet, at a folder level you designate. So whether you have your user directories at the root (e.g., /caitlin, /joe…) or several levels down (/Company/Home/Users/caitlin, /Company/Home/Users/joe…), you can report out the directories in the spreadsheet at the level you desire.
  • Once you have those directories reported out in the spreadsheet, you can add redirects so that each full folder goes to the desired account on the target.  Additional options enable you to finely control the resulting folder structure on the target.

What is a file owner and how is it used in account mapping?

Account mapping is fundamentally based on file ownership.  Ownership can happen if a logged in Windows user creates, modifies, or copies and pastes a file to a new location.  So if a user named Joe has a personal folder called “Joe’s Folder,” Joe may not be the owner of every single file in the folder.  Frequently, administrators who are setting up personal spaces for users may add files to users’ folders that are still owned by the administrator who created them, and these need to be accounted for during a transfer.

You can find the owner of a file by doing the following:

1: Right click on the file and select Properties.

2: Click on the Security Tab.

3: Click the Advanced button.

4: The file owner is displayed at the top of the pop-up:

I just want to send Joe’s entire personal folder on the source to Joe’s account on the target, and ignore who owns the files in his folder.

Yes, you can do that.

1: First, in the users tab, map ALL source owners in the Owners tab to a single admin for the Target Account:

Source Owner Target Account
DOMAIN\joe admin@company.com
DOMAIN\caitlin admin@company.com

 

You do this for two reasons:  first, if the source owners are not all mapped in the Users tab, it will generate an error, but second and more importantly, this is your fallback destination account if CFP cannot transfer the folder to the designated account in the Target Owner field of the permissions tab.  So if you make a typo in the Target Owner field, the fallback account will be what’s listed in the Users tab, and if you have one account listed, you only have one place to look for the folders that could not be transferred to a valid account.  If CFP can find a valid target account for the Target Owner in the Paths tab, mapping in the Users tab is ignored.

2: Set up the Paths tab of your account mapping spreadsheet as follows:

Source Owner Source Path Skip? Target Owner Target Path Write (Groups)
DOMAIN\joe /Joe’s Folder joe@company.com DOMAIN\Marketing
DOMAIN\caitlin /Caitlin’s Folder caitlin@company.com DOMAIN\Project1

Note that the Source Path does NOT have a filename at the end.  The Skip? field is left blank.

  • If you want to send files to the root of the account, leave the Target Path column blank as shown above.
  • If you want to send files to a folder in the account, enter it as ‘/foldername’ in the Target Path:
Source Owner Source Path Skip? Target Owner Target Path Write (Groups)
DOMAIN\joe /Joe’s Folder/ joe@company.com /foldername DOMAIN\Marketing
  • The folder may be one that exists in some or all of your target accounts, or it can be a new folder that CFP will create automatically when the transfer job runs.
  • Create an entry as shown above for each user folder that you wish to transfer.  Upload the edited spreadsheet, wait a minute or so for the sheet to be processed, and then click the Play () button on the dashboard to run your job.

NOTES

1: Any folders that are selected for transfer in the original job configuration (i.e., the folders selected in the file chooser for the source node of your job) that are NOT accounted for in the Permissions tab will fall back to the default mapping mechanism:  CFP will look at the owners of the folders/files in the owners tab of the spreadsheet and transfer them to the target accounts you have designated.

For this reason, it is highly recommended that you set up the target node of your job as follows:

2: Target Account Name for the target node of your job should always be left blank. Entering a target account will nullify Account mapping.

Create a Destination folder in the target node, so your final target node configuration will look something like this:

3: This way, if any files and folders are not mapped in the Paths tab of your spreadsheet, they will go to a folder (in this example, a folder called ‘CFPmigration’).  If you have mapped all source owners to a single admin account as shown above, there will be one CFPmigration folder in the admin account, and the files that go in there will be grouped in folders labelled with each source owner’s name.  This helps to isolate any unmapped files in the CFP transfer to that one folder, so it’s easier to track them down later and identify that they came from the transfer.

4: Note that when you map a given folder with path-based mapping, you are overriding any ownership and permissions settings that were present on Windows for all of the folder’s files and subfolders.

5: Path-based mapping should only be used for folders. If you use folder remapping for a path that ends in a file rather than a folder, it will generate an error.

Updated on April 25, 2019

Was this article helpful?

Related Articles

Leave a Comment