New-MMExMessageFilter
Creates a message filter for collections.
Detailed Description
The New-MMExMessageFilter cmdlet creates a message filter that will be used to skip specific messages in the collection based on the specified parameters. This filter can be used on collection level with Set-MMExCollection cmdlet . For details refer to Configuring Migration Using PowerShell section of User Guide.
Syntax
New-MMExMessageFilter
-MessageClassesToSkip <message class, full class name, suffix or prefix>
[-MessageClassesToSkipAgeBased <size limit>]
[-AgeInDays <integer>]
Examples
Example 1
New-MMExMessageFilter -MessageClassesToSkip "IPM.*.EnterpriseVault.Shortcut", "IPM.Post.*"
This command creates a message filter to skip all messages of the IPM.Post class including subclasses, and also all messages which class has IPM prefix and EnterpriseVault.Shortcut suffix.
Example 2
New-MMExMessageFilter -MessageClassesToSkip "IPM.*.EnterpriseVault.Shortcut", "IPM.Post.*" -MessageClassesToSkipAgeBased "IPM.Note.Shortcut" -AgeInDays 25
This command creates a message filter. It will skips all messages of the IPM.Post class including subclasses, all messages which class has IPM prefix and EnterpriseVault.Shortcut suffix, and all messages of the IPM.Note.Shortcut class that are older than 25 days.
Parameters
-MessageClassesToSkip
Specifies the list of message classes to be skipped. Migration Agent for Exchange will skip all specified message classes of messages..
| Required? | true |
| Position? | 1 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | true |
|
|
TIP: You can use an asterisk wildcard character in names of message classes, so the full name need not be typed. |
-MessageClassesToSkipAgeBased
Specifies a list of message classes that will be skipped depending on how many days ago these messages were created. Migration Agent for Exchange will skip certain message classes of messages that are older than a number of days specified by AgeInDays parameter.
| Required? | false |
| Position? | 2 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | true |
|
|
TIP: You can use an asterisk wildcard character in names of message classes, so the full name need not be typed. |
-AgeInDays
Specifies the number of days for MessageClassesToSkipAgeBased parameter. Migration Agent for Exchange will skip certain message classes of messages that are older than the specified number of days.
| Required? | false |
| Position? | 3 |
| Default value | none |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
Load Balancer solution parameters
Load Balancer solution handling
The Add-MMExExchangeRemoteHost has the following syntax:
Add-MMExExchangeRemoteHost -OrganizationName <Exchange organization name> -FQDN <FQDN name> -Version <Exchange server version> [-ADSite <Active Directory site name>]
Where
- OrganizationName is a name of Exchange Organization.
- FQDN is FQDN name of Client Access Server or Load Balancer in Exchange organization.
- Version is version of Exchange server that is accessed by means of Client Access Server or Load Balancer in Exchange organization.
-
ADSite - is a name of Active Directory site where Client Access Server or Load Balancer is located. This parameter is optional.
Example: Add-MMExExchangeRemoteHost
The following cmdlet adds the FQDN of Client Access Server or Load Balancer that reside in the source or target organization to the project database:
Add-MMExExchangeRemoteHost -OrganizationName ExchangeOrg1 -FQDN ExchCAS.source.com -Version Ex2010sp3
Appendix A. Measurement of Migration Agent for Exchange Performance
This section contains performance test results of a single Migration Agent for Exchange instance that performs mail data migration from Exchange Server 2010 to Exchange Server 2013.
Performance test results:
- Maximum memory consumption per instance is about 1000 MB.
- Average data processing speed per instance is 3.5 GB per hour.
Configuration of the Test Environment:
| Server Role | Server Operating System | CPU | RAM, GB |
|---|---|---|---|
| Exchange Server 2010, source | Windows Server 2008 R2 Enterprise SP1 | 4 vCPUs (Intel Xeon E5-2665) | 34 |
| Exchange Server 2013, target | Windows Server 2012 | 8 vCPUs (Intel Xeon E5-2670 v2) | 30 |
| Agent host | Windows Server 2012 R2 | 8 vCPUs (Intel Xeon E5-2670) | 15 |
| SQL server 2008 R2, Migration Manager console | Windows Server 2008 R2 Enterprise SP1 | 2 vCPUs (Intel Xeon E5-2665) | 17 |
Network speed: 1 Gbit/s.
Appendix B. Migrating Large Public Folders to Exchange 2013 (or Higher) and Office 365
Unlike Exchange versions 2010 and earlier, in Exchange 2013 or higher
|
|
Important: Currently, Migration Manager for Exchange processes public folders of source Exchange 2013 or higher organizations as a single list of public folders ignoring their actual division by public folder mailboxes. Therefore, you need to plan public folder migration from an Exchange 2013 or higher organization according to information in this section in the same way as for Exchange 2010 and earlier organization. |
