IT tutorials
 
Technology
 

Microsoft Exchange Server 2013 : Messaging records management (part 4) - Creating a retention policy

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

Creating a retention policy

Now that you have created the necessary retention tags to help managers impose order on their mailboxes, you can create a new retention policy. Under the Compliance Management section of EAC, choose Retention Policies and click New (+). You have to name the retention policy and add the set of retention tags that enable the new policy to impose some level of retention compliance on the users to whom you assign the policy.

Retention policy names are entirely internal and are never revealed to users. The major step in building the policy is to scan the set of available tags and select the necessary ones (Figure 6). When the required tags are selected, click OK to return to the initial screen and then Save to create the new policy. EAC then checks to ensure that the set of tags is valid and that you haven’t done something such as specifying two default retention tags or two folder tags for the same folder.

The dialog box EAC displays to enable retention tags to be added to a policy. All the available tags are listed, and the administrator can choose those he wants to include in the policy. Clicking OK adds the selected tags to the policy.

Figure 6. Adding retention tags to a retention policy

When EAC returns to Compliance Management, you should then see something like Figure 7 with the new policy listed in the set of retention policies defined for the organization and the set of retention tags used by the policy shown in the action pane.

A screen shot showing how EAC displays details of a new retention policy after it is created. The details pane shows all the retention tags that are incorporated in the policy.

Figure 7. Reviewing the tags in a new retention policy

You can also create retention policies through EMS by using the New-RetentionPolicy cmdlet. In this command, you create the policy and associate the 11 tags you want to use with the new policy. Don’t worry about uppercasing the tag names as defined. EMS can locate tags as long as you spell their names correctly.

New-RetentionPolicy –Name 'Management Retention Policy' –RetentionPolicyTagLinks 'Archive after 2 years', 'Calendar 5 years', 'Delete after 5 years', 'Deleted Items 7', 'Inbox 30', 'Junk Mail 3', 'Keep for Audit', 'Retain for 10 years', 'RSS Feeds 3', 'Sent Items 30', 'Sync Issues 1'

You can examine details of the new retention policy with the Get-RetentionPolicy cmdlet:

Get-RetentionPolicy –Identity 'Management retention policy' | Format-List

Some of the properties Get-RetentionPolicy reveals apply to Exchange Online only. For example, Exchange Online enables administrators to mark a retention policy as default (IsDefault = $True), meaning that Exchange applies this policy to users’ mailboxes if another retention policy isn’t assigned.

Provided there is good reason for each tag to exist in the policy, a 10-tag policy composed of some folder tags, a default tag, and some personal tags is a reasonably simple retention policy because other policies can incorporate a lot more tags to create a very exact retention environment for a user to operate within. You might have more tags than this if you decide to include a retention policy tag for every default folder. Using retention policy tags to clean out items that otherwise accumulate and are never cleared out in default folders such as Sync Issues, Junk E-Mail, and RSS Feeds is a good example of where you can gain real value from a well-designed retention policy.

Inside Out Good reasons to limit the number of tags in a policy

Microsoft recommends that you have no more than 10 personal tags in a policy; otherwise, you might confuse users with too much choice. (Only personal tags usually show up in client user interfaces, hence the focus on these tags.) This is reasonable advice, but as with most advice, there will be times when you need to incorporate more tags in a policy to meet specialized business needs. A more sophisticated policy for a department might have separate retention tags for many of the default folders, a set of personal tags developed specifically to suit the retention needs of the department, and a default retention tag for everything else. User interface constraints are another good reason for limiting the number of tags in a policy. If you have five personal tags or fewer in a policy, there’s a reasonable guarantee that Outlook Web App can display all the tags in its user interface. However, if you include 20 personal tags in a policy, you’ll find that Outlook Web App cannot list all the tags, and some will simply drop off the end of the available list. This is especially true when you consider the relatively small display screen of some of the devices that Outlook Web App now supports.

Outlook 2013 takes a different approach from Outlook Web App by displaying up to 10 personal tags when a user selects an item, right-clicks, and selects Assign Policy from the shortcut menu. This list includes an entry for More Retention Policies that reveals the full set of personal tags defined in the policy. As you can see from the rightmost screen in Figure 8, the full set of retention tags for the policy assigned to a mailbox contains 14 tags, many of which are of dubious value. Using a separate dialog box keeps the Outlook user interface under control while still permitting users to discover all the tags available in a policy at the expense of requiring separate clicks and additional knowledge of where to find the tags. For all these reasons, it’s just a bad idea to create a tag-filled policy.

To illustrate how the Outlook user interface might struggle to deal with a large number of personal tags in a policy, two screen shots show how a policy that contains 14 tags is displayed from the context-sensitive menu revealed when a user right-clicks a selected item (the screen on the left) and when he uses folder properties to set a retention policy.

Figure 8. How Outlook 2013 displays the full set of personal tags to users

Inside Out Calendar and Tasks

Although retention policies support tags for calendar and task items, no client currently exposes the necessary user interface to enable users to apply policies to these folders. In some respects, this is a good thing because it means that administrators are the only people who can set a retention policy for these important folders. Some might disagree because they want to apply a different retention policy, but that’s the current situation.

 
Others
 
- 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
- Sharepoint 2013 : Business Connectivity Services - External Data Columns
 
 
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