Exchange 2010 onprem to 2013 on prem cross forest LARGEITEMLIME issue

ok i have started migrating some of our users over, however some are failing due to large files.
I know that i can use the -LargeItemLimt switch to have the migration "SKIP" those files. (there seems to be alot of misconception  that this will actually COPY the files & the value that you define is the MB limit. this is incorrect,
& this switch just tells the migration that it is ok to skip X (the value you define) amount of messages.)
Ok so now that that is out of the way
how or where would one configure to ALLOW mailboxes to be migrated over that contain large files? Is it in the transport/send/receive connectors size limits? is it else where?
I rather temp allow large files to complete my migrations & copy those files over, rather then skipping those files, & essentially loosing them for ever.

Now here is the thing, "AllowLargeItemLimit" is still mystery (to me at least)
But you can update the size of Send and Receive Connector on 2013 and should work
Set-TransportConfig -MaxSendSize 100MB -MaxReceiveSize 200MB
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 200MB
Get-SendConnector | Set-SendConnector -MaxMessageSize 200MB
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

  • Exchange 2010 DAG Replication - too much data crossing the wire

    I’m replicating 3 Exchange databases from our production active Exchange 2010 server across the WAN to another passive Exchange 2010 server at our DR site. 
    The Exchange server at the DR site does not have any active databases, i.e. no users are hitting that server. 
    We are running Update Rollup 8 for Exchange Server 2010 SP1 on both these servers. 
    The two sites are connected via a 10Mb/s MPLS connection and all the databases are in sync and the replication is working fine. 
    I have setup a network sniffer at the primary site and see a sizable amount of data crossing the wire from the production Exchange server to the DR Exchange server. 
    When I query the production Exchange server using the Tracking Log explorer and only choose the EventID ‘RECEIVED’ that should show me the amount of data that has been committed to the database. 
    If I choose a date range that is the same exact range that I have used to capture the raw data with my sniffer the amount of data the sniffer shows crossing the wire is 10 fold compared to what the Tracking Log Explorer shows. 
    If I actually count up the data in the LOG files it is about 20% more than what is crossing the wire but that seems to be because the DAG is compressing the data. 
    If in a one hour timeframe there is 500MB of data crossing the wire to the DR Exchange server the tracking log explorer will show only 50MB. 
    I would like to know why the data crossing the wire far exceeds the amount of data that is truly being sent/received from the primary exchange server. 
    Perhaps I’m simply not getting a true view of the amount of data being committed to the exchange server using the Tracking Log Explorer. 
    Maybe there is a better way to report how much data is being committed to the exchange databases. 
    Any assistance would be appreciated…

    Two things.
    1 - you must update Exchange to SP3 and a recent RU.  Willard has already provided the links, which point back to my blog if you want to see the lifecycle map for Exchange 2010.  SP1 has been out of support since January 2013.  Time to move
    on pllease
    2 - Looking at the tracking log is not sufficient.  I would not expect that to show everything.
    I want to know what traffic you see as excessive.  What ports are you seeing used here?
    My money is on content indexing.  CI will use additional traffic over and above log repl traffic.  Expect CI traffic to be roughly the same again.  You can test this by disabling CI on the database or stopping the services on the DR server. 
    To disable the CI for the database:
    Set-MailboxDatabase DBName -indexEnabled $False
    Or stop the Exchange search services on the DR box to leave production unaffected.
    Again - you need to update Exchange.  You would be better to do that now rather than when something breaks and Microsoft support cannot fully assist you since you are not uptodate.    I'll leave discussion of the security issues resolved
    in recent Exchange RUs aside. 
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

    Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
    Tried several mailboxes. Same result.
    Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
    Ex 2013 is SP1 aka CU4.
    How to proceed???
    john11

    After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
    btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
    What did work:
    1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
    of the four mailboxes. The other 3 failed.
    2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
    3. Then on the Exchange 2013 box, use this Exchange shell command:
    New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
    This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
    Get-MoveRequest
    The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
    Thanks for the suggestions. I had to get this done and the MS Tech made that happen. 
    john11

  • Exchange 2010 Migration to 2013 Coexistence url's

    Hello,
    What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information
    I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while
    only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.
    So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my
    existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

    Read the article below from Ross Smith. There can't be better article than this:
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    If exchange 2010 and 2013 are on same site, then you need to:
    1. Remove External URL from Exchange 2010 CAS servers, retain the Internal URL
    2. Move the SSL certificates from Exchange 2010 to Exchange 2013
    3. Point the external URL to Exchange 2013 instead of Exchange 2010
    4. Of course, you would need to re-configure Autodiscover, Web Services URLs on Exchange 2013 CAS servers.
    Once this is done, for any mailbox that is hosted on Exchange 2010, Exchange 2013 would proxy the connections and deliver the content.
    - Sarvesh Goel - Enterprise Messaging Administrator

  • Latency leads to full system Failure in Exchange 2010 - Resolved in 2013?

    My work encountered a bug - and for no lack of trying - I could not find any bug submission for Ex2010 anymore.  Since Most programming relies on the foundation of the past - if replication service was implemented the same in 2013 than it could leave
    to a full system failure.
    The issue is something happened in REPLICATION service in such a fashion that it accepted a connection, and in the programming it set a variable to a LARGE NUMBER (fail closed) to replace for "Copy Queue
    length" in the ball park of 922 quadrillion.
    The service never updates this value because of its quasi-state and some timeout occurs and now the GOOD servers think their copy is ludicrously behind.  This causes the GOOD servers to attempt to fail-over - as they believe their copy from the BAD
    server has failed or perhaps another check fails...
    [6 DAG pieces on 3 servers, 4 pieces per server]
    In my scenario Server 3 holds:  
    1 part of server 2  <= Tells server 2 you're bad - don't fail over
    1 part of server 1. <= Tells server 1 you're bad - don't fail over
    2 parts its own <= "good" - though dead replication service
    As I do not know if this exploitable by simply placing a listener in place of replication service to accept and do not respond to connections - I do not know.  However, there is a "bug" or flaw in my opinion to allow 1 bad server to superceed
    two good servers based on a partial service crash.  Simply stopping replication service on Server 3 allowed Server 1 / 2 to take over with out issue - I then restarted replication service and no issue since. 
    Since i wasted an hour looking where to submit this - this forum will hopefully do - I am very much a white hat - but I am dislike the non-simple way before me to disclose said information to the creator.  I want my hour back for their non-intuitive
    process, or maybe the simply don't care about Exchange 2010.
    - Dan

    Please note "LATENCY" in my topic is not network but inter-process on a single host, and is used as saying a timeout occurs without value.

  • Upgraded to Exchange 2010 now outlook 2013 can't connect externally

    Outlook 2013 used to connect to my exchange server via our TMG before upgrading to 2010. At first the clients were changed back to NTLM all the time but I fixed that and we now see basic with SSL. Now we get repeated logon.
    I have used rpc connectivity analyser and it tells me that my (self issued) certificate doesn't chain properly - but the signing certificate is loaded on the client (by Enterprise CA policy) and looking at the mail server certificate in the certificate manger
    reports the certificate to be good and correctly shows the chain (so is this a problem in the anyalyzer or does outlook constrcut its certificate chain using a different code library than say IE?).
    Oddly Windows 8.1's mail cient works flawlessly when outlook 2013 goes into loops?
    Any suggestions?
    ICHC

    Hi ICHC,
    Just as Ed said, we should create new rule on TMG during the upgrading. 
    Found an blog for your reference:
    Upgrade from Exchange 2007 to Exchange 2010 - Part II
    https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
    Disclaimer:
    Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software of information found there. Please make sure
    that you completely understand the risk before retrieving any suggestions from the above link.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 and Outlook 2013

    please read my question and comments carefully before replying.
    We just upgraded to Outlook 2013 x64bit and exchange 2010. there is only one exchange server with all updates and fixes installed, and Outlook is up-to-date as well.
    User A sends a meeting request with tentative appointment to user B
    User B accepts the appointment and it shows on his calendar as tentative
    User A changes the appointment from tentative to out of the office or busy and sends update to user B
    User B receives the update and click on No Response Required
    User B's calendar does NOT change from tentative to out of the office or busy.......
    we tried OWA as well as tried this in cached mode and online mode and made no difference.
    you can see that communiation is real time between the two clients and exchange because as a test, I changed the words and client machine immediately updated but the free/busy/out of the office status never changes unless you change the time of the appointment.
    Please let me know
    David

    Hi David,
    It is by design.
    The Free/Busy status is a private property that can be changed but
    only with a full update. A full update is practically a new meeting invitation to the same event, replacing the old properties with the new ones. Full updates are sent when one or more of the following properties are changed:
    Start Date/Time
    End Date/Time
    Recurrence
    If you only send a update about free/busy status, it is an informational update instead of a full update. Thus, the free/busy status of the meeting is unchanged. For more information about meeting updates, we can refer to the following blog:
    http://blogs.technet.com/b/outlooking/archive/2012/06/11/understanding-meeting-updates.aspx
    If you have any feedback for TechNet Subscriber Support, contact
    [email protected]
    Best Regards,
    Winnie Liang
    TechNet Community Support

  • Decommissioning Exchange 2010 Casarray (contains 2013 Mailbox Servers?)

    I'm in the process of decommissioning exchange 2010. I went to remove the 2010 casarray and see that my 2013 mailbox servers are a part of the array? Can I still remove the array? Do I leave it?

    Hi,
    Please have a look in to the below mentioned article especially the reply from Off2work
    http://social.technet.microsoft.com/Forums/office/en-US/c10550fa-b735-48ee-ad52-a75f0176e1de/cas-array-in-exchange-2013?forum=exchangesvrdeploy
    As an additional info , as per my knowledge there is no use of cas array in exchange 2013 and at the same time exchange 2013 servers will not make use of it even though if it is an member of an casarray in exchange 2010.
    Please reply me if you have any queries .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Microsoft Exchange 2010 / Office Pro 2013 - Contact Issues

    Good Morning Everyone.
     We are running MS Exchange 2010 and have recently upgraded all our clients to MS Office 2013 Pro from Office 2007.
    We've had problems with people being able to access previously accessible share folders etc. but we've managed to resolve them. What we are having problems with are peoples personal contacts....
    Within Outlook If we click "New Email", then we click "To", choose address book and select "Contacts" (Personal contacts) we receive the error:
    "The Address list cannot be displayed. The contacts folder associated with this address list could not be opened; it may have been moved or deleted, or you do not have permissions. For information on how to remove this folder from
    the outlook address book, see Microsoft Outlook Help"
    The unusual thing is, if we go to the people tabs at the bottom (Mail, Calender, People etc") Then we can access the address book without issue?
    Any help would be appreciated, this problem is on every single client...
    Regards
    Steve Skingle

    Hi,
    Please make sure the Contact folder is enabled as an email address book in Outlook. We can check this by right-clicking on the personal contact folder, select
    Properties, then Outlook Address Book tab.
    Check if the “Show this folder as an email Address Book” option is ticked. If not, tick it and restart Outlook to check the result.
    Please let me know the result.
    Steve Fan
    TechNet Community Support

  • Microsoft Exchange 2010 and Outlook 2013

    My colleagues computer suddenly crashed yesterday and it wouldn't restart without a system restore.
    Now when we try to open up Outlook it says that you must connect to Microsoft Exchange at least once before you can usse your Outlook Data file (.ost)
    Also The PC has lost the trust relationship on the domain
    We have exchange 2010 and the servers OS is Microsoft Windows Small Business Server 2011 and the Client PC is running off of Windows 8.
    Can you please help me resolve this issue?
    kind regards
    Steve Bradshaw
    [email protected]

    It might be possible that the MAPI key (which enables Outlook to synchronize with Exchange) has been deleted due to the System crash. So, in order to establish the connection, you need to Reconnect the OST file to the original MAPI profile and then reconnect
    then MAPI profile to Exchange Server. 
    If the above method fails to resolve the issue, then the best option for you would be to take the help of any professional OST to PST Conversion Software, which will help you to Extract data from your OST file and convert it to PST file which you can import
    back to your Outlook to establish the connection with Exchange Server again.
    You can check this
    presentation for more info.
     

  • Pre-requisites for upgrading exchange server 2007 to 2013(Multiple domain, single forest scenario)

    Hi,
    We have a forest with multiple Domains in it. Each domain has exchange servers installed in it. & All are installed in Single EXCAHNGE Organization.
    One of the domain from the same respective forest has decided to upgrade their exchange server from 2007 to 2013.
    So my basic query is, do we require to upgrade the service pack on all exchange servers(which is a pre-requisite) in the organisation forest wide or can we just upgrade the service pack on the exchange server in that specific Domain where this activity is
    planned ?
    As my organization has around 30 Exchange servers running across 10 Geo locations and are running exchange 2007 Sp1 & exchange 2010 SP1, So immediately installation of service pack in all servers would require additional time and approvals. 
    Is this possible to just upgrade exchange servers of My domain with latest service pack and install exchange 2013 in domain ????

    Hi,
    You will not be able to install Exchange 2013, until all of the Exchange Servers in your ORG has been brought up to a supported level.
    In other words, your servers should be at:
    * Exchange 2010 SP3 + RU5
    * Exchange 2007 SP3 + RU13
    So No, upgrading the servers only in Y"OUR" domain is not enough.
    Martina Miskovic

  • Removed Exchange 2010 SP3 Rollup 8; some clients still having Outlook issues

    We have removed Exchange 2010 SP3 Rollup 8 and rebooted the Exchange servers; but some Outlook clients are still experiencing the issues where calendar appointments can't be saved. They get "the item cannot be saved to this folder. The folder was deleted
    or moved or you do not have permission." Then "the operation failed". Everyone has created new Outlook profiles. This fixes some computers; but not all. This is happening on Windows 7 with Office 2010 and Windows 8.1 with Office 2010.
    Does anyone have a fix?
    Thanks!
    Mary Cato

    Hi Mary,
    Is there the same issue when using OWA ?
    If OWA is ok, except recreate outlook profile, I also recommend you try moving mailboxes to another database and check if any helps.
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Auto-Mapping with Full Access Mailboxes-not working in exchange 2010 clients outlook 2013

    hello, I have exchange server 2010, the clients are running outlook 2013, I set an mailbox for automapping (full access) but when i restart client it does not appear in the client. i also did the command in the exchange shell, no errors. how can i fix this.

    no sp info shows with the 
    Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersionName                
    Edition             : Enterprise
    AdminDisplayVersion : Version 14.0 (Build 639.21)
    chart says 
    Exchange Server 2010 November 9, 200914.00.0639.021
    is that the issue need sp 1? 

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Outlook 2013/Exchange 2010 Free/Busy access issues.

    Good Day Everyone,
    I am running a Win 2008 R2 environment with Win7 users, using Exchange 2010 and Outlook 2013. Last week my users started experiencing issues with being able to view Free/Busy in the Calendar for any other user. I have checked past issues with this with patches
    KB 2837618 and KB 2837643. Neither patch is showing as installed and I have tried a nummber of the suggested fixes offered for that issue to no avail. OWA seems to be working just fine.
    Our Outlook version is: 15.0.4605.1003
    I need a fix for Outlook users and since I havve 140 users, individual fixes are a not realistic option.
    Any assistance would be greatly appreciated.

    Hi,
    Please test if Out of Office feature works well in Outlook. If Out of Office doesn't work either, it should be Autodiscover related.
    Once Autodiscover has not been configured properly, the Free/Busy information may not display correctly. If you are also seeing issues with Out of Office assistant, we may assume that you haven’t correctly setup Autodiscover, since these two symtoms are
    common when Autodiscover is not configured correctly.
    To verify that, please test Outlook Autodiscover Connectivity:
    http://technet.microsoft.com/en-us/library/bb123573.aspx
    We can also learn Configure Exchange Services for the Autodiscover Service from:
    http://technet.microsoft.com/en-us/library/bb201695.aspx
    Regards,
    Melon Chen
    TechNet Community Support

Maybe you are looking for