Set-MMExGroupMatching
Sets object matching for migrated by Quest Migration Manager for Active Directory (Microsoft Office 365 only) mail-enabled universal security distribution groups. This cmdlet cannot be used for on-premises targets.
This task can be scheduled as described in Using Task Scheduler to Automate Tasks
Detailed Description
The Set-MMExGroupMatching сmdlet searches the source organization My Source Organization for mail-enabled universal security distribution groups and then copies legacyExchangeDN of each source group as an X500 address for migrated target group to set object matching. It is required to synchronize client permissions of these distribution groups.
|
|
Caution: This command should be performed before starting the public folder migration process. It is recommended to repeat this command in case a new mail-enabled universal security distribution group is added. |
Syntax
Set-MMExGroupMatching
-SourceOrganization <source organization name (as displayed in tree-view)>
-TargetOrganization <target organization name (as displayed in tree-view)>
Example
Set-MMExGroupMatching -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization'
This command searches the source organization My Source Organization for mail-enabled universal security distribution groups and then copies legacyExchangeDN of each source group as an X500 address to migrated mail-enabled universal security distribution group on the target organization My Target Organization to synchronize client properties of these distribution groups and to set object matching.
Parameters
-SourceOrganization
Specifies the source organization from which mail-enabled universal security distribution groups will be migrated.
| Required? | true |
| Position? | 1 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-TargetOrganization
Specifies the target organization to which mail-enabled universal security distribution groups will be migrated.
| Required? | true |
| Position? | 2 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
Import-MMExPublicFolderMapping
Imports public folder mapping to provision public folder mailboxes in target.
Detailed Description
The Import-MMExPublicFolderMapping cmdlet imports public folder mapping from a comma-separated values (CSV) file for provisioning necessary public folder mailboxes on target. This operation is required to prepare public folder synchronization and in case of changes in source public folder hierarchy as described in Specific Case Workarounds
During import operation, Migration Manager for Exchange reads files and connects to source and to target organization using credentials from the project database to ensure that these public folders exist in source and in target and can be processed. In case this verification is successful, the public folder pair will be added to database for synchronization, but really synchronization will be started after initialization.
Syntax
Import-MMExPublicFolderMapping
-MappingFilePath <path and filename for the output CSV file>
-Organization <target organization name (as displayed in tree-view)>
Examples
Import-MMExPublicFolderMapping -MappingFilePath MigrationMapping.csv -Organization 'My Target Organization'
This command imports public folder mapping from "MigrationMapping.csv" file and provisions public folder mailboxes and empty public folders in organization named 'My Target Organization' according CSV file values.
Parameters
-MappingFilePath
Specifies the full path for the output CSV file to be generated.
|
|
TIP: If only file name is specified for CSV file, then the output file will be generated in the current directory. |
| Required? | true |
| Position? | 1 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-Organization
Specifies the target organization to which mail-enabled universal security distribution groups will be migrated.
| Required? | true |
| Position? | 2 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
Inputs
Organization
MappingFilePath
Outputs
CSV file
Initialize-MMExPublicFolderMigration
Prepares public folder migration project database for synchronization
|
|
IMPORTANT: MAgE must be stopped before this operation, in case it is started. |
Detailed Description
The Initialize-MMExPublicFolderMigration cmdlet prepares project database for public folder migration using specified CSV file. This operation is required to start public folder migration and in case of changes in source public folder hierarchy as described in Specific Case Workarounds. The CSV file contains SourceFolder, FolderSize, FolderClass, TargetFolder and TargetPFMailbox fields.
Syntax
Initialize-MMExPublicFolderMigration
-MappingFilePath <path and filename for the output CSV file>
-SourceOrganization <source organization name (as displayed in tree-view)>
-TargetOrganization <target organization name (as displayed in tree-view)>
[-Direction]
Examples
Example 1
Initialize-MMExPublicFolderMigration -MappingFilePath MigrationMapping.csv -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization'
This command imports public folder mapping from "MigrationMapping.csv" file and prepares project database for public folders migration from organization 'My Source Organization' to organization 'My Target Organization'.
Example 2
Initialize-MMExPublicFolderMigration -MappingFilePath MigrationMapping.csv -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization' -Direction OneWay
This command imports public folder mapping from "MigrationMapping.csv" file and prepares project database for public folders migration from organization 'My Source Organization' to organization 'My Target Organization' with 1- way synchronization from source to target.
Parameters
-MappingFilePath
Specifies the full path for the output CSV file to be generated.
|
|
TIP: If only file name is specified for CSV file, then the output file will be generated in the current directory. |
| Required? | true |
| Position? | 1 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-SourceOrganization
Specifies the source organization from which mail-enabled universal security distribution groups will be migrated.
| Required? | true |
| Position? | 2 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-TargetOrganization
Specifies the target organization to which mail-enabled universal security distribution groups will be migrated.
| Required? | true |
| Position? | 3 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-Direction
Specifies public folder synchronization direction. The following values are available:
- OneWay - 1-way public folder synchronization
- TwoWay - 2-way public folder synchronization
|
|
IMPORTANT: This decision applies to the current migration project and cannot be changed later. In case this parameter is not set you will be prompted to make this selection during initialization. |
| Required? | false |
| Position? | 4 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
Inputs
SourceOrganization
TargetOrganization
MappingFilePath
Restart-MMExPublicFolderMigration
This command restarts public folder migration or resynchronizes permissions for the specified public folder depending on specified parameters.
Detailed Description
The Restart-MMExPublicFolderMigration cmdlet restarts migration for a specified public folder to resynchronize content and permissions, or resynchronizes permissions only for the public folder if PermissionsOnly parameter is specified. See Managing Public Folder Synchronization for details.
Two resynchronization modes are available depending on PermissionsOnly parameter for the project:
- PermissionsOnly is not set
Permissions and folder content will be resynchronized for specified public folder. Migration will be restarted for public folder and all currently available permissions and messages from source will be migrated to target again. It can be useful in case some messages or permissions were found to be migrated incorrectly, restart of migration forces MAgE to repeat data transferring attempt.
|
|
NOTE: MAgE will not cleanup ALL content of target public folder. For 1-way synchronization, MAgE will reapply all permissions from the source folder to target and will migrate all source messages to target. If some of those messages had been previously migrated by MAgE, old copies will be overwritten (recreated). |
- PermissionsOnly is set
Permissions will be cleared from project database and then resynchronized for specified public folder. This is the only action that will be performed. No public folder content is affected.
Syntax
Restart-MMExPublicFolderMigration
-FolderId <public folder ID value>
[<PermissionsOnly>]
[<CommonParameters>]
Examples
Example 1
Restart-MMExPublicFolderMigration -FolderId 5
This command restarts synchronization for single public folder specified by public folder identifier 5. Identifier could be retrieved using Get-MMExPublicFolderStatistics cmdlet or from a log file.
Synchronization was restarted for the public folder MyFolder with identifier 5
Example 2
Restart-MMExPublicFolderMigration -FolderId 11 –PermissionsOnly
This command only resynchronizes permissions for the public folder with ID 11.
Parameters
-FolderID
Specifies the identifier of a public folder to restart.
| Required? | true |
| Position? | 1 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-PermissionsOnly
Specifies whether permissions for the specified public folder will be cleared from project database and then resynchronized. This is the only action that will be performed.
| Required? | false |
| Position? | 2 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
|
|
TIP: You can find public folder identifier in the log entry, it is a number after the "M":
e.g., in the following log entry 2019-01-28 11:50:52.7225 Px1F48 Tx27 A1 C2 M7 Trace ... public folder identifier is "7". |
