Exchange 2010 On-Premises Mailbox Move

We have created another database within a DAG and moved the users from an existing database to the new database. Mailflow is working correctly but we have one issue. The OWA no longer works for these users. If the users tries to logon or if I try to access
their mailbox using OWA the response is "Your mailbox appears to be unavailable. try to access it again in 10 seconds. If you see this error again, contact your helpdesk". Inheritable permissions are set on the user account in AD.
Is there some permissions I need to add to the new database or IIS?
Exchange 2010 SP2
HossFly, Exchange Administrator

Hi hossFly,
Thank you for your question.
We could run the following command:
Clean-MailboxDatabase  <databasename>
For example:This example cleans the mailbox database MBD01.
Clean-MailboxDatabase MBD01
If the issue persist, we could run the following command:
New-MailboxRepairRequest -Database "<Mailbxname>" –CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview
Then we could restarted MS Exchange Mailbox Assistant to check if the issue persist.
If there are any questions regarding this issue, please be free to let me know. 
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Similar Messages

  • Exchange 2010 outlook and mailbox move to another server

    does a user need to create a new profile when mailbox has been moved to a different server?
    TM

    Right, they don't need to recreate their outlook profile.
    Cheers,
    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.

  • Exchange online and Exchange 2010 on-premise calendar availability

    I am running a hybrid exchange 2010 on-premise and online exchange environment.  The online exchange users cannot see calendar availability of anybody on premise.  The on-premise users can see the online exchange availability.  I can see the
    calendar if the calendar is shared, but trying to setup a meeting or calendar appointment still shows the unavailable through all days.
    All of the users are using office 365 for outlook on premise and exchange online.  If it is only working one way, could it be an autodiscover issue where it is not configured correctly on our on-premise exchange 2010 or online exchange?  Which
    side would be causing the issue?

    I have done a little more research and ran the following in powershell:
    [PS] C:\Windows\system32>Get-FederationInformation -domainname weiman.com
    RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
    TargetApplicationUri  : outlook.com
    DomainNames           : {Weiman.onmicrosoft.com, weiman.com, Weiman.mail.onmicrosoft.com}
    TargetAutodiscoverEpr : https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
    TokenIssuerUris       : {urn:federation:MicrosoftOnline}
    IsValid               : True
    [PS] C:\Windows\system32>Get-OrganizationRelationship | FL
    RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
    DomainNames           : {herbertstanley.com, weiman.com, Weiman.mail.onmicrosoft.com}
    FreeBusyAccessEnabled : True
    FreeBusyAccessLevel   : LimitedDetails
    FreeBusyAccessScope   :
    MailboxMoveEnabled    : True
    DeliveryReportEnabled : True
    MailTipsAccessEnabled : True
    MailTipsAccessLevel   : All
    MailTipsAccessScope   :
    TargetApplicationUri  : outlook.com
    TargetSharingEpr      :
    TargetOwaURL          : http://outlook.com/owa/herbertstanley.com
    TargetAutodiscoverEpr : https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
    OrganizationContact   :
    Enabled               : True
    ArchiveAccessEnabled  : True
    AdminDisplayName      :
    ExchangeVersion       : 0.10 (14.0.100.0)
    Name                  : On Premises to Exchange Online Organization Relationship
    DistinguishedName     : CN=On Premises to Exchange Online Organization Relationship,CN=Federation,CN=WEIMAN,CN=Microsof
                            t Exchange,CN=Services,CN=Configuration,DC=herbertstanley,DC=com
    Identity              : On Premises to Exchange Online Organization Relationship
    Guid                  : 26b4ec5d-fe93-473e-b451-1f9aa2e94ebb
    ObjectCategory        : herbertstanley.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
    ObjectClass           : {top, msExchFedSharingRelationship}
    WhenChanged           : 1/13/2014 1:25:54 PM
    WhenCreated           : 12/17/2013 1:04:32 PM
    WhenChangedUTC        : 1/13/2014 7:25:54 PM
    WhenCreatedUTC        : 12/17/2013 7:04:32 PM
    OrganizationId        :
    OriginatingServer     : gemini.herbertstanley.com
    IsValid               : True
    I am not sure why we have that value for the OriginatingServer.  That server is a backup domain controller, not the server that houses the on-premise exchange.
    I then ran the set-OrganizationRelationship and get the below error.
    [PS] C:\Windows\system32>Set-OrganizationRelationship -Identity weiman.mail.onmicrosoft.com -targetapplicationUri outloo
    k.com -TargetAutodiscoverEpr https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
    The operation couldn't be performed because object 'weiman.mail.onmicrosoft.com' couldn't be found on 'gemini.herbertst
    anley.com'.
        + CategoryInfo          : NotSpecified: (0:Int32) [Set-OrganizationRelationship], ManagementObjectNotFoundExceptio
       n
        + FullyQualifiedErrorId : F2215CB2,Microsoft.Exchange.Management.SystemConfigurationTasks.SetOrganizationRelations
       hip
    How do I change the originating server to be my exchange server?

  • 1x Exchange 2010 on-premises hosts 2 domains/companies, they've now split and will be hosted at separate locations.. autocomplete & NDR's

    Per the subject. CompanyA and CompanyB shared the same Exchange 2010 Server. They have close ties but have outgrown the shared offices so CompanyB has moved 2 miles down the road. There is no link between the offices.
    CompanyA is keeping the original server, CompanyB has moved to new premises with their own Forest/Domain/DC and a shiny new Exchange 2010 Server.
    I'll be using new-mailboxexportrequest / new-mailboximportrequest to move all e-mail data to CompanyB and then creating x500 proxy addresses so that at least at CompanyB they can all reply to CompanyB mails. That helps CompanyB continue to be able to respond
    to old CompanyB e-mails/meeting requests.
    But CompanyA and CompanyB will still want to e-mail each other regularly, I haven't done the move yet but past experience suggests that due to auto-completes (and how Outlook/Exchange functions internally) they're likely to experience a lot of bounce-backs
    e-mailing each other, especially responding to pre-split mail.
    I'm likely to use NK2Edit and a login script to automatically remove the other company from the autocompletes so new e-mails should go through okay but are there any other solutions for CompanyA responding to old CompanyB mails and meeting requests
    (and vica versa?) Special Send Connector with the old X400 addresses? Anything?
    Any helps really appreciated.

    Hi,
    Agree with Jon.Knight. If there is no direct route between company A and company B, they will have to route over the internet.
    When you move company B' users to a new forest, the email address will not exist on both sides at the same time then a shared SMTP namespace would work. You can create an SMTP connector on both sides with the local domain defined in the address space.
    With this the Exchange server checks locally for the email address and if it does not find it defined locally, it will route the email to the other Exchange server which will in turn deliver it to a local mailbox.  Make sure both sides have this shared
    SMTP address space defined in the accepted domains. The address space needs to be listed as an Internal Relay.
    Here is a thread for your reference.
    Cross Forest Migration mail flow between Exchange 2007 and 2010
    http://social.technet.microsoft.com/Forums/en-US/2592bc14-87aa-4bad-a3b2-edbaab547f3c/cross-forest-migration-mail-flow-between-exchange-2007-and-2010
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange 2010 /hosting shared mailbox issue

    Hello everyone.
    I had an issue come up in our Exchange 2010 with /hosting switch deployment (currently at SP2).
    We have several organizations and shared mailboxes configured and working on some. We add Full access permissions via Powershell + Send as rights and it auto configures and works just fine.
    Last week though, one of several people that uses a specific shared mailbox started getting the error: "Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the
    Microsoft Exchange Server computer is down for maintenance." (Error ID: 300)
    The other users can still work just fine. Configuring the account in another PC shows the same problem (so it's not the local profile).
    Creating 2 users, giving nr1 full access to nr2 generates the same error.
    In another org though, i was able to give full access to another acount to an existing user and it worked (although the auto-mapping didn't, had to add it manually)
    I'm out of ideias. Any sugestions?
    EDIT: Did a couple more tests on another Org. On this one everything works with the shared folder access with old and new accounts but strangely the auto-mapping doesn't.
    It seems that this is an issue with the mapping.
     

    Hi,
    From your description, I recommend you manually update or create your Outlook profile with RPC encryption and check the result. Here is the steps on Outlook 2007 for your reference:
    1. Select your profile, and then click Properties, click E-mail Accounts.
    2. Select the Microsoft Exchange Server account, and then click Change.
    3. In the dialog box that contains your mailbox server and user name, click More Settings.
    4. In the Microsoft Exchange Server dialog box, click the Security tab.
    5. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK.
    6. Click Next, and then click Finish.
    For more information, here is a kb for your reference.
    Connection issues and error messages in Outlook for a mailbox on a server that is running Exchange Server 2010
    http://support.microsoft.com/kb/2735060
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

    Hi,
    I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
    We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
    All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
    url) also redirects me to https://legacy.domain.com/owa just fine.
    HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
    Anyone any tips where to search?
    Many thanks in advance.
    Best regards and many thanks in advance, Eric Vegter

    This seems to be an outstanding issue.
    We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
    migration of our mailboxes from the 2007 DB to the 2013 DB.
    In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
    Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
    "Use the following link to open this mailbox with optimal performance:
    http://mail.domainname.com/"
    After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
    -Lorne

  • Remote 2010 - 2010 Cross-forest mailbox move timeout

    I'm having a problem moving large mailboxes cross-forest. Smaller mailboxes with fewer items move successfully. I've tried the suggestions in this article
    http://technet.microsoft.com/en-us/library/dd638094.aspx about increasing DataImportTimeout in the EWS web.config and restarting IIS on both sides, just in case.
    I also found a suspicious timeout in MsexchangeMailboxReplication.exe.config that was 00:00:50 (exactly the timeout it's complaining about in the error below), but changing it to 10 minutes didn't seem to help
    <customBinding>
    <binding name="MrsProxyClientBinding"
    receiveTimeout="00:00:50"
    sendTimeout="00:00:50">
    <reliableSession ordered="true" />
    Below is the full text of the error I'm geting in the move request log. After this error occurs, the entire mailbox move process begins again. The strange thing is I've gotten successful moves of mailboxes up to 10Gb before, and this same error happens on a
    mailbox that's 4gb.
    Can someone help troubleshoot this error? It's driving me crazy.
    11/17/2011 10:00:00 PM [Server2] Initial seeding completed, 172342 items copied, total size 10.55 GB (11,327,875,162 bytes).
    11/17/2011 10:00:00 PM [Server2] Final sync has started.
    11/17/2011 10:02:13 PM [Server2] Transient error TimeoutErrorTransientException has occurred. The system will retry (1/60).
    Error details: The call to 'https://server1.domain.local/EWS/mrsproxy.svc server1.domain.local (14.1.325.0 caps:01FFFF)' timed out. Error details: The request channel timed out while waiting for a reply after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. --> The request operation did not complete within the allotted timeout of 00:00:50. The time allotted to this operation may have been a portion of a longer timeout. --> The request channel timed out while waiting for a reply after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. --> The request operation did not complete within the allotted timeout of 00:00:50. The time allotted to this operation may have been a portion of a longer timeout.
    at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallService(GenericCallDelegate del, String epAddress, VersionInformation serverVersion)
    at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationProxyClient.CallServiceWithTimeout(TimeSpan timeout, GenericCallDelegate del)
    at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationProxyClient.Microsoft.Exchange.MailboxReplicationService.IMailboxReplicationProxyService.IFolder_GetRules(Int64 folderHandle, Int32[] extraProps)
    at Microsoft.Exchange.MailboxReplicationService.RemoteFolder.Microsoft.Exchange.MailboxReplicationService.IFolder.GetRules(PropTag[] extraProps)
    at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.<>c__DisplayClass1c.<Microsoft.Exchange.MailboxReplicationService.IFolder.GetRules>b__1b()
    at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
    at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.Microsoft.Exchange.MailboxReplicationService.IFolder.GetRules(PropTag[] extraProps)
    at Microsoft.Exchange.MailboxReplicationService.FolderRecWrapper.ReadRules(IFolder folder, PropTag[] extraPtags)
    at Microsoft.Exchange.MailboxReplicationService.FolderRecWrapper.EnsureDataLoaded(IFolder folder, FolderRecDataFlags dataToLoad, ReportBadItemsDelegate reportBadItemsDelegate)
    at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass4`1.<LoadFolders>b__0()
    at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
    at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.LoadFolders[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
    at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.GetFolderMap[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
    at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.GetSourceFolderMap(GetFolderMapFlags flags, FolderRecDataFlags dataToLoad, GenericCallDelegate abortDelegate)
    at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyAllFolders()
    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<FinalSync>b__4b(MailboxMover mbxCtx)
    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
    at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: IFolder.GetRules
    OperationSide: Source
    Primary (34bdddb1-2e13-45ab-a575-3f6de414c398)
    PropTags: [ReportTime; 1627389955; 1627455491]
    Folder: 'MAILFOLDER', entryId [len=46, data=0000000083AB09B7111C3B4682D4140582FD21F30100E929EE996D69BF409B946039972CD120000000F4001F0000], parentId [len=46, data=0000000083AB09B7111C3B4682D4140582FD21F30100D60B955AB375EF4DB7D38206B8CDAA36000000E3000C0000]

    Hi,
    Please try the steps below to chang the following file:
    C:\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.Config file contents:
    --Change the following on the source side on the CAS server in the file MSExchangeMailboxReplication.exe.config
    • Changed the values from 1048576 to 3048576 :-
    <binding name="MrsProxyClientBinding"
    receiveTimeout="00:00:50"
    sendTimeout="00:00:50">
    <reliableSession ordered="true" />
    <textMessageEncoding>
    <readerQuotas maxArrayLength="3048576"
                          maxStringContentLength="3048576" />
    </textMessageEncoding>
    <httpsTransport authenticationScheme="Negotiate"
    maxReceivedMessageSize="3048576"
    allowCookies="true" />
    • Modify the 
    file MSExchangeMailboxReplication.exe.config on the target CAS server as follows:-
    binding name="MrsProxyClientBinding"
    receiveTimeout="00:00:50"
    sendTimeout="00:00:50">
    <reliableSession ordered="true" />
    <textMessageEncoding>
    <readerQuotas maxArrayLength="3048576"
    maxStringContentLength="3048576" />
    </textMessageEncoding>
    <httpsTransport authenticationScheme="Negotiate"
    maxReceivedMessageSize="3048576"
    allowCookies="true" />
    Note: make a backup before you change the value.
    Restart IIS and then try again to see if this works. Hope it is helpful.
    Best Regards Fiona Liao E: [email protected]

  • Can Exchange Online Protection work with Exchange 2010 on-premise

    I want to keep my current Exchange 2010 server but switch to Exchange Online Protection for anti-spam.
    Is that possible?
    Without doing any AD/Azure sync?

    Yes to both.  With directory synchronization you can have the added benefit of blocking mail to nonexistent recipients.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010 - associate all mailboxes (new and existing) to a custom ThrottlingPolicy

    I've seen that you can set an Organization-wide scope for a ThrottlingPolicy in Exchange 2013 (for a RecipientRateLimit)
    but I cannot find a way to do that in Exchange 2010.  Will the following command work in 2010, or is there a comparable command/method for 2010? I need this to be set for all existing users, on all servers/databases, and for all future users as well. 
    New-ThrottlingPolicy -Name RecipientsLimit -RecipientRateLimit 500 -ThrottlingPolicyScope Organization
    Thank you.
    Über Random

    Hi Uber,
    I'm afraid there is no way to set an organization wide scope in exchange 2010, because the "ThrottlingPolicyScope" parameter is not supported in exchange 2010, however it is supported in exchange 2013.
    Please check the parameter list which in the following articles:
    New-ThrottlingPolicy in exchange 2010
    New-ThrottlingPolicy in exchange 2013
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Decommission Exchange 2010 after all mailboxes have been moved to Exchange Online

    Currently very confused on what to do.
    I'm looking to migrate mailboxes to Exchange online using a Hybrid deployment with Dirsync. The users have multiple email and domain addresses. They are moving away from their SBS 2011 and Exch 2010 server. They have an AD and File and Print server. Once
    all mailboxes are moved and mx records are changed and everything is running smootkly. I would like to then decommission SBS and Exch 2010 box and still use DIRsync
    Few questions
    Once I remove Exch 2010 what wont I be able to do. Cant find anything specific online
    Will I still be able to create a user in AD then login to Exchange online and assign a license then
    the user would have mailbox
    Edit a user and add smtp email address.
    As I don’t have many users should I rather use PST migration or will I run into the same problems.

    Yes, you should move the arbitration mailboxes - they are organizational mailboxes, not mailbox database mailboxes.
    Make sure all Exchange resources and operations hosted on this server have been moved to your Exchange 2013 system before you remove Exchange from this server.  If you try to remove Exchange (in either the GUI or the command line) and something is
    still using this server, you will be alerted that something is still using the server and will be told what it is.
    HTH ...

  • Exchange 2003 to 2007 mailbox move - Multi-threading

    Hi all,
         i was moving mailboxes from 2003 to 2007sp3, i was trying to move 10 mailboxes at a time using max thread command line, but it seems to working only two at a time, can you please advise?
    tnx
    lrok
    Lrok

    Are you using the EMS to initiate the moves? If so, use the -MaxThreads parameter to increase the number of concurrent moves.
    However, the default is "4". If only two are moving at a time there's probably some throttling going on because of poor performance. Increasing the concurrency probably would result in worse performance.
    I forget if the restriction on the 2003 side is "2". If it is, you can run multiple sessions and increase the concurrency in that way. It's not the same as increasing the number of threads, but multiple processes may get you the increase you need. Just
    don't overdo it. :-)
    --- Rich Matheisen MCSE&I, Exchange MVP

  • Exchange 2010 cannot create mailbox

    Hi
    I cannot create a mailbox on the exchange, I am getting an error: 'You must provide a value for this property'..

    Hi Guy's, that for the replies so far...
    let me fill in a few gaps.
    We had a server crash on a old exchange server(Exch 2010 sp1)
    We created a new server and imported all the mail to the new server.
    There now was still some reverences to the old server. It was removed from adsiedit but it is still stuck in some places and i think that is what is causing the issue. The old server does not exist anymore so could not uninstall.
    i Have restarted the Exchange server so all services has been restarted.
    Error in the application log:
    Cannot find route to Mailbox Server CN=SVVCAB029\0ADEL:a4b9500f-d0f8-4101-8ea8-001c74078ad5,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Dac Systems,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=dac,DC=local
    for store CN=Mailbox Database 1124606198,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Dac Systems,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=dac,DC=local in routing tables with timestamp 2012/07/20
    07:12:25 AM. Recipients will not be routed to this store.
    When we try and create a new user we get the error above. i Do specify the mailbox db to use as you can still see the old on in there but no luck...

  • Exchange 2010 SP3 - Search-Mailbox -DeleteContent fails: the search folder timed out.

    We have a bunch of users that have hundreds of thousands of Undelivered Mail Returned to Sender email in their inbox. I believe these mailboxes were compromised and were sending out spam. We have fixed that issue, but I am trying to clean out all these messages
    from their inbox. I have run this command successfully on a few users, but this one in particular is giving me troubles. This mailbox has over 400,000 items to delete so I am wondering if there are just too many to process.
    Search-Mailbox -Identity EMAIL -SearchQuery "Subject:'Undelivered Mail Returned to Sender'" -DeleteContent
    Here is the error:
    The search on mailbox ....... did not complete because the search folder timed out.
        + CategoryInfo          : ReadError: (0:Int32) [Search-Mailbox], SearchFolderTimeoutException
        + FullyQualifiedErrorId : EC2CC554,Microsoft.Exchange.Management.Tasks.SearchMailbox
    I don't like the idea of having to delete these manually. If someone has an idea that would be fantastic.
    Thanks

    Hi,
    Based on the description, you couldn't run the search-mailbox cmdlet to delete all items after several times. I discussed with my colleagues, there is a limit when trying to delete items using search-mailbox cmdlet, it's 10000 at a time if a search query
    is specified. The error you got may be related to the large amount of items. Some scripts may help you to delete them all at a time, you can ask this question on the Script forum to get a better help.
    As a workaround, you can create an Outlook Inbox rule for these messages and move them to a specific folder. After that, you can delete the folder permanently.
    Here is a similar thread for your reference.
    http://community.office365.com/en-us/f/158/t/239292.aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2007 to Exchange 2010 cross forest simultaneous mailbox move limits

    Hi All, 
    I am testing the throughput of mailbox moves from Exchange 2007 to Exchange 2010 cross forest. Single mailbox moves seem to be quite fast and I am not concerned about network, disk IO or server resource limitations, however I have not tested multiple simultaneous
    mailbox moves to determine what the Exchange limitations are. If anyone could identify the limitations of the items below it would be much appreciated: 
    Limit of Exchange 2007 simultaneous mailbox moves per database
    Limit of Exchange 2007 simultaneous mailbox moves per Mailbox server
    Limit of Exchange 2007 simultaneous mailbox moves per CAS server
    Limit of Exchange 2010 simultaneous mailbox moves per database
    Limit of Exchange 2010 simultaneous mailbox moves per Mailbox server
    Limit of Exchange 2010 simultaneous mailbox moves per CAS server
    Any other Exchange 2007 or 2010 hard coded limits
    Thanks in advance. 
    Michael.

    My usual answer to this question is that Microsoft set these limits for a reason.  Increasing them may not offer you much in the way of benefits if you end up slamming the server.  I generally recommend that you leave them alone.
    I have had occasional opportunities to change these constraints, most notably back during a migration to Exchange 2003 and international mailbox moves (Asia to U.S.) where the limiting factor was network latency.  I was able to increase the number of
    concurrent threads to 16 from the default 2 and there was still available bandwidth because the process was limited by the latency. 
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Outlook 2010 SP1 Profile Does Not Update After Moving Mailbox Between Exchange 2010 SP2 Sites

    I am working on a large mailbox migration from one AD site to another. 
    Exchange version at both sites:Exchange 2010 SP2
    Two Mailbox Servers: MBX01 in site A / MBX02 in site B
    (There is a DAG but keeping this simple)
    Two CAS Arrays: CASA.domain.com / CASB.domain.com
    The RPCClientAccessServer property is set accordingly.  Where MBX01 is set to CASA.domain.com and MBX02 is set to CASB.domain.com
    Clients:Outlook 2010 SP1
    Scenario: I successfully move a mailbox from Site A to Site B.  The Outlook client does not automatically update its server settings to point to the new cas array (CASB.domain.com) and continues to connect to the old CAS server (CASA.domain.com).
    I have seen a few articles regarding this pointing to workarounds such as:
    - repairing the outlook profile on the client
    - delete the existing outlook profile
    - run a script to update the prf file (re-cache's email at the client)
    I am interested in knowing if anyone else has experienced this, what their solution was for a large migration and if any roll-ups or service packs have possibly fixed this problem.
    I would also like to know if you have seen this affect ActiveSync devices.  I am getting mixed results in my tests and thought it may be contributed toward different device types, mobile os versions, etc...
    I have posted this to the Exchange 2010 forum as well, just wasn't sure where to start.
    Thanks.
    Mike

    Hi,
    Seems you got several replies in the thread below that you posted in Exchange forum:
    http://social.technet.microsoft.com/Forums/exchange/en-US/68ae67c1-59f5-44bb-aadc-0aea3f72ad2d/outlook-profile-not-updated-to-new-cas-array-after-mailbox-move-between-sites?forum=exchange2010#68ae67c1-59f5-44bb-aadc-0aea3f72ad2d
    Please come back to the thread above and check if the replies are helpful.
    Since this issue is more related to Exchange, we can provide rarely assistance on this problem. If you need any help on Outlook client side, please don't hesitate to let me know.
    I would appreciate it if you could post the solution here when you found it, so that other community members who have same question in this forum will benefit from it.
    Best Regards,
    Steve Fan
    TechNet Community Support

Maybe you are looking for