Migrating Public Folder Permissions

Permissions for Public Folders can only be migrated from Exchange 2010+ (i.e., they cannot be migrated from Exchange 2007).

The account for the Source needs to either be an Owner of the Public Folder or be in the Public Folder Management Role Group. The Role group method resolves issues of missing ownership of a folder.

In order for Public Folder permissions to be migrated correctly, the users on the Source and Destination must be created and set up and not hidden from the address book. When we migrate permissions for a Public Folder, we attempt to match on three criteria:

• Username portion of the source email address to a username on the destination.
• Direct match of the entire source email address to a user email address on the destination.
• Display name of the user on the source to a user on the destination. 
  • You can force MigrationWiz to match on the Display Name by adding this command to the Support Options in the Advanced Options: UseDisplayNamePermissionMatching=1

Note: By default, Public Folder permissions are migrated for folders that do not exist.  If folders already exist, permissions are not migrated.

If you would like to force permissions to be migrated when a folder already exists, you will need set the Advanced Option to migrate permissions for New folders and existing folders. Additionally, if you are using Public Folder mapping scripts provided by BitTitan Support, you need to set the option to New folders and existing folders. This setting can be found under Source/Destination in the advanced options of the project.

Note: Rules, such as Assistant Rules, are not migrated with Public Folder migrations. Default and Anonymous permissions are not supported. These will need to be set manually in the destination...