It may be necessary to remigrate ACL's on mailbox folders without migrating mailbox content. This article describes how this can be achieved.
There may be different reasons for remigrating folder ACL's, which could include:
There are two different scenarios that can be contemplated here:
Scenario 1 : "Re-migrate ACLs and Delegates":
[Exchange]RemigrateMode=1 (Default value) should be sufficient for "On-premise Exchange" and "O365" targets. This should quickly skip all migrated messages and migrate ACL/Delegates. This default option will migrate any new items that have not being previously migrated.
Also, you can ensure that no items are migrated (including new items) selecting a date in the past that will not return any items:
Scenario 2: "Fresh migration":
For "O365" target: One can just check "Migrate mail data" (without the other "mail", "task", and "calendar" data checked), the reason behind is that O365 target does not traverse folder hierarchy to migrate folder ACLs. MNE is designed to migrate delegates and apply specific folder permissions to well-known folders:
Note: Parameter [General]ACLs=0 will not migrate ACLs.
For "On-premise Exchange": Delegates are migrated by adding AD "publicDelegates" attribute without going through each folder, but ACL is migrated going through folders recursively. It would require you to check "Migrate mail data" and select "mail", "task" and "calendar" data if you want those folder ACLs migrated:
To avoid spending time on migrating items in these folders, you can ensure that no items are migrated selecting a date in the past that will not return any items:
Note that if you uncheck “Migrate email messages” in this scenario, you will find out after migration that you have delegate user migrated but when checking the folder permission in Delegate Access, it is set to “None”:
© ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center