Any user of the Migration App.
How It Works
Migration App translates NTFS permissions to Egnyte during the Permissions Migration command in a three-step process.
- First, it extracts the permissions from the Source.
- Next, it maps those permissions to what they should look like at the Egnyte side.
- Finally, it applies permissions to the files on Egnyte.
Note that during Steps 1 and 2, no information is provided to the User Interface. So until the system begins Step 3, nothing will display on the Migration Dashboard.
Permissions Migration can take longer than the original Data Migration, so plan accordingly.
- Before migrating permissions, it's ideal if both users and groups have already been created on the Egnyte platform, although it is possible to migrate empty groups.
- Can also migrate Azure AD users and group permissions using this tool.
- Migration App migrates permissions for folders. Files inherit the permissions of their parent folder.
- Permissions Migration is an all-or-nothing command, which means it doesn't do "True-Ups." We recommend to run Permissions migration at the very end of a Migration Job, right before cutting over all your users from using the Source to using Egnyte.
- The first two steps can take a considerable amount of time, and no information is available to be displayed on the User Interface until they are completed. This can be somewhat confusing, since other commands in Migration App, such as Scan, Sanitize and Migrate Data, provide both stats and a visual progress bar that corresponds to the status of the command.
- Once permissions are scanned and extracted from the source and mapped to Egnyte (the first two steps), they are then applied at a rate of one folder per second, regardless of the number of permissions aligned with each folder.
When running Permissions Simulation or Permissions Migration, if there are very long path names, the error directory may not be found on source. This means those paths have a path length more than 256 characters. In such cases, there are two solutions:
Change the default path length by changing the registry key, refer to Microsoft’s documentation here.
Change the folder structure so that the path length comes under 256 characters.
- Run True-up to upload the data according to the new folder structure.
- Run Permissions Simulation or Permissions Migration again.
- Change the default path length by changing the registry key, refer to Microsoft’s documentation here.
- It is not possible to migrate permissions to Private folders on Egnyte.
Permissions mapping is detailed below.
|Read & Execute||Viewer|
|Delete Subfolders and Files||Full|
|Create Files/Write Data||Editor|
|Create Folders/Append Data||Editor|
|Write Extended Attributes||Editor|
|Traverse Folder/Execute File||Viewer|
|Read Extended Attributes||Viewer|
What If Some Users And Groups Have Not Yet Been Created On Egnyte?
If you run a Permissions Migration and any of the Users or Groups scanned on the Source are not found on Egnyte, the Permissions Migration command itself will complete successfully. But in the Migration Report, you can open up the "Missing Users" and "Missing Groups" worksheets to view a list of those Users and Groups not yet created on Egnyte.
Once the missing Users and Groups on your Egnyte domain is created, run Permissions Migration again or manually apply the appropriate permissions.
Permissions Migration is usually the last step in a migration project, but there are times to do a dry-run before initiating the actual Permissions Migration. A Permissions Migration Simulation provides insights into any missing Users and Groups on Egnyte that will be needed to create before running the final Permissions Migration command.
Prior to initiating either the Simulation or a Permissions Migration, first create all the expected Groups and Users on your Egnyte domain.
Navigate to the Migration Details page. On the Migration Actions menu, select Permissions Simulation.
This will initiate a three-step process.
- First, Migration App scans the source to identify NTFS permissions.
- Next, it scans the destination domain to identify Users and Groups that have already been created.
- Finally, it compares the two to provide insights as to what might be missing
Depending on the number of permissions on either your source or destination, these scans can take some time to complete.
Once the command has completed, the results will be displayed on the Migration Details page. Additional information may be found on the Migration Job Report.
Permissions Simulation Results On The Migration Job Report
Click Download Job Report and open the CSV file. The Migration Summary register will include the Permissions Simulation on the list of completed commands.
It is also possible to select the Perms Migration Simulation register for more detailed information. And the Missing Users and Missing Groups registers will provide a list of anything found missing.
Questions? Feature Requests? Other Feedback?
If you have feature suggestions or requests, feel free to submit them here, and make sure you mention Migration App in the text.
For more complex requests that would benefit from providing screenshots or other attachments, you may submit them to firstname.lastname@example.org. Be sure to include Migration App in the email title. Our Support team will push your comments to the Product team for consideration.