Calendar and Tasks retention tags are only controlled via the administrator.
Users cannot assign different retention tags to either the Calendar or Tasks folders or calendar and task items.
Two important implications of using Retention Policies to manage messages after Exchange 2010 SP2 RU4.
- Beginning with Exchange 2010 SP2 RU4, administrators can create retention tags via the cmdline for use with the Calendar and Tasks default folders. The supported retention actions are: DeleteAndAllowRecovery, PermanentlyDelete, MarkAsPastRetentionLimit. Note that calendar and task items can be moved to the archive mailbox via the MoveToArchive retention action that is associated with the All or Personal retention tag type.
- Default Policy Tags (DPTs) used to move or delete items will now apply to Calendar and Tasks folders.
Because the retention actions MoveToDeletedItems and MoveToArchive are not supported for calendar and task type, we cannot use command to prevent default delete DPT from applying to calendar and task default folder. To work around this issue, we can disable this functionality by adding the following registry key to Mailbox servers:
Value: 0 = Do not process Calendar and Task folders
Value: 1 = Process (default )
Or place the mailbox in a retention hold.
Set-Mailbox "Michael Allen" -RetentionHoldEnabled $true
i. Non-recurring tasks:
1. A non-recurring task expires (or moves to the archive) according to its message-received date, if one exists.
2. If a non-recurring task does not have a message-received date, it expires (or moves to the archive) according to its message-creation date.
3. If a non-recurring task has neither a message-received date nor a message-creation date, it neither expires nor gets moved to the archive.
ii. Recurring tasks expire (or move to the archive) according to the end date of last occurrence. If a recurring task doesn’t have an end date, it does not expire (and isn’t moved to the archive).
iii. A regenerating task (which is a recurring task that regenerates a specified time after the preceding instance of the task is completed) doesn’t expire (or get moved to the archive).
iv. If an item is found within the Tasks folder that doesn’t have a proper item type, it’s ignored (as the item might be corrupt).