Exchange 2010 Retention Tags

Hi folks,
I wonder if anyone can help please. I have applied a retention tag to automatically move staff emails to the Archive mailbox after 12 months and this policy has been in place now for a couple of years.
The company now wish for me to apply some option retention tags for staff allowing them to choose to e.g. Archive after 2 years, 5 years etc...
My question is that if a user chooses a folder in their live mailbox and selects Archive after 5 years, does that apply to emails just in the live mailbox or will the messages move back from their Archive mailbox to their live mailbox until the chosen Archive
period expires?
I hope this makes sense.
Many thanks
Danny

If you have items in the archive, there is no automated process to move those back into the live mailbox. So if you archive everything older than 1 year now, and change the setting to 5 years, you will see nothing moved to or from this folder
for the next four years.

Similar Messages

Exchange 2010 Retention Policy - Deleting Archived Items

Our current retention policy is configured to do the following
Archive all Emails for every user 3 Months or Older to a separate Archive Mailbox Database.
We then Perform Monthly, and Yearly backups of this Archive Database. Our Yearly's are 7 Year backups.
Since we will have the data backed up to tapes for 7 years we would like to purge the Archive Database of all Emails older than 2 years.
If I implement a tag of Permanently Delete -All other folders with an Age limit of 730 days would this remove the items from the "Archive Mailbox's" as we would like?

Yes. If you have any tags that delete items from the primary mailbox, they will also delete target items from the archive.

"Permanently Delete" fail in outlook client after setting up the "Archive and Retention Policy" in Exchange 2010

In Exchange 2010 server, we have setup a policy under "Default Archive and Retention Policy" as all messages under "Inbox", "Sent Items" and "Deleted Items" will be Permanently Delete after X months.
However, one of our client found that some of the email messages was still found under his "Deleted Items". All other email messages under her outlook client (2010) were successfully deleted according to the policy.
Is there any reason for this exception?
Thank you

Hi,
Based on your description, you created retention policy tags for Inbox, Sent Items and Deleted Items folders. Then you linked them to the default archive and retention policy
Default Archive and Retention Policy.
Please check if this issue affects all users.
Please create a different retention policy which is associated with these retention tags, and apply this policy to a test user to check result.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 - Archiving Policy tag (how to create dont move message)

Hi guys!
We have started to use functionality Archiving corporate Mailboxes.
We have deleted all the default retention policies/tags and created 1 default which Will move all the messages which are older then 60 days.
Soo default archive and retenetion policies are gone after deleting them.
Now the idea is to create 1 more retention policy tag, that user would manually chose what they do not wish to be moved to archive mailboxes and stay and instead of that those messages must stay in the mailbox.
Well we got stucked at how to create that kind of policy tag:
any hints would be more then appreticiated.
with best regards,
Bostjan
bostjanc

Hi,
Agree with Ed. We can't tag an item to stop it from being moved to archive.
Here is an article which can help you to understand the retention policy and retention tag for your reference.
Retention tags and retention policies
http://technet.microsoft.com/en-gb/library/dd297955(v=exchg.150).aspx
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Delete emails from a specific folder in Exchange 2010 SP1

Hi all,
Since Exchange 2010 SP1 does not have “-DeleteContent” parameter in mailboxexportrequest any more, how do we delete emails from a specific folder of a user mailbox? (Personal folder, not default folders).
Please note that the ASQ for searchquery in Search-Mailbox does not support “folder”.
If going for retention policy, is there a way to tag a retention policy to a specific folder of a user mailbox without user attention?
William Yang
William Yang

Hi William,
Yes, you may not run the Search-Mailbox to delete items in specific folder at the moment. Hope it will be back soon.
You can create a Personal tag, users can apply personal tags to folders they create. But users have to select related Retention Policy using Outlook or OWA manually.
For more information, please see:
Understanding Retention Tags and Retention Policies
http://technet.microsoft.com/en-us/library/dd297955.aspx
Frank Wang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Problem with Assigning Policy button in Outlook 2010 and Exchange 2010

