Exchange 2013 archiving

Hello,
i have a problem with exchange 2013 in-place archiving.
Archive mailbox is in different database that mailbox database.
Yesterdey i have activated archiving for a first mailbox; when i activated archive many "Not read" message were sent.
Seem that when archive is active message sent to user that have request of read but that have not answer like "read" for the user when they are stored in archive mailbox send out reply to sender with "Not read: " in the subject.
I have checked "retention policy" and "retention tags" properties via exchange management shell but i did not find any field to disable unread in archive or something like.
Please can i have support for this problem?
Thanks  in advance.

Hi,
Before going further, I’d like to confirm how many senders are affected by the issue.
Please check if there is any Outlook rule about the unread message notification.
And we can also check if the sender select the option “always send read receipt”:
File>options>mail>tracking
Best regards,
Angela Shi
TechNet Community Support

Similar Messages

  • Exchange 2013 Archive mailbox best practise

    Current senario:
    Migrating to Exchange 2013 CU3 from lotus Domino
    in lotus domino the customer is having huge archive files(nfs file size is around 30 GB, like wise users are having multiple archive file with same size.)
    Requirement is all these file need to migrated to exchange 2013 CU3. whcih we are taking care by using thrid party tool.
    My concern is exchang e2013 support for huge mailbox size. if so what maximum size supported for online mailbox and archive mailbox.
    can I assign multiple archive mailbox to users.
    we have got separate Exchange 2013 archive server in place
    We would like know the best practise/guide line for archive mailbox/live mailbox size.
    refered below link:
    http://blogs.technet.com/b/ashwinexchange/archive/2012/12/16/major-changes-with-exchange-server-2013-part-1.aspx

    The key decision is that the content in the primary mailbox is synchronized with the client when in cached mode, while the content in the archive is not.  So I'd want to keep the primary mailbox populated with the content the user needs on a daily basis,
    and put the rest in the archive.  Unfortunately, that answer is not a number, and it isn't the same for all users.
    Each user can have zero or one archive mailboxes, not multiple.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 Archiving question

    Hi all,
    I have a question on Exchange 2013 Archiving. 
    In the Default MRM Policy it has the Default 2 year move to archive tag. 
    When this runs it moves any emails over 2 years old to the users Archive mailbox. 
    I also know it will recreate the folder structure that was in the inbox. 
    My question is once it's moved to the users Archive what policy is applied to the emails and folders by default? 
    When you look at them it just says Using Parent folder Policy. 
    Would the parent folder be the Archive - %username it's self?  Or is nothing applied and the users must go in a assign a tag to it?
    Thanks

    Hi,
    If you apply one retention policy to a mailbox, then this retention policy will be applied to the primary and archive mailbox, this means that the archive mailbox have the same retention policy as primary mailbox.
    Here is an example to help you to understand this.
    You can use a DPT with the Move to Archive action to move items to the archive mailbox in two years, and a DPT with a deletion action to remove items from the mailbox
    in seven years. Items in both primary and archive mailboxes will be deleted after seven years.
    You can refer to the following article for more information.
    http://technet.microsoft.com/en-gb/library/dd297955(v=exchg.150).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 - Archive RESTRICTION

    Hello All my Exchange MS Expert, 
    I have a customer requirement --> My customer want to restrict all user in their organization not to delete archive item from their archived mailbox? can we achieve this through security
    option / from ADSI edit??? I have suggested them to go with inplace-hold but not wanted in-pace feature instead they need if a user want to delete any archived item they should get message saying "you don't have appropriate" permission
    / unable to delete.
    I have open a Microsoft advisory Case: they told me to give some time to work on this requirement for test and will comeback to me.
    Friends if you have any suggestion pls pass me. Much appreciate your valuable input.

    Hello All my Exchange MS Expert, 
    I have a customer requirement --> My customer want to restrict all user in their organization not to delete archive item from their archived mailbox? can we achieve this through security
    option / from ADSI edit??? I have suggested them to go with inplace-hold but not wanted in-pace feature instead they need if a user want to delete any archived item they should get message saying "you don't have appropriate" permission
    / unable to delete.
    I have open a Microsoft advisory Case: they told me to give some time to work on this requirement for test and will comeback to me.
    Friends if you have any suggestion pls pass me. Much appreciate your valuable input.
    Exchange doesn't work that way. Using litigation hold/ Single Item Recovery is the only supported method.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 - Folders missing when importing PST to archive mailbox

    Hello,
    I'm having an issue when importing PST files to an Exchange 2013 archive mailbox using the command "New-MailboxImportRequest
    test -FilePath '\\server\e$\ArchiveExport\test.pst' -IsArchive -BadItemLimit 5 -ErrorAction Stop"
    The import is running without an error and shows the status complete. The size of the archive mailbox is exactly the same like the size
    of the PST file!
    But when I check the users archive mailbox some folders are missing. It seems that this happens only to default folders like "Inbox"
    or "Sent Items". Other folders are visible.
    The mailbox import log shows the following:
    16.01.15 16:31:56 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.
    16.01.15 16:31:56 [server] Copying 3 items, 4.789 KB (4,904 bytes). Skipping 0 items, 0 B (0 bytes).
    If I start the import process again the log says the following:
    16.01.15 16:46:54 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.16.01.15
    16:46:54 [server] Copying 0 items, 0 B (0 bytes). Skipping 3 items, 4.789 KB (4,904 bytes).
    So it seems that the mails are really there but just not visible.
    I did some tests:
    When  I import the PST file directly to the users mailbox (without parameter -IsArchive) I can see all content of the PST file.
    When I add the parameter -TargetRootFolder "Testfolder" the whole PST content shows up correctly under that folder.
    Can anyone explain this?
    Regards

    Hi PhilippMair,
    Thank you for your question.
    If all subfolders were merged, we could use OWA to check if the missing folders is appeared. If we could see missing folders by OWA, I suggest we recreate outlook profile and reset outlook view.
    In order to troubleshooting, I suggest we collect the import log to analysis if the subfolder of Inbox or Sent Item is exported.
    In my test lab, inbox has three subfolders, there are 123,456,789; when I import PST file, I will see the following log:
    1/20/2015 7:32:31 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox' into '/Top of Information Store/Inbox'.
    1/20/2015 7:32:31 AM [EXCH2-CU1] Copying 18 items, 302.3 KB (309,594 bytes). Skipping 0 items, 0 B (0 bytes).
    1/20/2015 7:32:32 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/123' into '/Top of Information Store/Inbox/123'.
    1/20/2015 7:32:32 AM [EXCH2-CU1] Copying 5 items, 62.21 KB (63,699 bytes). Skipping 0 items, 0 B (0 bytes).
    1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/456' into '/Top of Information Store/Inbox/456'.
    1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 6.908 KB (7,074 bytes). Skipping 0 items, 0 B (0 bytes).
    1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/789' into '/Top of Information Store/Inbox/789'.
     1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 21.31 KB (21,820 bytes). Skipping 0 items, 0 B (0 bytes).
    We could check if there are any subfolder which would not be merged and copied. If your import log has any abnormal, I suggest you send log file to
    [email protected] for our troubleshooting.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Archiving migration from Symantec EV to Exchange 2013

    Hi all,
    We have a customer who has Exchange 2007 email system and Symantec EV 7 for archiving email. We need to migrate their email from Exchange 2007 to Exchange 2013 and activating Exchange 2013 archives. The customer asks to use this tool "Archive
    2-Anywhere" from Archive360 to migrate archives from Symantec EV to Exchange 2013.
    My question is I need to do this (migrating a user mailbox archive) in parallel with moving his mailbox to new exchange?

    Search the Internet for a phrase like "Migrate Enterprise Vault to Exchange 2013".  You should get some hits for ideas for third-party solutions.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • What is the best backup plan for Archive Databases in Exchange 2013?

    Hi,
    We have Exchange 2013 with Hybrid setup with O365.
    We have On premise exchange 2013 servers with 3 copies of primary Database & Single Copy of Archival DBs.
    Now we have to frame backup policy with Symantec Backup Exec which has to backup our primary & Archival DBs
    In 2007 exchange, before migration to 2013, we had policy of DBs - Weekly Full backup & Monthly Full Backup
    Please suggest what would be the best possible backup strategy we can follow with 2013 DBs.
    That too, especially for Archiving DBs
    Our Archiving Policy are - 3 category - Any emails older than 6 month OR 1 Year OR 2 Year should go to Archive mailbox.
    Keeping this in mind how to design the backup policy ? 
    Manju Gowda

    Hi Manju,
    you do not find best practice different from the common backup guidelines, as there is no archive db specific behaviour. Your users may move items to their archive at any time as well as your retention policies may move items that machted the retention policies
    at any time. The result is frequently changing content to both, mailbox and archive mailbox databases, so you need to backup both the same way. You also may handle archives together with mailboxes together in the mailbox db 
    Please keep in mind that backup usually means data availability in case of system failure. So you may consider to do a less frequent backup with your archive db with dependency to the "keep deleted items" (/mailboxes) setting on your mailbox database.
    Example:
    keep deleted items: 30 days
    backup of archive db: every 14 days
    restore procedure:
    * restore archive DB content
    * add difference from recover deleted items (or Backup Exec single item recovery) for the missing 14 days.
    So it depends more on your process than on a backup principle.
    Regards,
    Martin

  • Outlook 2010 clients cannot access their Online Archive mailbox in Exchange 2013??

    Hello,
    I have an issue where my Outlook 2010user cannot see/access their Archive mailbox when they are migrated from Exchange 2010 to Exchange 2013.
    Both the live and archive mailbox is in Exchange 2013, the user can launch Outlook but if they click on their Archive mailbox it is unavailable.
    Once the user is upgraded to SP2 or Outlook 2013 they have no issues accessing their archive mailbox.
    These users have the minimum required Outlook version (14.0.6126.5000),
    they are running 14.0.6129.5000.
    Is there a different requirement on the Outlook client if the user has an archive mailbox in Exchange 2013 as well?
    Thank you.

    Hi,
    Is there any update on this thread?
    Thanks,
    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]
    Simon Wu
    TechNet Community Support

  • In what way Exchange Server 2013 archiving is better than the other 3rd party application ?

    Hi All,
    Can anyone here please share some thoughts and comments regarding of which feature of Exchange Server 2013 archiving is better than the 3rd Party application like Symantec Enterprise Vault ?
    Any comments and suggestion would be greatly appreciated.
    Thanks
    /* Server Support Specialist */

    It's free.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    yes, as long as we are using the Exchange Server 2013 Enterprise Edition.
    /* Server Support Specialist */

  • Archiving on exchange 2013

    Hi everyone,
    our group (which uses  mobile sales system) is actually on Lotus notes and i am exploring features of exchange 2013 so that we can have necessary arguments to move to it. (Any help on that would be most welcome)
    Actually we have our archives locally (on the clients) and no back is done .  So if we have a hardware issue or any of the kind we lose all the mails.
     I would need from exchange to have the archive available from anywhere and also available offline from the client side.
    Is it possible and how can we do it?

    You cannot use Exchange archive, because they dont fullfill one of your need : "also available offline ".
    Exchange Archive cant be cached on client side, so you can only access them being connected to Exchange (trough OWA or OA). They arent avalaible as well in ActiveSync (and probably BES).
    Bruce Jourdain de Coutance - Consultant Exchange http://brucejdc.blog.free.fr
    So when user using iPad or iPhone through Active Sync, they cannot access the archived item on Exchange Server 2013 ?
    /* Server Support Specialist */

  • Primary mailbox (on Exchange 2010) and Personal Archive (on Exchange 2013), possible?

    Current environment is Exchange 2010 SP3 RU5 supporting 4,000 Users. Client estate is Outlook 2010 SP1 going on SP2.
    We're pulling our Archiving solution away from 3rd party and back into Exchange. Implementing a new set of Exchange 2010 Servers (old DAG or in a new Archive DAG) would be easy. But is there Exchange 2013 stepping stone potential?
    Can the Archive DAG / Archive mailboxes be on 2013? i.e. for any given User, leave their primary mailbox on Exchange 2010 and create new Archive mailbox on 2013.
    I want to avoid implementing 2010 Archive Servers and then go 2013 Archive 6 months or a year later.
    This article suggests 'no':
    http://technet.microsoft.com/en-gb/library/dd979800(v=exchg.150).aspx
    "Locating a user’s mailbox and archive on different versions of Exchange Server is not supported."
    I've found little info but the odd statement here / there.
    Is this the latest position? Is it that cut & dry? Anyone tried it? Why won't it work (or will it but it's not supported)?
    Thanks!

    <I had a response from MS>
    Below is a summary of the case for your records:
    Symptom:
    =============
    Is it possible to implement a 2013 environment to host the Archive mailboxes? i.e. for any given User, their primary mailbox is on Exchange 2010 and their Archive
    mailbox is on 2013. 
    Resolution:
    =============
    It’s not supported to have a user’s primary mailbox reside on an older Exchange version than the user’s archive. If the user’s primary mailbox is still on Exchange
    2010, you must move it to Exchange 2013 before or at the same time when you move the archive to Exchange 2013.
    http://technet.microsoft.com/en-us/library/jj651146(v=exchg.150).aspx
    as per the repro in our lab, having the archive mailbox in higher version of exchange would fail with the error above
    <the scenario isn't completely relevant, looks like he's trying to put the Primary on 2013 and not the Archive, no matter, we've established there are problems, question is whether they are looking into this area / to patch, they go on...>
    At this point in time we don’t have a conformation from the product team, if the above would change in the future exchange versions.
    <MS did say on the call that they were not looking at fixing it, naturally this isn't a "never", as per previous statement - they can't commit 100% to the future, but they've provided me the answer - they are not currently looking at resolving/providing
    this as a migration scenario, end.>

  • Creation of a second Exchange 2013 server on a different site (with the roles of MBX and CAS) fails on prepare active directory and prepare schema.

    Hello everyone
    I have a network infrastructure  consisting of 3 sites, site A, site B, and site C. i have 2 domain controllers on every site, and the AD roles are on the primary domain controller on site A. On site A I have an Exchange 2013sp1 CU6.
    I want to create a second Exchange on Site B, with the roles of mailbox (the exchange on Site A will be first DAG member and the Exchange on Site B will be the second member of the DAG) and CAS.
    First question: Is my  thought correct about installaing on the same server mailbox and CAS server?
    Second question: how many DAG witnesses I need for the DAG? One per site, or one in general (for example located on site A)
    Third question: When I am trying to perform “Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”  I receive the error
    “ Setup encountered a problem while validating the state of Active Directory:
     The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema can't be executed.  See the Exchange setup log for more information on this error. For more information, visit:
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
    I tried  to run the PrepareSchema from  the ISO of Exchange 2013 SP1 and form the extracted content of Exchange 2013SP1 CU6 archive, but still receive the same error. Any ideas?
    Thanks in advance.

    Thank you for your answer,
    I have tried to run "Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”  from
    Exchange 2013 CU6 media, but I still receive  the error:
    The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema
    can't be executed.  See the Exchange setup log for more information on this error. For more information, visit:http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
    any ideas?

  • Inter-Org Mailbox moves from Exchange 2007 to Exchange 2013

    G'Day All,
    Is it possible to move Exchange 2007 mailboxes to Exchange 2013 in a different forest? Both environment has all the required patches and service packs.
    There is a two way trust, and I don't want to introduce Exchange 2010 CAS in the source forest if I don't need to.
    I have read the following article http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/ but it is not clear what is the required to setup in Exchange 2007.  I have read many other articles to do with Exchange 2013 mailbox moves, endpoints,
    etc, but non of them is clear of how does it work having Exchange 2007 source.
    Thanks in advance.

    Hi Atonal,
    Could you please take a look at this technet blog that has been well elaborated about your concern :
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    The blog provides step-wise assistance while you are planning to move from exchange 2007 to 2013.
    Here is another library available from technet team that includes all the terms while preparing mailboxes for cross-forest move request : http://technet.microsoft.com/en-us/library/ee633491%28v=exchg.150%29.aspx
    Alternatively, you can checkout this proficient application (http://www.exchangemigrationtool.com/) in order to avoid any interruption and proceed hassle-free migration from exchange 2007 to 2013.

  • Help With Migration From Exchange 2007 To Exchange 2013

    We have an Exchange 2007 Server with Service Pack 3 and Rollup 12 applied. 
    I installed a new Exchange 2013 Server and then immediately applied CU3.
    I am following this Technet article:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    The only deviation from the instruction I have had to do is in Part 2, section 4 “Configure offline address book (OAB)”. 
    Instead of entering:
    Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2013)"
    I had to enter:
    Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2012)"
    I believe this is due to the fact that the writer installed from an Exchange 2013 CU1 disk and I only had Exchange 2013.
    Also when I tried to run:
    Move-OfflineAddressBook -Identity "Default Offline Address Book" -Server SRV-EX2013
    I get the following error:
    Move-OfflineAddressBook : Failed to create the 'ExchangeOAB' folder on the target server 'SRV-EX2013'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform
    this operation. Error message : 'Catastrophic failure (Exception from RESULT: 0x8000FFFF (E_UNEXPECTED))'.At line:1 char:24+ Move-OfflineAddressBook <<<< 
    -Identity "Default Offline Address Book" -Server SRV-ex2013+ CategoryInfo         
    : InvalidResult: (Default Offline Address Book:OfflineAddressBookIdParameter) [Move-OfflineAddressBook], LocalizedException  
    + FullyQualifiedErrorId : 9250969C,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveOfflineAddressBook
    However when I looked at the address books in EAC I could see that “Default Offline Address Book (Ex2012)” was the default and that it contained a copy of the Global Address List. So I did nothing else about it.
    I am now at Part 3, section 7 “Move Mailboxes” and it keeps failing. 
    I am using the EAC so that I at least see the error as using the powershell brings back no results. 
    Anyway it Syncs the 18 items in the mailbox then fails with:
    Data migrated: 936.7 KB ‎(959,145 bytes)‎
    Migration rate: 0 B ‎(0 bytes)‎
    Error: MigrationPermanentException: Error: An error occurred while updating a user object after the move operation. --> Unable to generate the e-mail address. Unable to load address module ‎'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\address\SMTP\AMD64\inproxy.dll‎'
    for address type ‎'SMTP‎'. Additional message: ‎'Access is denied‎'.
    Help??
    Tony

    Hi,
    You can't configure Exchange 2013 to generate other OAB versions, and the OAB generation occurs on the Mailbox server on which the organization mailbox resides.Therefore, to move OAB generation in Exchange 2013, you must move the organization mailbox. You
    can only move the OAB generation to another Exchange 2013 mailbox database. You can’t move OAB generation to a previous version of Exchange.
    And please refer to the following articles :
    Moving OABs between Exchange versions
    If you want to upgrade from exchange 2007 to exchange 2013,I recommend you refer to the following article:
    Upgrade from Exchange 2007 to Exchange 2013
    Exchange   version
    Exchange   organization coexistence
    Exchange 2007
    Supported with the following   versions of Exchange:
    Update Rollup 10 for Exchange        2007 Service Pack 3 (SP3) on all Exchange 2007 servers in the       
    organization, including Edge Transport servers.  
    Exchange 2013 Cumulative        Update 2 (CU2) or later on all Exchange 2013 servers in the       
    organization.
    Install Exchange 2013 in an Existing Exchange 2007 Organization
    You can install a Microsoft Exchange Server 2013 server into an existing Exchange Server 2007 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2013. However, you can't perform an in-place
    upgrade from Exchange 2007 to Exchange 2013.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

    We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them. 
    With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
    For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
    In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
    I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
    I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
    So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
    In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
    Questions are, Is this the right way to migrate all the users to Exchange 2013?
    Will it affect the operation of existing Exchange 2007 server?

    Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
    For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
    However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
    2013 for standardization.
    Refer article for configuring URLs -
    http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
    - Sarvesh Goel - Enterprise Messaging Administrator

Maybe you are looking for