Exchange 2007 Messaging Records Management

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/compliance-policies-archiving/exchange-2007-messaging-records-management-part1.html[/CODE]
[SIZE=3][B]
PART-1[/B][/SIZE]

[B]Introduction[/B]

One major new feature of Exchange 2007 is that of Messaging Records Management (MRM). The main principle behind MRM is that it helps an organization with its legal compliance requirements, something that previous versions of Exchange aren’t particularly good at. It does this by placing the onus on the user to categorize their messages, leading to these messages being retained where appropriate. Obsolete messages are then removed. Sounds simple enough? In truth it is, although there are a few processes to understand and some terminology to become familiar with.
[B]The MRM Process[/B]

As I just mentioned, with MRM users are able to categorize their own messages and ensure that these messages are retained. Where are they retained? One of the key components of MRM is a [B]managed folder[/B]. There are actually two types of managed folder, namely [B]managed default folders[/B] and [B]managed custom folders[/B]. Managed default folders are based on folder names that already exist within users’ mailboxes, such as the Inbox or Sent Items, whilst managed custom folders are created by the Exchange administrators and are essentially additional folders seen within users' mailboxes. They can be seen via Outlook and OWA and typically they cannot be deleted, renamed or moved. For example, Figure 1 shows how managed folders appear within the OWA client. Notice how, when right-clicking the folders, that the options to delete or rename the folders are dimmed.
[IMG]http://www.msexchange.org/img/upl/image0021178182538053.jpg[/IMG]
[B]Figure 1:[/B] Managed Folders In OWA
We'll cover how you create these managed folders and how to set the retention settings as we go through this article. The important point to take away at the moment is that it's the users that classify their messages, placing them into the appropriate managed folder either manually or via rules. If messages are placed into managed folders for retention purposes, it follows that there must be a process for removing unwanted content. MRM gives us a way to control unwanted content based on age or message type. We'll also cover that as we go through this article.
You have already seen from Figure 1 what managed folders look like from within an OWA client. You'll notice that the managed folder names in Figure 1 are all custom names that I created, hence these are referred to as managed custom folders. Look at Figure 2 below to see a list of the managed default folders that can be configured. Note that the Action pane has been removed from the Exchange Management Console (EMC) for clarity. To view managed default folders via the EMC, follow these steps:

[LIST=1][*]Run the EMC.[*]Expand the [B]Organization Configuration[/B] node and then click [B]Mailbox[/B].[*]In the result pane, select the [B]Managed Default Folders[/B] tab.[/LIST]
To view this information via the Exchange Management Shell (EMS), the relevant cmdlet is [B]Get-ManagedFolder[/B]. This is shown in Figure 3.
[B][IMG]http://www.msexchange.org/img/upl/image0041178182538084.jpg[/IMG]
[/B][B]Figure 2[/B]: Managed Default Folders
[IMG]http://www.msexchange.org/img/upl/image0061178182538084.jpg[/IMG]
[B]Figure 3[/B]: Results of Get-ManagedFolder
For the remainder of this article, let's look at the first two steps of the five required to deploying MRM. In part two of this article, I’ll cover the remaining three steps.
[B]Step 1: Create Managed Folders[/B]

Managed default folders are created automatically when Exchange 2007 is installed, although you can choose to create additional managed default folders if you wish. Creating managed custom folders is really easy, both via the EMC and via the EMS. Let’s go through the process of creating some sample managed folders and content settings as follows. Don’t forget, these are just sample folders to give you an idea of the process; they probably wouldn’t mean much in the real world!

[LIST][*]Check users’ Inbox folders for items older than 90 days. Once found, these items are placed into a managed custom folder called [B]Old Inbox Items[/B] where they are retained for a further 180 days.[*]Create managed custom folders that store documents for two different projects, namely [I]Project X[/I] and [I]Project Y[/I]. These documents are stored for 365 days.[/LIST]
The first thing to do is to create the new managed custom folders. Here's how:

[LIST=1][*]Run the EMC.[*]Expand the [B]Organization Configuration[/B] node and then click [B]Mailbox[/B].[*]Either right-click the Mailbox object and choose the [B]New Managed Custom Folder… [/B]option, or choose the same option from the Action pane.[*]The New Managed Custom Folder wizard appears which consists of the screen that you see now, plus the Completion screen. The first screen is shown below in Figure 4.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0081178182919599.jpg[/IMG]
[B]Figure 4[/B]: Managed Custom Folder Wizard

