IT tutorials
 
Technology
 

Microsoft Exchange Server 2013 : Messaging records management (part 5) - Applying a retention policy to mailboxes

10/26/2014 9:11:03 PM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

Applying a retention policy to mailboxes

You can apply retention policies to mailboxes by:

  • Selecting mailboxes individually in EAC and editing the mailbox properties to assign a retention policy. This option is acceptable when you have to deal with only a few mailboxes. You cannot set a retention policy on a mailbox when it is initially created with EAC; this has to be done afterward, possibly because the use of personal tags in a retention policy requires an enterprise CAL. The standard CAL permits the use of default and folder tags in a retention policy.

  • Selecting multiple mailboxes and applying a Bulk Edit. This exposes options available for all the selected mailboxes in the action pane. The option to enable an archive for all the selected mailboxes is available through the More Options link at the bottom of the action pane.

  • Running the Set-Mailbox cmdlet to apply retention policies to a group of selected mailboxes. This is clearly a more efficient approach to take when you have to deal with more than a few mailboxes at one time.

When assigned to a mailbox, the policy becomes active the next time the MFA processes the mailbox. At this point, MFA writes the policy information into the mailbox. Until MFA processes the mailbox, the policy tags will not appear in the client user interface, so the lack of these tags is a good indication that the MFA has not yet gotten to a mailbox. You can force the issue by running the Start-ManagedFolderAssistant cmdlet as follows, passing the name of the mailbox you want MFA to process:

Start-ManagedFolderAssistant –Identity 'Tony Redmond'

If you’re setting a policy for a group of users (see Figure 9), you’ll probably do it in one operation by selecting the mailboxes with the Get-Mailbox cmdlet and piping the results to Set-Mailbox. For example:

Screen shot showing how to apply a retention policy to a mailbox by using EAC. This is done by selecting a mailbox, editing its properties, selecting Mailbox Features as shown here, and then selecting the retention policy to apply.

Figure 9. Assigning a retention policy to a mailbox

Get-Mailbox –Filter {CustomAttribute7 –eq 'Management'} | Set-Mailbox
–RetentionPolicy 'Management retention policy' –RetentionComment 'Management retention policy applies to this mailbox'

To discover the set of mailboxes that have retention policies in place, you can use a command like this:

Get-Mailbox –Filter {RetentionPolicy –ne $Null} | Format-Table Name, RetentionPolicy –AutoSize

Inside Out Only one retention policy—ever

A mailbox can only ever have one retention policy, so when you assign a retention policy to a mailbox, the action overwrites any policy that might already be in place. You can change retention policies multiple times on a mailbox, but this isn’t a good idea unless you really need to switch policies because the effect of the different policies might confuse users; the MFA responds to different retention settings in the different policies. Setting a value for the RetentionURL parameter is not compulsory, but it is a useful way to communicate how a user might find additional details about the company’s retention policy. This URL is visible only through Outlook 2010 and Outlook 2013 (Figure 10) and isn’t displayed by earlier clients or Outlook Web App.

Set-Mailbox –Identity 'TRedmond' –RetentionPolicy 'Management retention policy'  –RetentionComment 'Management retention policy applies to this mailbox' –RetentionURL 'http://Intranet.contoso.com/RetentionPolicies.html'

By looking at the parameters that set retention information with the Set-Mailbox command, you can see that the RetentionComment property provides the text you can see beside Account Settings. The RetentionUrl property populates the URL for the More Information link, hopefully taking the user to a website on which she can find some additional information to explain why a retention policy is necessary and what it means to the user. It is good practice to set up such a website and populate it with some practical examples of what a retention policy means to a user. For instance, it could explain to users that items in some of the default folders are automatically cleared to the archive after a certain period. Taking such a step might just save some expensive help desk calls!

The backstage area of Outlook 2010 and Outlook 2013 displays information about the retention policy that applies to the user’s mailbox if this information is provided by updating the RetentionComment and RetentionURL properties for the mailbox. In this case, the Management retention policy is in force. The URL is available if the user clicks the More Information link.

Figure 10. How Outlook shows retention policy information in its backstage area

It is common practice to set these properties when you place a mailbox on any type of hold (in-place or retention). These topics will be discussed in the following sections. For now, although you don’t have to set these properties to impose an effective retention regime, they are helpful to communicate information to users about what’s going on in their mailbox. Experience with many projects demonstrates that anything that assists in effective communications with users is likely to reduce help desk calls.

The value of $Null

When you want to remove a retention policy from a mailbox, you just set its policy to $Null. For completeness, it’s a good idea to also set the other properties associated with retention policies to $Null. Here’s the command:

Set-Mailbox –Identity 'JSmith' –RetentionPolicy $Null –RetentionComment $Null  –RetentionURL $Null

After you begin to deploy retention policies to mailboxes, the question arises of how to integrate the assignment of retention policies with any user provisioning process your company has in place. Unless you also enable an archive for a mailbox when it is created, Exchange won’t assign a default retention policy automatically, so an explicit administrative action is usually required to allocate a retention policy to a mailbox. This action is not difficult to code with EMS, but it is something that needs to be considered as part of your deployment plan.

Inside Out Managing retention policies and tags in a hybrid environment

If you run a hybrid environment in which some mailboxes are on-premises and some are on Office 365, you have to synchronize retention policies and tags from the on-premises organization to the cloud tenant domain to ensure that the same policy applies to all customers. You can create the retention policies and tags within Office 365 or you can use the scripts provided by Microsoft. Export-RetentionTags.ps1 exports details of retention policies and tags from an on-premises organization to a file in XML format, and Import-RetentionTags.ps1 imports the data from a previously exported file. Regretfully synchronization is not automatic and has to be done on a regular basis.

 
Others
 
- Microsoft Exchange Server 2013 : Messaging records management (part 4) - Creating a retention policy
- Microsoft Exchange Server 2013 : Messaging records management (part 3) - Naming retention tags, Creating retention tags
- Microsoft Exchange Server 2013 : Messaging records management (part 2) - System tags, Designing a retention policy, Managed Folder Assistant and retention policies
- Microsoft Exchange Server 2013 : Messaging records management (part 1) - Types of retention tags
- Microsoft Exchange Server 2013 : Compliance management - Archive mailboxes (part 3) - The default archive and retention policy , Disabling an archive mailbox
- Microsoft Exchange Server 2013 : Compliance management - Archive mailboxes (part 2) - Updating properties of an archive mailbox
- Microsoft Exchange Server 2013 : Compliance management - Archive mailboxes (part 1) - Enabling archives
- Sharepoint 2013 : Business Connectivity Services - Export and Import Models
- Sharepoint 2013 : Business Connectivity Services - User Profile Properties
- Sharepoint 2013 : Business Connectivity Services - Connecting to an OData Source
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us