One of the major challenges in account mapping is that the output of shares listed on the paths tab for even moderately sized data sets can be thousands or even millions of lines. This quickly gets overwhelming to manage.
The three different strategies for reducing spreadsheet size are:
- Expanding or reducing permissions
- Ignoring ACLs past a given folder depth for the full job, just the conflicts, or both
- Ignoring file permissions.
The two important things to consider when using these features are:
- These features can result in a mapping spreadsheet that represents very different permissions from what are actually on the source. This can result in inadvertent access to confidential files on the target that was not available on the source.
- These features work differently depending on the target. For example, if reduced permissions are supported by files on the target, the feature ‘Ignore File Conflicts’ will have no effect on the spreadsheet for a Windows source, because File Conflicts will not be applicable to this source/target combo.
Granting Additional Permissions and Restricting Permissions
Granting additional permissions and restricting permissions are options in the Mapping Strategy page that automatically eliminate conflicts due to reduced permissions in waterfall compliant targets. Be aware that there are subtleties in permissions – for example, User A may have write permissions to /Folder A, but read-only permissions to /Folder A/Folder B – that will automatically be overridden; and in the above scenario, User A will have write permissions to the full /Folder A tree if Grant Additional Permissions is selected.
To grant or restrict permissions, go to the Mapping Strategy page and select the desired option:
Ignore Permissions – Spreadsheet-wide Settings
The following two settings will apply to both the Paths tab and Conflicts tab.
IGNORE PERMISSIONS ON FILES: Select Manage Permissions on Files to list files in the spreadsheet whose permissions are different from their parent folders. Select Ignore Permissions on Files to remove all file listings from the spreadsheet:
IGNORE ACLS BELOW THIS DEPTH: Enter the number of levels of folders that you wish to list permissions on in the spreadsheet:
The currently selected directories will be level 0, the children of those directories will be level 1, and so on. For example, if you have Home/User0 and Home/User1 selected on the source, and the folder depth is 2, permissions for Home/User0/Folder1/Folder2 ACLs will be listed (remember that Home/User0 is the selected directory, so that is level 0), while Home/User0/Folder1/Folder2/Folder3 will not be listed.
NOTE: If you are using Ignore ACLs Below This Depth in conjunction with Ignore Conflicts Below this Depth, this is how it works: Ignore ACLs is the macro setting. It will ignore all permissions – conflicts or otherwise – for the entire spreadsheet beyond the depth you specify. What you can do is specify a depth of, say, 6 for the Ignore ACLs setting, and then specify a depth of 3 for the Ignore Conflicts setting to further limit the folder depth on the Conflict Paths tab. That will result in a max of 6 folder levels on the Paths tab, and a max of 3 folder levels on the Conflict Paths tab. If you just leave the Ignore Conflicts setting blank, it will inherit the value in the Ignore ACLs field.
Ignore Permissions – Conflicts
The following settings will only apply to the Path Conflicts tab.
IGNORE PERMISSIONS CONFLICTS ON FILES: In the Settings page of the mapping job, select Ignore Permissions Conflicts on Files from the Ignore Permissions Conflicts on Files radio button group:
This will eliminate files from the Path Conflicts tab.
This feature is only supported where the target platform does not support reduced permissions (e.g., Box) or it does not support nested permissions (e.g., most Dropbox migrations). The Ignore setting will not be applied, and files will still be listed in the spreadsheet, for target platforms that support reduced or nested file permissions, such as SPO/OneDrive.
For Dropbox targets, also keep in mind that conflicts due to nested sharing will be listed in the Path Conflicts tab of the spreadsheet. If the data is going to a Team Folder, you will want to remove the skips set to yes on that tab so the data is transferred. If you have a redirect to a Team Folder implemented in the Paths or Path Conflicts tab to resolve the nesting conflict, it will apply to any child items in the other tab.
IGNORE CONFLICTS BELOW THIS DEPTH Ignore Conflicts Below This Depth is a setting on the Settings page of the mapping wizard:
A folder depth of 0 will be the folder selected for transfer in the job configuration. A folder depth of 1 will be the selected folder’s immediate child, or subfolder.
For cloud service providers that conform to waterfall permissions, this will eliminate reduced permissions conflicts below the specified depth. For Dropbox, this will also eliminate nested shares below the specified depth. For cloud providers such as Egnyte that support both nested and reduced permissions, this setting will have no effect.
Trying Your New Spreadsheet on For Size
You no longer have to Generate a new spreadsheet when the above settings are changed. Once the first version of your map has been generated, you can change the settings above and then click the Regenerate button on the Define Map screen:
Take note of the date below the Download Generated Map button, as it will change almost immediately after you click the Regenerate Map button. In this example, the time for the generated map changed from 10/15/18 1:11PM in the screen capture above to 10/16/18 at 4:21PM:
There is no scanning, because the existing task data is recrunched with the new settings, so the only notification you will get that there is a new map will be the change in generated map date.
You can change the settings and regenerate as many times as you want to optimize the paths listed in the paths tab.