[LIST=1][*]On the first screen, the following information needs to be entered:
[LIST][*]The [B]Name[/B] field is the name of the managed custom folder as seen within the EMC and EMS.[*]The [B]Display the following name…[/B] field is the name that users see within Outlook and OWA. This field is automatically populated with the same information that you type into the Name field, but you can change this field if you like. In my case, I’ve set both of these fields to [B]Old Inbox Items[/B].[*]There is an optional size limit that you can set on this managed custom folder. In my case, I set this to 1024KB meaning that each user gets allocated 1MB to this managed custom folder. This is obviously too low to be meaningful, as I entered this value to make it easy for me to simulate what happens when the storage limit is exceeded.[*]There is an optional field to enter descriptive information that is shown to the users within Outlook or OWA. Figure 5 gives an example of how this looks to the users in OWA, coupled with how the storage limit allocation is progressing.[*]Finally, there is an option to prevent users from minimizing the descriptive information in Outlook or OWA.[/LIST]
[*]Once all the relevant information has been entered, click the [B]New[/B] button. The [B]Completion[/B] page is then shown which also shows you the EMS commands to create this managed custom folder via PowerShell. The cmdlet used is:

[I]New-ManagedFolder -Name 'Old Inbox Items' -FolderName 'Old Inbox Items' -StorageQuota '1MB' -Comment 'Inbox items older than 90 days are placed here for your review.' -MustDisplayComment $true[/I][/LIST]
I’ve then repeated the above series of steps to create the Project X and Project Y managed custom folders.
[IMG]http://www.msexchange.org/img/upl/image0101178182919615.jpg[/IMG]
[B]Figure 5[/B]: Managed Custom Folder Comment
Incidentally, since I’ve mentioned the fact that you can set storage limits on the folders, you may be wondering what happens if you exceed these limits. Figure 6 shows you how the storage limit allocation comment looks when you’ve exceeded your limit. Figure 7 shows you the warning message you receive when attempting to add additional items to the folder that has exceeded the limit. These are how the messages are seen in the OWA client.
[IMG]http://www.msexchange.org/img/upl/image0111178182919646.jpg[/IMG]
[B]Figure 6[/B]: Managed Custom Folder Storage Limit Exceeded Comment
[IMG]http://www.msexchange.org/img/upl/image0121178183363365.jpg[/IMG]
[B]Figure 7[/B]: Warning When Storage Limit Exceeded
[B]Step 2: Create Managed Content Settings[/B]

The next piece of our MRM jigsaw is the managed content settings. Managed content settings actually apply to either managed default folders or managed custom folders like the folders we just created. In our case, we want to apply settings to the default Inbox folder as well as our three managed custom folders which means we’ll be setting three different managed content settings (both ‘project’ folder content settings are essentially the same). Managed content settings allow you to perform various options such as moving items to the Deleted Items folder or your chosen managed custom folder, or perhaps permanently deleting the items. It follows that, since managed content settings apply to managed folders, you must either target the managed default folders or have created at least one managed custom folder before you can create managed content settings. Here's how to create our managed content settings for the default Inbox folder:

[LIST=1][*]Run the EMC.[*]Expand the [B]Organization Configuration[/B] node and then click [B]Mailbox.[/B][*]Select the [B]Managed Default Folders[/B] tab and you will now see the managed default folders list as shown above in Figure 2.[*]Highlight the Inbox managed default folder and then either right-click it and choose the [B]New Managed Content Settings… [/B]option, or choose the same option from the Action pane.[*]The [B]New Managed Content Settings[/B] wizard appears showing the Introduction screen. This is shown in Figure 8. Let’s examine the options that have to be configured:
[LIST][*]In the [B]Name of the managed content settings…[/B] field, enter a meaningful name that will be seen in both the EMC and EMS. I’ve chosen to enter [B]‘Inbox items older than 90 days’[/B].[*]In the [B]Message type[/B] drop-down list, choose the type of items that will be affected. Choices are [I]All Mailbox Content[/I], [I]Calendar Items[/I], [I]Contacts[/I], [I]Documents[/I], [I]Faxes[/I], [I]Journal Items[/I], [I]Meeting Requests Responses and Cancellations[/I], [I]Missed Calls[/I], [I]Notes[/I], [I]Posts[/I], [I]RSS Items[/I], [I]Tasks[/I] and [I]Voicemail[/I]. Since I want everything older than 90 days to be affected, I’ve chosen [B]All Mailbox Content[/B].[*]We require message retention to be set, so the [B]Length of retention period (days)[/B] check box is selected and a value of 90 added.[*]Since the above option has just been selected, it’s now possible to configure when the retention period starts. I’m interested in ensuring that the retention period starts when the messages are delivered, so I’ve left it at the default option. The other option is [I]When item is moved to the folder[/I].[*]It’s now also possible to specify the [B]Action to take at the end of the retention period[/B]. I’ve chosen the [B]Move to a Managed Custom Folder[/B] option, clicked the [B]Browse…[/B] button and then selected the [B]Old Inbox Items[/B] managed custom folder previously created. The other options here are [I]Move to the Deleted Items folder[/I], [I]Delete and Allow Recovery[/I], [I]Permanently Delete[/I] and [I]Mark as Past Retention Limit[/I].[*]Once completed, this screen looks like the one shown in Figure 8.[/LIST][/LIST]
[IMG]http://www.msexchange.org/img/upl/image0141178183363365.jpg[/IMG]
[B]Figure 8[/B]: Managed Content Settings Wizard

