Great details, thanks very much!

Regards,


[logo]


Rami SIK

Systems Specialist and Security Officer

British Columbia Securities Commission

1200 - 701 West Georgia Street

Vancouver, BC V7Y 1L2


Tel: 604-899-6853

Fax: 604-899-6506

www.bcsc.bc.ca<http://www.bcsc.bc.ca/>

Email: [email protected]<mailto:[email protected]>

Find us on: Twitter<https://twitter.com/BCSCInvestRight> | 
Facebook<https://www.facebook.com/BCSCInvestRight> | 
YouTube<https://www.youtube.com/user/BCSCInvestRight>




[environ]Please consider the environment before printing this email



From: [email protected] [mailto:[email protected]] On 
Behalf Of Adam Farage
Sent: Thursday, December 04, 2014 5:07 PM
To: [email protected]
Subject: RE: [Exchange] implementing Retention policy on Exchange 2013CU6

This would be a default policy tag, which tags all data within the mailbox 
(except for Calendar I believe.. someone correct me if I am wrong). Something 
to keep in mind is if you are using an online archive, the default policy tag 
also applies it self there, or at least in Exchange 2010 it did. So if you set 
a default policy tag to delete any item after 10 years it will also delete the 
items within the online archive as the managed folder assistant is going to tag 
those with a tombstone date, and when that date is met it will take its action 
(which is the action set on the tag).

Its a pretty simple process:

  1.  Create a default policy tag
  2.  Create a retention policy for the default policy tag you made
  3.  Apply the retention policy to a test mailbox (I use mine typically, or a 
copy of my mailbox) and then force run the Managed Folder Assistant
  4.  If that goes well and the business approves, apply it to all.. then wait 
for the "oh gosh my email disappeared" calls to come in from the users :)


The managed folder assistant basically takes care of the retention policy stuff 
on the backend. Its a throttled service, so if you want it to run right away 
against a particular mailbox you can use the command 
Start-ManagedFolderAssistant [email protected]<mailto:[email protected]> 
(for example).



To apply the retention policy across all mailboxes org-wide:



Get-Mailbox -ResultSize Unlimited | Set-Mailbox -RetentionPolicy "name of 
retention policy you created"



You can then verify by doing..


Get-Mailbox -ResultSize Unlimited | Select DisplayName, RetentionPolicy | 
Export-CSV C:\RetentionPolicyVerification.csv


You "technically" do not need to start the managed folder assistant on the 
mailbox, as it will scan it eventually.. but you can force it to run if you 
want:



Get-Mailbox -ResultSize Unlimited | Start-ManagedFolderAssistant


... just make sure to test first. I have been on calls when I was a field 
engineer where a person did this (create a default policy tag, apply it to all 
execs as they asked.. but they asked for a default retention of 7 years not 
days) and it turned into a disaster to recover from.


________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: RE: [Exchange] implementing Retention policy on Exchange 2013CU6
Date: Thu, 4 Dec 2014 16:53:51 -0800
Short answer: yes
Longer answer: 
http://technet.microsoft.com/en-us/library/dd297955%28v=exchg.150%29.aspx
________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] implementing Retention policy on Exchange 2013CU6
Date: Fri, 5 Dec 2014 00:47:07 +0000
Hi All,

I am tasked to implement a retention policy for all mail items of X year 
company wide. I was looking into the default policy on the server, and I was 
wondering if the default policy is enough for both default folders and user 
defined folders?
Any feedback in general based on your experience with the retention policies 
appreciated.

Thanks,

Rami


________________________________

If this message is not meant for you, do not use it - please let us know, and 
then delete it. We try hard to keep our messages and attachments free of 
viruses and other malicious programs, but are not liable if our precautions 
don't prevent their spread.

Reply via email to