Transitioning from the Exchange Mailbox (Classic) Agent and OnePass for Exchange Mailbox (Classic)
Before you transition from the Exchange Mailbox (Classic) Agent and OnePass for Exchange Mailbox (Classic) to the Exchange Mailbox Agent, review the following considerations and recommendations.
Consider the following before you transition your classic mailbox content to the Exchange Mailbox Agent:
- Only the content from the latest cycle is imported.
- Messages that were content indexed using OnePass for Exchange Mailbox (Classic) do not remain content indexed after they are imported into the Exchange Mailbox Agent. You must configure content indexing in the Exchange Mailbox Agent and run content indexing jobs after the messages are imported. Without content indexing, search will include only the email metadata (to/cc, subject, attachment name, etc. Content indexing is required for email body searches.
However, we recommend that you run the content indexing job only after you have imported all you classic content. For example, if you must run multiple import jobs to import all your classic content, wait until after you have run the final import job before you content index the messages in the Exchange Mailbox Agent. That way, you do not have to run several content indexing jobs, and you will not content index messages that have already been content indexed in previous jobs.
- The Exchange Mailbox Agent does not track stub movement by default. Enable the Track stub movement option on the Advanced tab of the Create New Archiving Policy dialog box.
Review the following recommendations before you transition your classic mailbox content to the Exchange Mailbox Agent:
- The storage policy that you use for the Exchange Mailbox Agent should use the same deduplication database (DDB) location that is used for the classic agent.
- Disable incremental jobs for all classic subclients.
Last modified: 4/1/2019 4:30:12 PM