[LIST=1][*]Clicking the [B]Next[/B] button takes you to the [B]Journaling[/B] screen, where it’s possible to forward copies to an alternative address. It’s possible to pick any type of mail-enabled recipient here, such as a mailbox, distribution list or contact. I’ve not selected this option in this example.[*]Clicking [B]Next[/B] takes you to a configuration summary screen, followed by the [B]Completion[/B] screen that once again shows you the EMS command to create this configuration via PowerShell.[/LIST]
The cmdlet used is:
[I]New-ManagedContentSettings -Name 'Inbox items older than 90 days' -FolderName 'Inbox' -RetentionAction 'MoveToFolder' -AddressForJournaling $null -AgeLimitForRetention '90.00:00:00' -JournalingEnabled $false -MessageFormatForJournaling 'UseTnef' -RetentionEnabled $true -LabelForJournaling '' -MessageClass '*' -MoveToDestinationFolder 'Old Inbox Items' -TriggerForRetention 'WhenDelivered'[/I]
It’s worth bearing in mind that once you’ve created your managed content settings, they appear below the relevant folder they are associated with as shown in Figure 9. Once again, the Action pane has been removed for clarity.
[IMG]http://www.msexchange.org/img/upl/image0161178183363365.jpg[/IMG]
[B]Figure 9[/B]: Content Settings Linked To Managed Default Folders
I’ve then proceeded to create additional managed content settings for the Old Inbox Items, Project X and Project Y managed custom folders. The ‘Old inbox items older than 180 days’ managed content settings configuration applies to all folder content and permanently deletes all items in the Old Inbox Items folder that are older than 180 days, whilst the ‘Documents relating to Project X’ and ‘Documents Relating to Project Y’ managed content settings apply only to documents and delete items older than 365 days. As you can see, things are flexible to suit your needs.
I want to close part one of this article by drawing your attention to the [B]Entire Mailbox[/B] managed default folder that you may have noticed in Figure 9. This can be used to apply managed content settings to all folders within a user’s mailbox, although managed custom folders and managed default folders already linked to a managed folder mailbox policy are excluded. I’ll be covering managed folder mailbox policies in part two of this article.
[B]Summary[/B]

This completes our look at part 1 of Messaging Records Management. So far we’ve covered how to create managed folders and managed content settings, as well as how some of these items are displayed to OWA users. In part 2, we’ll look at managed folder mailbox policies, how to apply these policies to users, and how to schedule the whole process to run.

