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

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 Certificate Question

    Hi,
    I have an Exchange 2013 and AD servers running on server 2008 R2. When you go to create an outlook account you are prompted that a certificate for mydomain.com.au has expired. When you click to view this certificate, it is referring to "www.mydomain.com.au".
    Once you accept the message it goes away, the outlook account sets up OK and the message does not show again unless you set up another account.
    The internal domain name is internal.mydomain.com.au. The Exchange server has a valid purchased SSL certificate that applies to autodiscover.mydomain.com.au, mail.mydomain.com.au, mydomain.com.au and the exchange servers internal name until 2015. The "www."
    cert and website for this domain is separate to the internal servers and mail. The cert for the website has indeed expired but my question is even though it is the same domain why would this internal exchange server be querying the www. certificate when creating
    an outlook account.
    Bit of a tricky question hope I have explained it OK.
    Thanks Robbie

    Hi Robbie,
    Your certificate expired issue may occur when using the Autodiscover service and Outlook Anywhere service. Please follow these steps to have a check:
    1. verify the FQDN that the client users to access the resource from Outlook:
    a. Start Microsoft Outlook.
    b. Click File > Account Settings, click Account Settings.
    c. Click the E-mail tab, click the Exchange account, and then click Change.
    d. Click More Settings, and then click the Connection tab.
    e. “Connect to Microsoft Exchange using HTTP” should be checked, then click Exchange Proxy Settings.
    f. Note the FQDN that is listed in the Only connect to proxy servers that have this principal name in their certificate box. For example, mail.contoso.com.
    2. Run the following command in Exchange to determine the value for the CertPrincipalName attribute for EXPR name:
    Get-OutlookProvider
    For example, the command returns the following: 
    msstd:server1.contoso.com
    3. Modify the CertPrincipalName attribute to match the FQDN that Outlook uses to access the resource:
    Set-OutlookProvider EXPR -CertPrincipalName:"msstd:<FQDN the certificate is issued to>"
    For the Autodiscover service checking, please open outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication
    - click Test to check your Autodiscover service. If possible, please post the Results tab here for more troubleshooting.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Migration Questions

    Exchange 2013 SP1 to a new server. I just realized that I have been asking migration questions on the "general" forum. Here's the deal:
    We just want to move to a newer server and reuse the "old" server as a DAG member. We have a production exchange 2013 SP1 server and I found that the DB is not on a RAID'ed drive. So, we purchased a server. I installed 2012 R2 and all windows updates.
    Then installed exchange 2013 SP1. Then got our AS/AV software installed. When I boot the new server up and login to ECP, it sees all the exchange users, DB and info. So, I followed:
    http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
    to migrate users and current email to the new DB. However, when users logged in their current email was not there. I also tried to use the ECP migration option and this resulted in the same, users old email was not in their inbox. So I had to perform that
    same process on the old DB to get users old email back. I then tried to use the migration option in the ECP->same issue. So as of now, we are on the old DB and things are working fine.
    According to:
    http://technet.microsoft.com/en-us/library/aa997006(v=exchg.65).aspx
    When moving from server to server, the DB filename must be the same. The non-production server does not have the same DB filename. Could this be the problem? Could someone point me to documentation on migrating from server to server

    So I ran Get-Mailbox -Database “Source Database Name” " -ResultSize Unlimited | New-MoveRequest -TargetDatabase “Target Database Name” and moved all the user mailboxes. Then moved the system mailboxes, public folders and
    OAB. Adjusted send connector to reflect new server. Log in as a user, all email is there. Great! Dismount the old DB. Wait a few minutes and user email is still there. Woohoo! Shut down the old exchange server and a few minutes later, all email is gone. Boo!
    Boot the old server back up and mount the old DB, all email is back in user inbox. How do I use only the new DB in exchange 2013?
    So I just dismounted the old DB and all email stays in users inbox?! So it must be something with the old server that did not get moved over but for the life of me I cant figure out what

  • IBM Domino to Exchange 2013 Migration question

    I've been tasked with looking into migrating our company of 5500+ Domino users to Exchange 2013.  Currently, my Domino servers spread across the county and not all in one location.  Is there a document/guide that can help me get an understanding
    on what type of environment I can take my hub/spoke Domino environment to in Exchange?  Any guidance would be appreciated. Thanks!

    hi Hoss,
    I have done couple of Migrations from Domino to Exchange Migrations and pretty familiar with this. For this to happen, you have to use a third party tool like Quest or Binary Tree.
    Since you said, 5500+ users, I would recommend you using one of the quest or binary tree tools to assist you with this migration. The key to the migration is the design and planning phase.
    I am familiar with Quest tools and will give you as much as i know but I am sure every other tool out there is pretty similar in terms of functionality.
    you have to purchase Quest licenses and for quest to be installed on your server, you have to go through Quest Professional services or a Quest approved vendor. You cannot install Quest on your own - this is a small drawback that I personally think.
    While your Quest servers are being setup, you have to plan out your Exchange server design and for a 6000 user mailbox, you wont have a big of a deal. I need the hardware information that you have purchased for the Exchange servers? are you going
    to go physical or virtual? I need to know the user message profile in your existing domino environment (how many emails sent/recived /size per day/per mailbox)? I also need your inputs on how many servers are you planning with Exchange 2013 in total (all roles),
    Do you need single item recovery? Do you have any storage contrains? and a 100+ questions. If you get me the answers for what I asked, I am willing to help you with the design fo Exchange 2013.
    Re: Domino:
    What version of domino are you running? What is your max mail file size? how many mailboxes (person documents) how many mail-in databases? how is your user account provisioning currently designed? and so on. user account provisioning could be a challenge
    because you have to introduce a 3rd party app like FIM or CA's User Management apps to work between your Domino and Exchange (during the time of coexistence) and there is a lot to it.
    All the best!
    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. Regards, Siva

  • 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

  • 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."

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • Exchange 2013 & Exchange 2007 Coexsistance

    We are in the process of migration from Exchange 2007 & Exchange 2013. Question is after decommision all last Exchange 2007 servers, if i want to restore mailbox data from 2007 database will i be able to install new Exchange 2007 server and perform restore.
    Question: Is it possible to install Exchange 2003 or 2007 in a pure Exchange 2010 organization?
    Answer: If this is an Exchange 2010 greenfield environment (an Exchange organization that consists only of Exchange 2010 servers and never had previous versions of Exchange deployed), the answer is no.If
    you have transitioned from Exchange 2007 to Exchange 2010 and the last Exchange 2007 server has already been decommissioned, the answer is again no. You will not be able to install Exchange 2007 at a later time in this organization because
    it’s now considered a pure Exchange 2010 organization.
    Please suggest, what all possible conditions I CANNOT INSTALL NEW EXCHANGE 2007 in my organization later.

    Hello,
    You're right. I'm afraid that there is no way to install pervious exchange version in exchange 2010/2013 organization.
    You can try Ed's suggestion.
    I don't know why you want to restore mailbox data from 2007 database.
    Cara Chen
    TechNet Community Support

  • Move Exchange 2013 installation to new virtual machine

    Currently have: 1 virtual server - Server 2012 (DC, Global Catalog), Exchange 2013 CU1 installation (yes I know- dont install Exchange on DC etc etc ... ). Server2012/Exchange2013 is installed on one VMDK, EDB and logs are saved on another VMDK.
    Want to do: Create second virtual machine and install Server 2012 (different name), add it as a member to the same domain (also in the same network), install Exchange 2013, move all mailboxes to the new server, uninstall the old Exchange 2013. 
    Question is- is it possible to somehow unmount the existing database (I am only using one database for mailboxes and public folders) and mount it to the new server or do I have to create a new database on the new server and move the mailboxes there? I've
    heard that the Exchange EDB databases were supposed to be portable between same versions of Exchange. 
    Any advice is appreciated. 

    Hi,
    Agree with Andy, to avoid down time, we can depend on database portability.
    And here are the steps you can refer to:
    1. Install new Exchange server on the member server.
    2. Move Mailbox Database using Database Portability:
    http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
    3. Move the public folders (if any), re-home the offline address book, and move your SMTP connectors
    http://support.microsoft.com/kb/822931
    4. Remove the old Exchange server.
    Thanks,
    Angela Shi
    TechNet Community Support
    Thanks for the reply.
    I'm a bit confused on the instructions from
    http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx- does step 4 instruct me to overwrite the newly created database (on the new server) with the old database and then mount it on the new server? Also, as the public folders are now in
    a mailbox on the same database- aren't they moved with the database without extra hassle?
    Also the link you gave me in Step 3 in your post refers to Exchange 2003.
    Thanks in advance.

  • 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.>

  • Exchange 2013 eseutil /d question

    I have a couple questions about offline DB defragging using eseutil /d.
    I am about to perform a migration from Exchange 2007 to Exchange 2013 hybrid on-prem/cloud where the mailboxes will be hosted on premises and the archive mailbox will be hosted in the cloud. As part of this migration, we will be migrating the mailboxes from
    2007 to a "temporary" database, then importing PST's (currently housed in a third party archive solution) into the archive mailbox. THEN migrating that archive mailbox to Office365 off-premises. Then running managedfolderassistant with the desired
    retention tags to "clean up" the mailbox. Then eventually moving the mailbox in to another database, where it will ultimately reside
    Long story short, the "temporary" database will need to grow and shrink beyond the point where normal online defrag will suffice.I will run eseutil /d on the temp database once all users have been moved off of it. I just need to verify that when
    running the offline degrag, that it will clean out ALL contents of he database, all deleted items folder, dumpster, deleted mailboxes, etc. I will have litigationholdenabled=true on all these mailboxes. Should I just delete the database and recreate it, rather
    than deal with eseutil /d. Let me know what you think of this proposed process...

    Hi Troy12n,
    Great information on eseutil /d from Gulab Prasad.
    Found some good blogs about Offline Defrag, hope it can help us understand it in details:
    Offline Defrag And DAG Databases, Oh My!
    http://blogs.technet.com/b/rmilne/archive/2013/08/23/offline-defrag-and-dag-databases_2c00_-oh-my_2100_.aspx
    How To Check Database White Space In Exchange
    http://blogs.technet.com/b/rmilne/archive/2013/08/20/how-to-check-database-white-space-in-exchange.aspx
    I also found a blog on "How to migrate to Office365 from Exchange 2007 step-by-step." for your reference:
    **Please make a full back up first**
    Step-By-Step: Migrating from Exchange 2007 to Office 365
    http://blogs.technet.com/b/canitpro/archive/2013/11/20/step-by-step-migrating-from-exchange-2007-to-office-365.aspx
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Migration questions from Exchange 2007 to Exchange 2013

    Dear Forum Members,
    I'd ask just two short questions, regarding a migration from Small Business Server 2008 (Exchange 2007) to 2013. We installed the two Exchange 2013 servers, configured a DAG and updated every single URL (OWA, ECP, AnyWhere, Autodiscover etc.) to be a mail.domain.com
    record (DNS round robin, since no HW load balancer :( )
    Thankfully, the mail flow between the Internet and the other Exchange 2007 users are still working. Now for those users I've already migrated, if I check outlook connections there are several connections for GUID based servers via the DNS Round Robin
    name proxy (the AnyWhere address). But I saw that there are still just one connection (type: Exchange Public Folders) to the old 2007 server. Is it okay? I'm a bit afraid to uninstall it because of this.
    And the other thing: Based on what I wrote, do you think I've done it good? Or could I miss any important things? You are much experienced than me in these migrations so I hope that I can get some confirmation/advice here :(
    ps: Is it good if I set NTLM authentication for Outlook AnyWhere?
    Thank you really much for your help,
    Best Regards,
    Chris

    Hi Chris,
    Agree with Hinte, the user will still connect to the exchange 2007 server if there is a public folder database in the old server.
    If the old public folders are no longer in use, you can delete the public folder database and create a new one in the exchange 2013 server, you can also consider migrating public folders to Exchange 2013 .
    The following articles for your reference:
    Use serial migration to migrate public folders to Exchange 2013 from previous versions
    Set up public folders in a new organization
    Step-by-Step Exchange 2007 to 2013 Migration
    >>Is it good if I set NTLM authentication for Outlook AnyWhere?
    The Outlook Anywhere authentication method you choose will depend on a few factors in your environment,
    I recommend you refer to the following thread to understand how to choose:
    https://social.technet.microsoft.com/Forums/exchange/en-US/75f8d6c4-70f4-49e5-ac32-a49dd91b5520/outlook-anywhere-ntlm-for-internal-users-and-basic-for-external-users?forum=exchangesvrclients
    Exchange 2013: Configuring Outlook anywhere
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

Maybe you are looking for