Mailbox sizes increase dramatically after migration to exchange 2013

After I migrate mailboxes from exchange 2010 mailbox to 2013, the size increases.
For example -
On exchange 2010 I run get-mailboxstatistics: TotalItemSize : 6.706 GB
On exchange 2013: TotalItemSize : 9.374 GB
Anand_N

Hi Anand,
Please note that the actual space used by the mailbox database will not increase. This only refers to the attribution of space used by each individual mailbox. Actually, this happens due to the inclusion of all item properties into quota calculations, providing
a more accurate computation of space consumed by items within their mailbox. However, you can adjust mailbox size and increase mailbox quota by 40% before moving.
You can follow below cmdlet in order to increase "ProhibitSendQuota" value for all users that are not using the database quota defaults:
Get-Mailbox -ResultSize Unlimited -Filter {UseDatabaseQuotaDefaults -eq $False} |
Where {$_.ProhibitSendQuota -ne "unlimited"} | ForEach {Set-Mailbox $_ -ProhibitSendQuota "$($($_.ProhibitSendQuota).Value.ToMB() * 1.4)MB" -WhatIf}
You can have a look on this link to prevent the cause :
Mailbox migration from 2010 to 2013
Hope, this will be helpful for you.

Similar Messages

  • After migration to Exchange 2013 the old outlook clients do not automatically reconfigure

    After migration to Exchange 2013 the old outlook clients do not automatically reconfigure
    we use outlook 2013

    Hi ,
    I hope you would be having exchange 2013 coexistence environment with exchange 2010 or 2007.
    Autodiscover is the feature which will make the outlook profiles to configure automatically.So please make sure the following things are in place.
    1.Autodiscover record on the internal dns need to be configured and it has to be resolved properly to the cas servers or else to the LB if you have.
    2.Please check the autodiscover internal url.
    get-clientaccessserver -identity "server name" | fl *internaluri*
    3.Make sure the name used for the autodisocver and internal outlook anywhere are available on the SAN certificate installed in exchange.Same time we need to enable the installed SAN certificate for the exchange services like iis,pop,imap,smtp.
    4.You need to have the autodicover name and internal outlook anywhere name on the internet explorer proxy exceptions when you have proxy servers available on your network for internet access.
    Note : moreover we need an additional information's from your side about your environment.
    Thanks & Regards S.Nithyanandham

  • Users cannot access calenders from outlook after migration to exchange 2013

    I have a strange situation after upgrading to exchange 2013 some users are reporting that they cannot open or create calender appointments for calenders they used to be able to manage. we currently are using outlook 2010. also when the users access the calenders
    with the webmail they are reporting that they can access the calenders and are able to do all the things they need to do.
    i have tried reinstalling office and adding their exchange accounts but this does not help.
    another stange thing is that to be sure i had setup the correct access policy i have reset all the security entries on all the calendars with the help of powershell. this seemed to have helped but after a couple of hours some users started reporting that they
    could not access calendar items again!

    Hi,
    Is there any error description when the problematic users cannot open or create calendar items? Since the issue only happens to some users instead of all users and all calendars can work well in OWA, I think the calendar in the mailbox
    should be configured properly.
    Please configure the problematic user’s Outlook account in a clean computer with new installed Outlook to check whether the issue persists.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

    Hi,
    we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
    With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
    As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
    there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
    On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
    We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
    Thanks, Paula

    Hi,
    Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
     Is it right?
    You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
     If possible, please switch this Outlook client from cached mode to online mode to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • File size increases dramatically after digital signature with Acrobat X

    I signed a PDF file using Acrobat X.
    File size of unsigned document: 200 k
    File size of signed document: 3200 k (more than ten times bigger)
    Any idea?
    BR
    Harald

    Finally I found the solution.
    The file size increase is a result of the embedded information used for long-term signature validation.
    If you do not need this feature, you can turn it off:
    Preferences > Security > Advanced Preferences > Creation tab
    disable "Include Signature’s Revocation"
    Help page: http://help.adobe.com/en_US/acrobat/X/pro/using/WS934c23d7cc8877da1172e0811fde233c98-8000. html
    BR
    Harald

  • ActiveSync Failures After Migration to Exchange 2013

    Hi all, 
    I am having an issue with ActiveSync a single mailbox that has been migrated from Exchange 2007 to 2013. After the mailbox was migrated to 2013 it continued to sync as normal for a week or so. After removing the exchange 2007 server (uninstalled exchange) from
    the topology, the user could no longer sync. 
    This is not the inherit permissions in AD issue. I had a user with that issue but this one is different.
    It appears to have something to do with the app pools. The following article provides a script to recycle the app pools, when I run this, the issue is resolved but only temporarily. Within 20 mins or so, the issue returns for the user. Running the script
    again works but again, it is only temporary.  
    http://www.expta.com/2014/04/fix-for-exchange-activesync-failures.html
    Can anyone tell me why this fix only works momentarily? Is there any way (besides running the script constantly) to make the fix stick? 
    Any help is much appreciated.
    Thanks!

    Instead of restarting App pool, I would suggest looking at the IIS logs on the Client Access Server and check for the entries for this user.
    If you notice either throttling/something wrong with this user's connection, troubleshoot in that direction.
    also look at Event logs to see if there are any problems with App pools creating Watson dumps. (event ID 4999, 1003 etc)

  • After Migrating To Exchange 2013 All Outlook 2010 Users Constantly Prompted For Password (BUT OUTLOOK WORKS).

    I have two servers.  One is Exchange 2010 and the other is Exchange 2013.
    Three of our users had mailboxes on Exchange 2013 for the last few weeks with no problems.  They used Outlook 2013 and Outlook 2010.  After moving the rest of our ~25 users to Exchange 2013 the users with Outlook 2010 began to be prompted for their
    password constantly.
    They try entering it and it immediately reappears.  
    The odd thing is it shows connected and they are able to send and receive emails correctly.  
    I've tested our exchange connectivity using www.testexchangeconnectivity.com and all is well there.
    I'm not really sure what's going on.
    Any help is appreciated.  
    Luke
    Thanks, Luke Pickard

    This can appear if Outlook clients are trying to connect to OAB virtual directory, and don't succeed for some reason. Mailbox and mailflow will work, but password prompt will appear when Outlook tries to contact OAB. Try to investigate in that direction.
    Also, perform Outlook Configuration test (right click Outlook icon in task bar while holding CTRL and select Test email autoconfiguration.
    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. Thank you! Damir

  • Can only access emails through OWA after migration from exchange 2007 to 2013

    can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
    needed RCA ... plz help..

    Hi,
    From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
    In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2007 migrate to Exchange 2013

    Dear MS Support,
    I did migrate Exchange 2007 to Exchange 2013
    The install complete, the exchange 2007 and 2013 can work together successful
    DAG has created and work fine
    Below is capture on exchange group after migrate
    The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
    The cerificate enroll with
    Alternative Names: mail.biendongpoc.vn
    The autodiscover on exchange 2007:
    [PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
    Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
    Identity      AutoDiscoverServiceInternalUri
    BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
    I have created new certificate for Two exchange 2013
    The certificate enroll with
    Alternative Names: cas.biendongpoc.vn
    I have create cname cas point to dag  on DNS server
    I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
    I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
    connected to Exchange 2013 and working perfectly
    Our problem, the account exchange 2007 work not stable ,
    sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
    If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
    It is not stable for current exchange 2007
    Anyone who can help me ?
    Thanks

    Hi
    huynhtrongnhatminh,
    I suggest you please go through this article.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Please check this for step by step guide.
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Please point your autodiscover and commonname to Exchange2013 CAS
    Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
    You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally. 
    Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
    Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
    No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
    Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
    http://exchange.sembee.mobi/network/split-dns.asp
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

    Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
    I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
    Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
    Error look like - cannot find exchange server.
    I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
    Someone have the same problem with migrated mailbox? How to solve it?
    Truly, Valery Tyurin

    You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
    Moreover, you can try this utility (
    http://www.exchangemigrationtool.com/ ) to accomplish this task.

  • Migrating AD Exchange 2013 Objects to a new AD Domain

    I have a client 'new company' (NC) who is splitting from the 'parent company' (PC).  They are using a 3rd party tool to conduct the AD migration/split.
     The PC AD domain is on Windows 2012 Servers and has trust relationship with the NC AD domain also running on windows 2012 server.  The users and computers have been successfully migrated/stubbed to the NC domain, however, the Exchange 2013 objects
    are not migrating over to the NC AD domain using the 3rd party AD migration tool.   
    Question, does any one have suggestions on how to migrate the exchange 2013 objects from the PC AD to the NC AD ?
    What techniques can be used ?
    Thanks in advance 
    RK

    What 3rd party tool are you using and have you contacted their support already? You can use the native tools to migrate mailboxes (I do all the time) but I wouldn't try and mix the native tools and a 3rd party tool on the same migration unless I was sure
    what the end result would be.

  • Cutover Migration to Exchange 2013 On-premises

    I have two clients who will be merging their on-prem Exchange 
    organizations. Different forests.  I've done many cutover migrations to
    Office 365 for other clients so I'm familiar with the process.  My 
    question is:  Is it possible to do an O365-style cutover migration (create migration endpoint, cutover batch, etc.) from
    an on-prem Exchange 2010 server to an on-prem Exchange 2013 server using
    the same steps?
    Thanks in advance for any input. 
    Steve

    Hi,
    Based on my knowledge, the Cutover Migration is used for migration to Exchange online. There is no related document about
    Cutover Migration from Exchange 2010 to Exchange 2013.
    To perform Exchange 2010 corss-forest migration to Exchange 2013, you need to use Active Directory Migration Tool (ADMT) migrate user accounts.
    Here is a related blog which may help you. (Even though this article is for Exchange 2010 corss-forest migration, it's also applies to cross-forest migration from Exchange 2010 to Exchange 2013.)
    http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Mailbox size increased after removing attachments

    Doing a little clean-up on my mail, I noticed my sent mailbox was 1.23 gigs. So, I went in saved several hundred attachments and then tried to remove attachments. It would only let me remove attachments about 5 messages at a time, so I moved over 300 messages that all had attachments to a new folder. After moving them I was able to remove all the attachments at one time.
    But after moving and removing attachments the size of my sent mailbox did not decrease it actually increased by over 400 megs to 1.7 gigs. And the new folder was also very large, at almost 700 megs (even after removing attachments).
    Any ideas how/why this happens? and what can I do to reduce the size of that mailbox?
    I have had the overflow issue before and have been trying to keep and eye on the mailbox sizes and keep them under 1 gig, but this one got by me. My only complaint is mail does not tell you the size of a mailbox in the application, if I was able to check the mailbox size right from the app it would be an easier thing to keep an eye on an everyday basis.
    Any help would be great.. thanks!
    G4 400   Mac OS X (10.3.9)  

    For each mailbox, Mail 1.x stores messages sequentially in an mbox file within the *.mbox package associated with the mailbox -- you can see the files contained in an *.mbox package by ctrl-cliking on it in the Finder and choosing Show Package Contents from the contextual menu.
    When a message is removed from a mailbox in Mail 1.x, the actual message may be completely erased from the mbox file, or it may remain there just marked for deletion in one of the other supporting files within the *.mbox package. In order to reduce the mailbox size when a message is deleted from the middle, the entire mailbox would have to be rewritten to disk every time, which is clearly not practical.
    When attachments are removed from a message, the attachments aren’t actually removed from anywhere. What really happens is that Mail creates a new message without the attachments and deletes the original message... and now you know what it really is that actually happens when a message buried in the middle of the mailbox is deleted...
    My only complaint is mail does not tell you the size of a
    mailbox in the application
    Mail 1.3 sure does. The size of the selected mailbox is displayed in the status bar (View > Show Status Bar). Interestingly enough, that feature is no longer available in Mail 2.x.

  • Free/Busy not working after mailbox migration to Exchange 2013

    I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013
    It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated.  If we remove the Outlook profile and recreate it, all is good.  Problem is that this is happening to more and more people.  Everyone
    is on Outlook 2010
    Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:
     Autodiscover: Outlook Provider Failure
     Exchange Web Services          Failure
     Availability Service           Skipped
     Offline Address Book           Failure
    The same if I run that command against the Exchange 2007 server.
    What am I doing wrong?

    I should have mentioned that.  Yes, OWA works perfectly for the affected users.  Just as deleting their Outlook profile and recreating a new one does.
    Results of Get-WebServicesVirtualDirectory:
    Identity    : Exch2007Srvr\EWS (Default Web Site)
    InternalUrl : https://legacy.company.com/EWS/Exchange.asmx
    ExternalUrl : https://legacy.company.com/EWS/Exchange.asmx
    Identity    : Exch2013Srvr\EWS (Default Web Site)
    InternalUrl : https://mail.company.com/ews/exchange.asmx
    ExternalUrl : https://mail.company.com/ews/exchange.asmx
    The URL you reference above is actually the site I used to perform migration.
    What's interesting (at least to me) is that on my machine I did not have any issues with seeing calendars. The Test E-mail AutoConfiguration (without Guessmart), I get prompted for my password over and over; however, after clicking on cancel I
    get:
    Attempting URL
    https://mail.company.com/autodiscover/autodisconver.xml found through SCP
    Autodiscover to
    https://mail.company.com/autodiscover/autodisconver.xml starting
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    Autodiscover to 
    https://mail.company.com/autodiscover/autodisconver.xml Failed (0x80040413)
    Attempting URL 
    https://autodiscover.company.com/autodiscover/autodisconver.xml found through SCP
    Autodiscover to
    https://autodiscover.company.com/autodiscover/autodisconver.xml starting
    GetLastError=0; httpStatus=200.
    Autodiscover to
    https://autodiscover.company.com/autodiscover/autodisconver.xml Failed (0x800C8203)
    Autodiscover to https://company.local/autodiscover/autodiscover.xml starting
    GetLastError=12029; httpStatus=0
    Autodiscover to https://company.local/autodiscover/autodisconver.xml Failed (0x80004005)
    Autodiscover to
    https://autodiscover.company.local/autodiscover/autodisconver.xml starting
    GetLastError=0; httpStatus=0
    GetLastError=0; httpStatus=200
    Autodiscover to
    https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C8203)
    Local autodiscover for company.local starting
    Local autodiscover for company.local Failed (0x8004010F)
    Redirect check to
    https://autodiscover.company.local/autodiscover/autodisconver.xml starting
    Redirect check to
    https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C820D)
    Srv Record lookup for hydraforce.ads starting
    Srv Record lookup for hydraforce.ads Failed(0x8004010F)
    However, when I did this on a system that cannot see any calendars, it all works perfectly.
    Browsing to
    https://autodiscover.hydraforce.com/autodiscover/autodiscover.xml does result in Error Code 600

  • Litigation Hold Mailbox Migration to Exchange 2013

    Hello,
    We have in our organization few mailboxes (Exchange 2010) which are enabled for Litigation Hold for a purpose. Now since we are moving to Exchange 2013, need to understand what happens to those mailboxes after migration.
    Neilesh

    Hi Neilesh,
    Below cmdlet would give you the actual mailbox size including the deleted items(changed hold items etc)
    Get-MailboxFolderStatistics -Identity contoso\chris | Select Name,FolderSize,ItemsinFolder
    Recoverable Items 127.5 KB (130,553 bytes) 54
    Deletions 0 B (0 bytes) 0
    Purges 0 B (0 bytes) 0
    Versions 0 B (0 bytes) 0
    Reference:
    Reporting Mailbox Folder Sizes with PowerShell
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Maybe you are looking for