[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/compliance-policies-archiving/exchange-2007-messaging-records-management-part2.html[/CODE]

[SIZE=3][B]PART-2[/B][/SIZE]

[B]Introduction[/B]

In part one of this article, we looked at an overview of what Messaging Records Management (MRM) is and then went on to cover the first two of the five steps required to implement it. The first step required the creation or identification of the required managed folders, namely managed default folders or managed custom folders. Once these had been created, managed content settings were created that were applied to the managed folders. We’ll now go on to look at the remaining three steps required to complete the process. They are:

[LIST][*]Create managed folder mailbox policies.[*]Apply the managed folder mailbox policies.[*]Schedule the managed folder assistant.[/LIST]
[B]Step 3: Managed Folder Mailbox Policies[/B]

The third step is to create managed folder mailbox policies. In part one of this two-part article, we created three managed custom folders that we can ensure are deployed to users at the same time by linking them to a managed folder mailbox policy. That’s one of the key things to consider regarding a managed folder mailbox policy – all managed folders that are linked to the policy are created at the same time when the policy is linked to a user’s mailbox. To create this policy via the Exchange Management Console (EMC):

[LIST=1][*]Run the EMC.[*]Expand the [B]Organization Configuration[/B] node and then click [B]Mailbox[/B].[*]Either right-click the Mailbox object and choose the [B]New Managed Folder Mailbox Policy… [/B]option, or choose the same option from the Action pane.[*]The [B]New Managed Folder Mailbox Policy[/B] wizard appears which consists of the screen that you see now plus the Completion screen. The first screen is shown below in Figure 10.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0021179497767224.jpg[/IMG]
[B]Figure 10:[/B] New Managed Folder Mailbox Policy Wizard

[LIST=1][*]On this first screen, give the managed folder mailbox policy a suitable name in the first field. Let’s assume that all of our managed custom folders are to appear in each user’s mailbox, so we’ll call this policy [B]Default Managed Custom Folders[/B].[*]In the [B]Specify the managed folders that you want to link to this policy [/B]area, click the [B]Add…[/B] button which then presents you with the [B]Select Managed Folder[/B] window. Here you will see all available managed folders, including both default and custom managed folders. I’ve added the Inbox, Old Inbox Items, Project X and Project Y custom managed folders. Note that you can shift or control-select multiple folders if required. Obviously we need to add the Inbox folder in order to ensure our Inbox managed content settings are applied. This won’t create the Inbox folder of course, since this is a managed default folder that already exists. This window is shown in Figure 11. Once done, click OK which returns you back to the previous window.[/LIST]
[B][IMG]http://www.msexchange.org/img/upl/image0031179497767271.jpg[/IMG]
[/B][B]Figure 11:[/B] Adding Folders to the Policy

[LIST=1][*]Clicking the [B]New[/B] button then presents the [B]Completion[/B] screen which also shows us the Exchange Management Shell (EMS) command used to create this policy. Clicking the [B]Finish[/B] button completes the wizard.[/LIST]
The EMS cmdlet for creating the managed folder mailbox policy is straightforward. It is:
[I]New-ManagedFolderMailboxPolicy -Name 'Default Managed Custom Folders' -ManagedFolderLinks 'Old Inbox Items','Project X','Project Y'[/I]
[B]Step 4: Apply Managed Folder Mailbox Policies[/B]

The penultimate step is to apply the managed folder mailbox policy that we just created to our users. As I stated earlier in step 3, let’s assume for this article that we want to apply our policy to all users. Perhaps the easiest way to do this is via the EMS, since we can easily deploy the policies to many mailboxes in bulk. A suitable cmdlet to deploy to all users the Default Managed Custom Folders policy that we just created is:
[I]Get-Mailbox | Set-Mailbox –ManagedFolderMailboxPolicy 'Default Managed Custom Folders'[/I]
You may remember from your PowerShell reading that in the above line we have piped the result of one cmdlet, Get-Mailbox, into the next cmdlet that sets the policies. Get-Mailbox is going to retrieve all mailboxes of course. You could do clever things like refining your selection to only include certain values set on specific Active Directory attributes. For example, you can retrieve all users who have their Active Directory [B]‘Title’[/B] attribute set to [B]‘Manager’[/B] via the following cmdlet:
[I]Get-User | Where-Object {$_.RecipientType -eq "UserMailbox" -and $_.Title -eq "Manager"}[/I]
You’ll note the use of the [B]UserMailbox[/B] recipient type, which targets all mailbox-enabled users, since we’re using Get-User this time rather than Get-Mailbox. To complete the entire cmdlet, we need to set the managed folder mailbox policy on the results, so the cmdlet becomes:
[I]Get-User | Where-Object {$_.RecipientType -eq "UserMailbox" -and $_.Title -eq "Manager"}| Set-Mailbox -ManagedFolderMailboxPolicy "Default Managed Custom Folders"[/I]
After executing your cmdlet, you may find warnings and errors recorded depending on certain circumstances. For example, you may see the warning shown in Figure 12 informing you that clients older than Outlook 2003 SP2 are not supported.
[IMG]http://www.msexchange.org/img/upl/image0051179497767271.jpg[/IMG]
[B]Figure 12:[/B] Set-Mailbox Warning
What happens in the situation where Exchange 2007 is coexisting with Exchange 2003? In such a situation, there’s a strong possibility that not all user mailboxes will have been moved to Exchange 2007 by the time the administrator creates MRM policies. If these policies are applied to all users, the error shown in Figure 13 will be displayed by EMS. As you can see, it is not possible to set the policy on an Exchange 2003 mailbox.
[B][IMG]http://www.msexchange.org/img/upl/image0071179498008021.jpg[/IMG]
[/B][B]Figure 13:[/B] Set-Mailbox Error
To apply managed folder mailbox policies via the EMC, follow these steps:

[LIST=1][*]Run the EMC.[*]Expand the [B]Recipient Configuration[/B] node and then click [B]Mailbox[/B].[*]In the result pane, locate the relevant user mailbox, right-click it and choose [B]Properties[/B] from the context menu.[*]With the user properties displayed, click the [B]Mailbox Settings[/B] tab.[*]Select [B]Messaging Records Management[/B] and then click the [B]Properties[/B] button.[*]In the resulting [B]Messaging Records Management[/B] window, select the [B]Managed folder mailbox policy[/B] check box and then click the [B]Browse[/B] button.[*]In the resulting [B]Select Managed Folder Mailbox Policy[/B] window, select the relevant policy. In our case here, we select the [B]Default Managed Custom Folders[/B] policy. Click OK.[*]Back at the Messaging Records Management window, you should see a screen similar to the one shown below in Figure 14.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0081179498008021.jpg[/IMG]
[B]Figure 14:[/B] Policy Enabled via EMC

[LIST=1][*]Click OK all the way back out to the main EMC window.[/LIST]
[B]Step 5: Schedule Managed Folder Assistant[/B]

Just creating the managed folder mailbox policy isn’t enough to get the managed custom folders created in each user’s Outlook or OWA client. To do this you must schedule the managed folder assistant to run on a mailbox server. In addition to creating the managed folders, the managed folder assistant also applies the managed content settings that we created in step 2 in part 1 of this article.
Here’s how to set the managed folder assistant using the EMC:

[LIST=1][*]Run the EMC.[*]Expand the [B]Server Configuration[/B] node and then click [B]Mailbox[/B].[*]In the result pane, locate the relevant mailbox server and right-click it. From the context menu, choose [B]Properties[/B].[*]From the resulting server properties window, click the [B]Messaging Records Management[/B] tab. This tab is very simple as you can see from Figure 15 below.[/LIST]
[IMG]http://www.msexchange.org/img/upl/image0091179498008021.jpg[/IMG]
[B]Figure 15:[/B] Mailbox Server Messaging Records Management Tab

[LIST=1][*]From here it’s just a case of clicking the [B]Customize…[/B] button and configuring when you want the managed folder assistant to run via the familiar schedule screen that you see so often when configuring Exchange.[/LIST]
If you don’t want to wait for the scheduled time to occur or if in the future you need to run the managed folder assistant on demand, you can perform a manual run via the following cmdlet:
[I]Start-ManagedFolderAssistant[/I]
Without any additional parameters specified, the above cmdlet will process all mailboxes on the local server. Optional parameters that you can include with the above cmdlet are:

[LIST][*][I]-DomainController[/I]. Use this parameter to specify which domain controller you’d like to use for the operation.[*][I]-Identity[/I]. With this parameter, you can specify which server you would like to process the mailboxes on.[*][I]-Mailbox[/I]. If you want to process an individual mailbox, use this parameter. You can specify this parameter using either the user’s email address, the user name in the domain\user format, or the mailbox GUID.[/LIST]
For example, to process the mailbox for User1 who’s a member of the NGH domain, you could use the following cmdlet:
[I]Start-ManagedFolderAssistant –Mailbox NGH\User1[/I]
When deciding on a suitable schedule for the managed folder assistant, be aware that Microsoft recommends that it does not occur at the same time as your backup or online database maintenance.
Finally, I’d like to finish this article by quickly covering what happens when you delete all the managed custom folders and managed folder mailbox policies. You’d think that this would remove the folders from the user mailboxes. What actually happens is that the Managed Folders root folder, plus all subfolders, are converted to normal folders that can then be removed by the user. Note from Figure 16 the change in the folder icons from those shown in Figure 1 from part 1 of this article.
[IMG]http://www.msexchange.org/img/upl/image0101179498008021.jpg[/IMG]
[B]Figure 16:[/B] Managed Folders Now Removable
[B]Summary[/B]

This completes our look at MRM in Exchange 2007. As you’ve seen, MRM allows the administrators and users to retain the information needed for business or compliance reasons and is a welcome addition to Exchange functionality. It’s not difficult to set up and configure but perhaps arguably the most difficult part of the implementation is going to be the planning involved in determining the required policies.

[/LEFT]