Get-MMExPublicFolderStatistics
Gets synchronization statistics of public folders.
Detailed Description
The Get-MMExPublicFolderStatistics cmdlet gets synchronization statistics of public folders. The obtained information can be then exported to a CSV file. See Tuning Statistics to use full functionality of this cmdlet.
Syntax
Get-MMExPublicFolderStatistics
[-FolderPath] <String>
[<CommonParameters>]
Examples
Example 1
Get-MMExPublicFolderStatistics
This command gets statistics of all public folders in the Migration Manager for Exchange project.
Example 2
Get-MMExPublicFolderStatistics |?{$_.SourcePath -eq '\Folder1'} | fl
This command gets detailed statistics of the public folder \Folder1:
Folder Id : 9
Collection Id : 1
Source Name : Folder1
Source Path : \Folder1
Source EntryId : 0x0000000093BDFE1CB63DD74E94AD8A0CD0028A730100F9B5E1322292134898CB269CC88977F40000B3841FE50000
Target Path : \Folder1
Target EntryId : 0x000000001A447390AA6611CD9BC800AA002FC45A03009521443180DC7248BBA93A26524A992600009DF9A4030000
Progress : 100
Discovered Items : 463
Processed Items : 463
Failed Items : 0
Last Processed Time : 2019-07-02T15:47:35Z
Last Error :
Example 3
Get-MMExPublicFolderStatistics | Out-GridView
This command gets statistics of all public folders in the Migration Manager for Exchange project and then sends the output to an interactive table in a separate window.
Example 4
Get-MMExPublicFolderStatistics |?{$_.Progress -eq 100}
This command gets synchronization statistics of the public folders that have progress = 100%.
Example 5
Get-MMExPublicFolderStatistics | ?{$_.Path -like "\PF_Root\*"}
This command gets statistics of the public folders that have path like = '\PF_Root\*'.
Example 6
Get-MMExPublicFolderStatistics | ?{$_.Path -like "\PF_Root\*"} | Export-Csv -NoTypeInformation -Encoding UTF8 -Path "C:\MMEx\export.csv"
This command gets statistics of the public folders and export it to the export.csv file.
Parameters
-FolderPath
The full path to the public folder to obtain statistics.
| Required? | false |
| Position? | 1 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable. For more information, see about_CommonParameters.
Inputs
FolderPath
Outputs
Grid view
CSV file
Get-MMExAgent
Gets parameters of specified Agents.
Detailed Description
The Get-MMExAgent cmdlet gets parameters of one or more Agents specified by the Agent Host and type.
Syntax
Get-MMExAgent
-Type PublicFolder
-AgentHost <hostname>
Parameters
-Type
Specifies the agent type, currently only 'PublicFolder' is allowed.
| Required? | false |
| Position? | 1 |
| Default value | PublicFolder |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-AgentHost
Specifies host name to install specified agent.
|
|
TIP: If this parameter is not specified, the agent will be installed on the local server (localhost).. |
| Required? | false |
| Position? | 2 |
| Default value | localhost |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable. For more information, see about_CommonParameters.
Examples
Example 1
Get-MMExAgent -Type PublicFolder
This command gets all Public Folder agents.
Example 2
Get-MMExAgent -AgentHost 'dmmconsole'
This command gets all agents from Agent host 'dmmconsole'.
Example 3
Get-MMExAgent -Type PublicFolder -AgentHost 'dmmconsole'
This command gets all Public Folder agents from Agent host 'dmmconsole'.
Start-MMExPublicFolderMigration
Starts public folders migration process in express-mode with minimal customization.
Detailed Description
The Start-MMExPublicFolderMigration cmdlet consequentially executes Install-MMExAgent, Set-MMExGroupMatching, Export-MMExPublicFolderMapping, Import-MMExPublicFolderMapping, Initialize-MMExPublicFolderMigration, Start-MMExAgent and Sync-MMExMailPublicFolder. This command should be executed after source and target organizations are added to migration project.
Syntax
Start-MMExPublicFolderMigration
-SourceOrganization <source organization name (as displayed in tree-view)>
-TargetOrganization <target organization name (as displayed in tree-view)>
[-Direction]
[-TargetMailboxSize <size limit>]
[-TargetRootFolderName <root folder name>]
[-TargetMailboxNameTemplate <mailbox name prefix>]
[-MigrateOnly <root folder name>]
[-SkipGroupMatching]
[-SkipSyncMailPublicFolders]
Examples
Example 1
Start-MMExPublicFolderMigration -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization'
This command starts public folder migration from 'My Source Organization' organization to 'My Target Organization' organization.
Example 2
Start-MMExPublicFolderMigration -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization' -TargetMailboxSize 2GB
This command calculates the number of mailboxes necessary to handle source public folder structure considering 2GB size limit for target folder mailboxes, and starts public folder migration from 'My Source Organization' organization to 'My Target Organization' organization.
Example 3
Start-MMExPublicFolderMigration -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization' -TargetMailboxNameTemplate "BrandNewMailbox"
This command calculates the number of mailboxes necessary to handle source public folder structure, and starts public folder migration from 'My Source Organization' organization to 'My Target Organization' organization. Target public folder mailboxes will be named like BrandNewMailbox plus numeric index.
Example 4
Start-MMExPublicFolderMigration -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization' -TargetRootFolderName "CustomRoot"
This command calculates the number of mailboxes necessary to handle source public folder structure, and starts public folder migration from 'My Source Organization' organization to 'My Target Organization' organization. Target public folders hierarchy will reside in the root folder named "CustomRoot".
Example 5
Start-MMExPublicFolderMigration -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization' - MigrateOnly "\Marketing"
This command calculates the number of mailboxes necessary to handle source public folder structure within \Marketing root, and starts public folder migration from 'My Source Organization' organization to 'My Target Organization' organization.
Example 6
Start-MMExPublicFolderMigration -SourceOrganization 'My Source Organization' -TargetOrganization 'My Target Organization' - Direction TwoWay
This command starts 2-way synchronization of public folders between 'My Source Organization' organization and 'My Target Organization' organization.
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 |
-TargetMailboxSize
Specifies maximum size allowed for target public folder mailbox.
| Required? | false |
| Position? | 3 |
| Default value | 15GB |
| 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 |
-TargetRootFolderName
Specifies name of a folder that will contain migrated public folders on target
| Required? | false |
| Position? | 5 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-TargetMailboxNameTemplate
Specifies naming template for target public folders mailboxes.
| Required? | false |
| Position? | 6 |
| Default value | PfMigrationMailbox |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-MigrateOnly
Limits migration scope by specifying source public folder root to migrate.
|
|
NOTE: This parameter requires setting of the TargetMailboxNameTemplate parameter. |
| Required? | false |
| Position? | 7 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
SkipGroupMatching
Specifies if object matching for migrated by Quest Migration Manager for Active Directory (Microsoft Office 365) mail-enabled universal security distribution groups will be skipped.
| Required? | false |
| Position? | 8 |
| Default value | false |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
SkipSyncMailPublicFolder
Specifies if mail-enabling of target public folders and setting directory properties for them will be skippedt.
| Required? | false |
| Position? | 9 |
| Default value | false |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
Inputs
SourceOrganization
TargetOrganization
TargetMailboxSize (optional)
TargetRootFolderName (optional)
TargetMailboxNameTemplate (optional)
MigrateOnly (optional)
SkipGroupMatching (optional)
SkipSyncMailPublicFolder (optional)
Export-MMExPublicFolderMapping
Exports public folder configuration and calculated mapping between source and target public folder mailboxes into comma-separated values (CSV) file.
Detailed Description
The Export-MMExPublicFolderMapping cmdlet calculates the number of mailboxes necessary to handle source public folder structure according to specified size requirements, and exports public folder configuration and mapping between source and target public folder mailboxes into comma-separated values (CSV) file. 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
Syntax
Export-MMExPublicFolderMapping
-SourceOrganization <source organization name (as displayed in tree-view)>
-MappingFilePath <path and filename for the output CSV file>
[-TargetMailboxSize <size limit>]
[-TargetMailboxNameTemplate <mailbox name prefix>]
[-TargetRootFolderName <root folder name>]
Examples
Example 1
Export-MMExPublicFolderMapping -SourceOrganization 'My Source Organization' -MappingFilePath MigrationMapping.csv
This command calculates the number of mailboxes necessary to handle source public folder structure, and writes public folder configuration and mapping for public folder migration from 'My Source Organization' organization to "MigrationMapping.csv file.
Example 2
Export-MMExPublicFolderMapping -SourceOrganization 'My Source Organization' -MappingFilePath MigrationMapping.csv -TargetMailboxSize 2GB
This command calculates the number of mailboxes necessary to handle source public folder structure considering 2GB size limit for target folder mailboxes, and writes public folder configuration and mapping for public folder migration from 'My Source Organization' organization to "MigrationMapping.csv file.
Example 3
Export-MMExPublicFolderMapping -SourceOrganization 'My Source Organization' -MappingFilePath MigrationMapping.csv -TargetMailboxNameTemplate "BrandNewMailbox"
This command calculates the number of mailboxes necessary to handle source public folder structure, and writes public folder configuration and mapping for public folder migration from 'My Source Organization' organization to "MigrationMapping.csv file. Target public folder mailboxes will be named like BrandNewMailbox plus numeric index.
Example 4
Export-MMExPublicFolderMapping -SourceOrganization 'My Source Organization' -MappingFilePath MigrationMapping.csv -TargetRootFolderName "CustomRoot"
This command calculates the number of mailboxes necessary to handle source public folder structure, and writes public folder configuration and mapping for public folder migration from 'My Source Organization' organization to "MigrationMapping.csv file. Target public folders hierarchy will reside in the root folder named "CustomRoot".
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 |
-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? | 2 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-TargetMailboxSize
Specifies maximum size allowed for target public folder mailbox.
| Required? | false |
| Position? | 3 |
| Default value | 15GB |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-TargetMailboxNameTemplate
Specifies naming template for target public folders mailboxes.
| Required? | false |
| Position? | 3 |
| Default value | PfMigrationMailbox |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-TargetRootFolderName
Specifies name of a folder that will contain migrated public folders on target
| Required? | false |
| Position? | 3 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
Inputs
SourceOrganization
MappingFilePath
TargetMailboxSize
TargetMailboxNameTemplate
TargetRootFolderName
Outputs
CSV file