First of all, I'm posting here because I'm not sure how to post in the previous version of Exchange forums.
Secondly, I'm re-posting this from the Outlook forums as I'm not getting any responses there despite of views.
Hi,
I'm having an issue in Outlook 2010 where I can't assign personal policies to folders. I have setup personal tags and added the mailbox to the right policy. I have also ran Start-MangedFolderAssistant in Exchange 2010 Shell against the mailboxes.
When I go into OWA, everything shows up perfectly, I can right-click and assign policies at will, but when I open Outlook 2010 then the Assign Policy button never appears. I force added it to the ribbon and I can see from there that the button stays grayed
out irregardless of where I click in the folder structure. I have even assigned the mailbox user Owner rights to all the folders to see if it will make a difference.
If anyone can help me solve this problem I will very grateful, I'm pulling my hair out here and I'm certain I could just be missing something very obvious somewhere,
It might be worth mentioning that the company has been using .prf files to configure Outlook thus far, I'm
looking to eliminate that. I'm not sure if that will have any effect on my current problem.
Thanks for your time.
Nico

Thanks for the reply Max, that's a pretty good link.
Like is I said though, I have the policies all set up in the Exchange configuration side of things, when I use OWA all the options for applying tags appear. It's just in Outlook 2010 Standard that the Assign Policy button stays grayed out.
Thanks.
EDIT:
This has been solved, looks like version problem with Outlook.
http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx

Exchange 2010 SP2 : Move calander entries and Task items from Archive mailbox to current active mailbox.

Hi,
After upgrade the exchange 2010 SP1 to SP2, all users calendar and task items entries also moved to archive mailbox from user's active mailboxes.
We like to move 90 days older emails to archive mailbox but not calendar & task items to be moved.
Any solution to move back those older archive calendar and task items to active mailbox users and also any settings to stop further to move calendar & task items to archive mailbox in SP2?
Thanks
MD

Hi,
Exchange 2010 SP2 RU4 added support for Calendar and Task Retiontion polices. For more information about that see the below blog post which also includes a workaround if you don't what these folders to be processed by MRM.
Calendar and Tasks Retention Tag Support in Exchange 2010 SP2 RU4
http://blogs.technet.com/b/exchange/archive/2012/08/14/calendar-and-tasks-retention-tag-support-in-exchange-2010-sp2-ru4.aspx
PS. Exchange 2010 SP2 is no longer supported.
Martina Miskovic

Retention Tags/Policy Issues

Hello,
We are using Exchange 2010 sp3. The tags/policies don't seem to work. I can see the "assign policy" option in owa but not in outlook. I set one up to delete items in the deleted items folder every day. it didn't work. we are using office 2010 home
and business. the link below shoes retention wont work with h&b 2010.
http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx
but i'm hearing that some folks are using h&b and having no issues at all.
any ideas?
thanks in advance,
alex

Hi,
Based on my knowledge, retention policies don't work with Microsoft Office Home and Business 2010. If you want to use retention policy feature, you need to upgrade.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 Excessive Archive Transaction Logs

I've got an Exchange 2010 environment with about 225 users over 6 mailbox DB's with corresponding Archive DB's.
They're seeing log files for the archive DB's growing by about 25-30% of the total DB size daily. Those logs are generally about 8 x the logs generated by the corresponding primary mailbox database.
Something like
DB1 = 20GB daily average logs 2GB
DB1Archive = 90GB daily average logs ~28GB
I don't see any Retention policies that have duplicated Tags and the Default policy has no tags assigned.
The customer wants to continue with their existing backup process of weekly fulls and daily incremental/differentials, and missing two days is enough to max out their transaction log volumes. (which are as large as their combined database size).
The archive db's have been in place for at least 12 weeks now so it's not just initial population, which is obvious by the fact that the archive db's are much larger than the original db's and the total logs in a week exceed the DB volumes by 2-3 times.

