-
Title
Excluding specific message classes upon migration -
Description
It is sometimes required to skip specific message classes from a migration. If the MessageClass is known and it is not the generic IPM.Note MessageClass then it can be excluded from the migration.
An example scenario would be to prevent Symantec Enterprise Vault messages from being migrated simply by excluding that/those specific message classes.The process also works in the same way with regards to public folder messages.
-
Resolution
The first way is to simply edit the config.ini located in the Mail Source Agent (MSA) folder (or PF Source Agent folder in the case where you wish to filter message types for public folder sync) and append the MessageToSkipTypes parameter. The default is:
MessagesToSkipTypes=IPC.Microsoft.ICS.EventBinding, IPC.Microsoft.EventBinding
You may wish to change this to exclude a Symantec message class:
MessagesToSkipTypes=IPC.Microsoft.ICS.EventBinding, IPC.Microsoft.EventBinding, IPM.Note.EnterpriseVault.PendingArchive
Modifying the config.ini on the affected agent will only allow that specific agent to clean up the issue. The next time the config.ini is written back to the target server, the config.ini will revert to the default setting (over written from QMM) for the MessageToSkipTypes parameter.
The second solution recommends a change to the parameter which has a universal effect on QMM. Make this change by selecting Tools | Options | Additional parameters for agent configuration files and adding the message class to the "MessageToSkipTypes" for the agents. This will prevent those message classes from being migrated.Please note, that this parameter doesn't support wildcards n other words you need to specify every unique class you want to skip.
-
Additional Information
In order to see the Additional parameters for agent configuration files you need to enable it via the Windows Registry on the console. Open Regedit and navigate to HKLM\SOFTWARE\Aelita\Migration Manager\CurrentVersion\Exchange Data and create new DWORD key ShowAdditionalParameters and set its value to 1. Note: It has been discovered that if any of the messages classes have been entered twice into the MessagesToSkipTypes= parameter, for example:MessagesToSkipTypes=IPM.Post, IPM.StickyNote, IPM.Task, IPM.NOTE, IPM.Post the MSA will go into a loop where it just restarts over and over again. It was additionally noted that you may or may not get following error message in the MSA log: "MessageClassFilter::TypesToFilter Error 457 This key is already associated with an element of this collection" This error indicates that there is a duplicate entry in the MessagesToSkipTypes= parameter. Please see Solution SOL49236 - Is it possible to just migrate mailbox permissions, without migrating content? - "https://support.quest.com/SUPPORT/index?page=solution&id=SOL49236" for additional info on the use of the MessagesToSkipTypes= parameter.