In order to ensure compliance policy requirements are met within the messaging environment, messaging data must be classified and maintained for periods of time based on the classification level.
In Exchange 2003, the Mailbox Manager provided a means to delete messaging data, including calendar and task objects. Mailbox Manager was limited in its ability, however:
In Exchange 2007, Mailbox Manager was replaced with Messaging Records Management (MRM). Managed Folders, the MRM feature in Exchange 2007, enabled customers to apply retention settings to default folders, such as Inbox and Deleted Items, and also deploy custom managed folders. Users would sort their messages by placing them into different managed folders, with each folder having a different retention setting. With respect to the calendar and tasks folders:
Exchange 2010 introduced Messaging Records Management 2.0 and the Retention Policy framework. The framework consists of retention tags and retention policies. Retention tags are used to apply retention settings to messages and folders. A retention policy is a group of retention tags that can be applied to the mailbox. The use of the word “retention” in this MRM 2.0 naming convention is misleading. In addition to controlling when items are expired out of the mailbox, retention tags can also be used to control when items move to the archive .
With Exchange 2010 RTM, SP1 and SP2 through SP2 RU3, MRM 2.0 does not provide support for assigning retention tags either directly to calendar and task items or to the calendar and tasks folders. Many of you, our customers, have spoken to us about the need for this functionality and see this as a takeaway when compared to previous versions of Exchange.
In the end, compliance requirements need to be met. Excluding calendar and task items from the retention policy framework means that customers that have business and/or legal compliance policies for managing data are unable to guarantee the requirements are met.
In Exchange 2010 SP2 RU4, we’ve added support for Calendar and Tasks folders to Retention Policies.
If you currently use or plan to use Retention Policies, this has important implications for your messaging environment.
Calendar and task items are different than normal message items. When a calendar or task item is saved, the item is stamped with its specific properties. To ensure that a collision (or conflict) doesn't occur between the Mailbox Folder Assistant (MFA) and the assignment of the default properties during an auto-save event, the MFA will not process calendar and task items immediately. Instead, the assistant will delay processing of calendar and task items for 2 hours (based on last modification time of the item; if there is no last modification time, then it is based on the creation time).
Unlike message items, end users cannot assign different retention tags to either the Calendar or Tasks folders or calendar and task items. In other words, Calendar and Tasks retention tags are only controlled via the administrator.
The following logic is used to determine the start date for expiration or move to the archive for calendar items in the Calendar folder:
The following logic is used to determine the start date for expiration or move to the archive for task items within the Tasks folder:
Support for Calendar and Tasks in Exchange 2010 SP2 RU4 means you’ll need to treat this update rollup differently. If you don’t use Retention Policies or if you don’t mind Calendar and Tasks items being moved to archive or deleted automatically based on the DPT settings, you can skip the rest of this post.
However, if you are concerned about the effects of this new functionality will have on your calendar and task items, you can implement the following temporary workarounds:
If you don’t want Calendar and Tasks items to ever expire, you can disable the functionality that is included in Exchange 2010 SP2 RU4. Add the following registry key to your Mailbox servers:
If you want Calendar and Tasks folders to expire at a different interval than DPTs, you can follow the following steps:
We are glad that we were able to bring this long sought after feature to the product. If you have any questions, please let us know.
Ross Smith IV Principal Program Manager Exchange Customer Experience