Hi,
First, please make sure there is no corruption in the retention policies.
If there is no corruption, I recommend you create a new archive mailbox database and move archive mailbox to this new database to check result.
Besides, here is a similar thread for your reference.
http://social.technet.microsoft.com/Forums/en-US/77845ba9-96c4-4b94-8d55-b47c51ef8974/exchange-2010-archive-transaction-logs?forum=exchange2010
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Apply retention tag to folder automatically

We are planning to migrate some mailboxes from Exchange 2007, which uses MRM 1.0, to Exchange 2010, which uses MRM 2.0 (Retention Tags and Policies).
Currently, with Exchange 2007/MRM 1.0 (Managed Folders), there is a "Retained Messages" folder that contains messages users want to keep.
Messages in this folder will *not* be deleted after 18 months (expiration date for messages *elsewhere* in the mailbox).
Good news is that even if we uncheck the Managed Folder Mailbox policy (in the mailbox properties), the "Retained Messages" folder remains (apparently as long as there are messages inside) and this "Retained Messages" folder
does migrate with the rest of the mailbox in test migrations to Exchange 2010.
The next part is the tricky part...
We intend to apply a Retention Policy to the migrated mailbox that currently has only one tag "Never Delete" (this is one of the built-in tags).
Before applying a default retention tag to the migrated mailboxes, we want to ensure that the "Never Delete" tag is applied to the migrated "Retained Messages" folder.
Of course, we could ask users to apply this tag and once it is applied, we could add a default tag to the policy that would delete messages after they attain a certain age (180 days, 18 months, whatever).
Is there a way we could apply this tag automatically, and avoid deletion of old messages, in case users forget to apply the "Never Delete" tag?
I saw this discussion...
https://social.technet.microsoft.com/Forums/exchange/en-US/97657e0c-c7f1-4c8e-bd7f-c7ecc9760e9c/push-a-folder-to-all-clients-apply-retention-tag-to-the-folder?forum=exchangesvrgenerallegacy
but am wondering if anything has developed since.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Hi David,
According to your description, my understanding is that you want to make sure “Never Delete” tag is applied to all “Retained Message” folder in all mailbox. Then when the mailbox is applied with other Default Policy tag, this “Retained Message” folder would
not be effected. Is it right?
Please confirm if the “Never Delete” tag is a personal tag created in Exchange 2010. Based on my knowledge, if it is a personal tag, the user can apply it in Outlook or OWA client instead of server side.
Additionally, there is a blog indicates that we can using Exchange Web Services to Apply a Personal Tag to a Custom Folder. I am not sure whether it works. Just hope it would be helpful for you:
http://blogs.technet.com/b/exchange/archive/2013/05/20/using-exchange-web-services-to-apply-a-personal-tag-to-a-custom-folder.aspx
Migrate from Managed Folders
http://technet.microsoft.com/en-us/library/dd298032(v=exchg.141).aspx
Regards,
Winnie Liang
TechNet Community Support

What personal retention tag is applied to folders

I am trying to use the code below to view the retention tags applied to folders in a given user's mailbox:
http://blogs.msdn.com/b/akashb/archive/2013/06/14/generating-a-report-which-folders-have-a-personal-tag-applied-to-it-using-ews-managed-api-from-powershell-exchange-2010.aspx
My environment:
2 x Exchange 2010 SP3 RU8v2 servers with CA, MB and HT roles. They are in a DAG.
1 x KEMP VLM-200 load balancer.
I downloaded and installed the EWS managed API:
http://www.microsoft.com/en-us/download/confirmation.aspx?id=35371
And I have seen what seems like every imaginable error message:
- The response received from the service didn't contain valid XML.
--> So I changed DNS so the URI in the script would connect directly to one of the two Exchange servers - and not the KEMP. Other solutions did not seem to work. This is a test env so I can "mess" with DNS.
- The request failed. The remote server returned an error: (403) Forbidden.
--> I think I solved this by adding https to the URI (the s in https was missing).
- The request failed. The remote server returned an error: (401) Unauthorized.
--> Not sure what I did here anymore (this has been taking me literally hours). But this error was replaced with the following:
- The account does not have permission to impersonate the requested user.
--> I was able to apparently solve this by granting a brand new user (not member of any admin groups with Deny permissions) the permissions described in this article:
https://msdn.microsoft.com/en-us/library/bb204095%28v=exchg.80%29.aspx
Even though that is for Exchange 2007 and I have 2010.
That seemed to work because that error messages no longer appears but... now this one appears again:
- The request failed. The remote server returned an error: (401) Unauthorized.
I've tried after granted the new user full permissions to the mailbox in question and without those permissions.
So in the end, I'm going in circles and I don't know how to make this work.
How can I see WHY the user is not authorized?
Does the user have to be a member of specific groups? I intentionally did NOT add them to any admin type groups because of what was stated in the MSDN article on impersonation (some admin groups have DENY permissions on user mailboxes).
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

These are the only lines of the code I have edited:
# Set the Credentials
$service.Credentials = new-object Microsoft.Exchange.WebServices.Data.WebCredentials("newuser1","Passwordabc123","mydomain.lan")
# Change the URL to point to your cas server
$service.Url= new-object Uri(https://mail.mydomain.net/EWS/Exchange.asmx)
I have also tried:
$service.Credentials = new-object Microsoft.Exchange.WebServices.Data.WebCredentials([email protected],"Passwordabc123")
Yes, I have mydomain.lan (original domain name) and mydomain.net (for email).
For better or worse, newuser1 is only a member of domain users (but currently has full access permissions to target mailbox).
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2010 - The certificate status could not be determined because the revocation check failed.

I have tried everything I have found online to get my DigiCert to work.
I have exported the cert and imported it into my child domains and they look perfect.
It is just my parent domain having issues.
netsh winhttp show proxy
does show my correct proxy server for http and https and port 8080
I have tried name, FQDN and IP address.
In the Bypass-list I have tried none, *.domain.com, and a list of all domains and child domains in my forest.
I have flushed the cache
certutil -urlcache crl delete
certutil -urlcache ocsp delete
and rebooted the Exchange 2010 (Windows 2008 R2) server
No matter what, I still see in my Server Configuration for the parent domain's DigiCert cert the message
The certificate status could not be determined because the revocation check failed.
with a red X on the left hand icon. Again, Child domains all say "The certificate is valid for Exchange Server usage."
Note: In spite of having the red X, I was able to assign via EMS the services.
Webmail works fine. Outlook Anywhere fails... I suspect it is due to my red X problem.
Suggestions?
Thanks in Advance
Jim.
Jim.

I have contacted DigiCert and they said the cert is working per their utility, hence the problem is outside the scope of their support.
I have followed, several times, http://support.microsoft.com/kb/979694
http://www.digicert.com/help/ reports all is well.
The DigiCertUtil.exe reports all is well and happy.
I have run
netsh winhttp set proxy proxy-server="http=myproxy:8080;https=myproxy:8080" bypass-list="*.mydomain.com"
Current WinHTTP proxy settings:
Proxy Server(s) : http=myproxy:8080;https=myproxy:8080
Bypass List : *.mydomain.com
I have flushed the cache using the commands
certutil -urlcache crl delete
certutil -urlcache ocsp delete
I still see in my Server Configuration for the parent domain's DigiCert cert the message
"The certificate status could not be determined because the revocation check failed."
with a red X on the left hand certificate icon.
To verify the cert via command line:
certutil -verify -urlfetch c:\mail_domain_com.cer
LoadCert(Cert) returned ASN1 bad tag value met. 0x8009310b (ASN: 267)
CertUtil: -verify command FAILED: 0x8009310b (ASN: 267)
CertUtil: ASN1 bad tag value met.
I suspect this is why I cannot get Outlook Anywhere to connect.
Child domains show a happy certificate icon. Parent domain does not.
Still scratching my head.
Thanks all!
Jim.

Event IDs 136 and 137 0x80000000000000 in System Log on Windows 2008 R2 Server, Exchange 2010 in Cluster

Hi,
I'm having an issue with one of my exchange 2010 Servers. We had a power outage and upon recovery, I cannot start Services Net.Pipe Listener Adapter and Net.Tcp Listener Adapter (And thus cannot Start IIS and provide Exchange Client Services.) This is a
physical server (Not VMWare or Hyper-V)
The System event log has lots of Event 136's and 137s on Ntfs with the keyword - 0x80000000000000 - The General Messages are: The default transaction resource manager on volume C: encountered an error while starting and its metadata was
reset. The data contains the error code.
and
The default transaction resource manager on volume OS encountered a non-retryable error and could not start. The data contains the error code.
XML Output as follows:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Ntfs" />
<EventID Qualifiers="32772">136</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-11-17T18:10:37.788942300Z" />
<EventRecordID>315532</EventRecordID>
<Channel>System</Channel>
<Computer>server.domain.com</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>C:</Data>
<Binary>1C00040002003000020000008800048000000000060019C000000000000000000000000000000000060019C0</Binary>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Ntfs" />
<EventID Qualifiers="49156">137</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-11-17T18:10:37.788942300Z" />
<EventRecordID>315531</EventRecordID>
<Channel>System</Channel>
<Computer>server.domain.com</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>OS</Data>
<Binary>1C0004000200300002000000890004C000000000020100C000000000000000000000000000000000020100C0</Binary>
</EventData>
</Event>
When I attempt to start the services - I get the following errors:
The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error:
Transaction support within the specified resource manager is not started or was shut down due to an error.
The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error:
Transaction support within the specified resource manager is not started or was shut down due to an error.
I have tried the "fsutil resource setautoreset true" fix without success.
Any ideas or direction would be much appreciated. Restoring this server will be extremely difficult.
Thanks!

We can close this question.
From an elevated prompt, I ran 'fsutil resource setautoreset true' and attempted to remove the files with .blf and regtrans-ms file extensions from C:\Windows\System32\config\TxR. but these files were locked by system processes. (They are also
tagged with the hidden file attrib so you may not see them at first)
So, I booted the system with a Windows 2008 R2 Install Disk, selected repair OS and selected the command prompt. I then performed a chkdsk /f c: and selected "Y" to unmount the drive. It made some repairs.
With the system booted from the install disk, and chkdsk executed, the locks were freed and I was able to delete the files from C:\Windows\System32\config\TxR.
Once the system rebooted, the services came back fine and everything was back to normal.

Retention tags not working if mailbox has another language than english

Hi folks
I've created a retention tag (type: Inbox ) in exchange 2013 which deletes all mails older than 14 days. works perfectly for mailboxes with english standart folders, but if i apply the policy to an mailbox with german or french language, the emails
are not getting deleted. i think the problem is that the inbox folder is called "Posteingang" in the german mailboxes.
is there a workaround to use my retention tag for other languages as well?
Thanks!

Hm, that sounded interesting enough for a test, but since I'm an O365 guy, I run the test against EO. Works OK even after I rename the folders, the only thing I did was to simply run the Start-ManagedFolderAssistant cmdlet to speed up the process.
EO is usually few versions ahead of on-prem, so either this has been fixed (and the fix is coming with CU7 or later), or we are simply missing something in your scenario. Have you verified that the policy is actually recognized as 14 days by the client,
for the non-English mailboxes? Double-check the tag and policy, and run the Start-ManagedFolderAssistant just in case.

How to force Outlook's Junk email fitler to not filter Exchange 2010 SP1 accepted domains?

Hello,
I wonder if there really is no way how to reach the result described in the title question. Because
http://support.microsoft.com/kb/2458522 says:
This issue occurs because of a functionality change that is introduced in Exchange Server 2010 SP1. In Exchange Server 2010 SP1, domains that are configured as accepted domains are no longer allowed in the junk email lists of a mailbox.
So please tell us Microsoft how can we force Outlook to accept internal domain as a trusted senders and not apply Junk email filter on it?
There was already a long discussion about the steps here
http://social.technet.microsoft.com/Forums/en-US/outlook/thread/15f857c6-0ed4-4004-9d90-cb5d16361752 so please don't offer anything described there.
Thank you,

Trying to deal with the Outlook Junk Email Filter is not very easy and had been a pain in the butt.
The ONLY way to ensure the Outlook 2010 Junk Email filter honors "white listed" emails is to stamp the email with SCL -1. Setting a transport rule will do that but it is not very flexible.
I was able to resolve these issues by simply enabling the Exchange 2010 Anti-Spam agents on each hub transport server. We have no Edge Server but we use a couple of Ironports at the gateway which provide the bulk of AntiSpam. We didn't think we would
need the Exchange AntiSpam so we hadn't initially enabled. After months of trying to resolve people's complaints of emails from internal system ending up in Junk, this solution worked for us.
This is the order in which it was done.
1. We set the receive connectors for the internal systems for bypassing Anti Spam. We basically have 2 receive connectors, one for internal system with no relay, and one for internal systems who are allowed external relay.
Get-ReceiveConnector "server\name of the recieve connector" | Add-ADPermission -User "“NT Authority\Anonymous Logon” -AccessRights ExtendedRight
-ExtendedRights ms-exch-bypass-anti-spam
Note: If you use SMTP Authentication, Exchange will only mark the emails as "Internal" and not assign a SCL of -1. It can only be on anonymous connections.
Note: We have a separate receive connector for the Ironports delivering external email that will not bypass Anti-Spam. These emails will receive a SCL rating of 0-9
2. We set the global SCL to 6 (default is 4). You can set it to whatever you want.
Set-OrganizationConfig -SCLJunkThreshold 6
So basically, any email tagged with SCL 7-9 will be moved to Junk by Exchange.
3. Set-ContentFilterConfig -SCLQuarantineEnabled $False -SCLDeleteEnabled $False -SCLRejectEnabled $False
We don't want delete, reject or quarantine anything on Exchange. Just move email to Junk folder if SCL 7-9 and have user deal with it.
4. Set the Internal SMTP Servers by adding each Exchange server's IP Address to the Global Transport Settings. I used EMC, Organization Config, Global Settings, Transport Settings properties, Message Delivery tab. Do NOT add any other "internal" servers
here, only the Exchange servers.
5. Then we installed the AS agents on each HT Server.
Starting with the first server
Stop MSExchange Transport service
D:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\install-AntispamAgents.ps1
After installation, disable all the agents except for Content Filtering Agent. This agent has to be enabled for Exchange to stamp the email with SCL -1. I used EMC, Organization Config, Hub Transport. You will see a new tab called Anti-Spam. Disable everything
except Content Filtering.
Start MSExchange Transport service.
Repeat on each HT server. (You won't have to repeat the disabling of the agents as that is a global setting)
6. You can add global safe senders by doing the following.
$list = (Get-ContentFilterConfig).BypassedSenders
$list
$list.add("[email protected]")
$list.add("[email protected]")
Set-ContentFilterConfig -BypassedSenders $list
The message headers are stamped with
For emails sent through the Internal connector
X-MS-Exchange-Organization-Antispam-Report: MessageSecurityAntispamBypass
X-MS-Exchange-Organization-SCL: -1
OR
For external emails from a safe sender
X-MS-Exchange-Organization-Antispam-Report: ContentFilterConfigBypassedSender
X-MS-Exchange-Organization-SCL: -1
OR
For all other external emails
X-MS-Exchange-Organization-SCL: 0
Good Luck. This has basically stopped all the calls about "legitimate" email in Junk Email folder.

Exchange 2010 Retention Tags

Similar Messages

Maybe you are looking for