Any End User Benefits Of Exchange 2010 to 2013 Upgrade?

Most of the benefits I see when I search online for new features of Exchange 2013 seem to be related to administrative functions that users don't see or care about.
What are the biggest benefits that end users can see for moving from Exchange Server 2010 to Exchange Server 2013 that don't require also upgrading Office 2010 to 2013 to take advantage of?

If your users do nothing in Outlook but send and receive messages, then there is probably no benefit. That would be true in just about any version of Exchange.
If however, they are interested in improved connectivity (Outlook Anywhere/ MAPI/HTTP in SP1) and getting a superior experience on mobile devices and tablets as well as access to apps, the 2013 is a must.
Don't forget the improvements coming Exchange's way in the future:
http://blogs.technet.com/b/exchange/archive/2014/04/24/mec-2014-recordings-are-here.aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • OWA still lands at Exchange 2010 for users migrated from Exchange 2010 to 2013

    I never had any issues with OWA redirection for a few users that I migrated from Exchange 2010-2013 initially. For users that I am migrating in the past few days, the OWA 2013 is landing on Exchange 2010 despite the mailbox being successfully migrated to
    Exchange 2013.
    Troubleshooting:
    1. I have restarted the IIS Services
    2. I have restarted MSExchangeOWAAppPool.
    3. I have also checked the homeMDB attribute of the 2013 migrated user with the Exchange 2013 database.
    I would really appreciate if anyone could share their experiences on similar issues.

    I have checked it, the migration status is completed. In regard to the namespaces, both CAS 2010 and 2013 are set to mail.domain.com; CAS 2013 is the internet facing. I have also checked the internal access for OWA, it's the same scenario. Migrating them
    back to 2010 and 2013 won't resolve the issue in my case, because the issue persists for every new user that I am migrating.
    I recently found the following when I login with a user who is not effected and then logout:
    1. Login in back with the affected user without closing the browser or clearing the cache, it lands at CAS 2013 OWA.
    2. However, I get the below listed error message when I logout. 
    Your request couldn't be completed.
    Click here to continue working.
    This may have occurred for security reasons or because your session timed out.

  • "Resend" option is not working for specific user. "The Operation Failed" Exchange 2010 Outlook 2013

    Hi Everybody. I have a weird one for you.
    I have a user that gets an "operation failed" message whenever trying to use the "resend" option on any email (It's the one right under recall). I had tested up and down on her machine. Exchange 2010 Outlook 2013
    Ran in safe mode, recreated her profile, disabled virus scanning, repaired office. (weird, the font just changed sizes on me)
    After all of this I tested on other computers, other users seem to be able to "resend" just fine. However her account does not work on any computer I try, internal or external to the network.
    It looks more like a profile issue.
    She's a very active archivist, so she only has 486MB of space used by her mailbox.
    It's well under quota.
    It's been really puzzling me.
    MCSE 2003, Exchange. MCTS Vista, 7. Administrator of awful, neglected website http://timssims.net

    Hi Timssims,
    Since there is only one user in the org has this issue, it seems an issue on the Outlook client side.
    I suggest asking Outlook Forum for help so that we can get more professional suggestions.
    For your convenience:
    https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
    However I also have some suggestions for your reference:
    1. If this issue occur on Cached Mode, I suggest turning to Online Mode for testing.
    2. Please also paste the detailed error message if "operation failed" is not the
    complete information.
    3. If still not works after perform operations above (including suggestions from Outlook Forum), I suggest re-creating a new mailbox for the specific user just as Martin suggested.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 to 2013 users migration

    Hi,
    I am migrating users from Exchange 2010 to 2013 and facing a lot of migration issues. few of them are as follow.
    1. It hung up at "syncing" and end up with a failure.
    2. After a long migration i got the following errors
    Error: MigrationPermanentExeception: Failed to reset the target mailbox after the move. Error Details:MaipExceptionADUnavailable: Unable to prepopulate the cache for user :: on domain controller xyz.domain.com (hr=0x80004005,ec=2414) Diagnosti Context: Lid:
    65256 Lid:1494 ---- Remote Context Beg ---- Lid: 52664 StoreEc: 0x96E Lid: 35973 StoreEc: 0x96E Target Mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible.
    Error details: Target mailbox connection was lost.
    3. users migration is taking a lot of time although mailbox size is not big and both servers are in same datacenter.
    Need urgent help pls....

    Hi,
    Here are the general steps for troubleshooting mailbox moves:
    1. If the move request didn't complete, view the Move Request Statistics.
    2. If the move request completed with errors, view the move report.
    3. View the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
    4. use the Exchange Management Console or the Exchange Management Shell to increase the diagnostic logging levels on the Client Access server for the Mailbox Move and Service categories of the MSExchange Mailbox Replication service.
    For more detailed information about general steps for troubleshooting mailbox moves, you can refer to the article below:
    http://technet.microsoft.com/en-us/library/dd638094(v=exchg.141).aspx
    Additionally, in order to narrow down the cause, I’d like to confirm the following information:
    1. Are the problematic target mailboxes in the same database?
    2. Is there a time boundary? After that, you cannot move mailboxes:
    http://social.technet.microsoft.com/Forums/en-US/90403f75-e530-478a-ab68-27823b730f68/exchange-2013-batch-to-migrate-users-from-2010-database-is-hung-at-syncing-after-a-disaster?forum=exchangesvrdeploy
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • How to use Powershell to set delegate for user mailbox in Exchange 2010 and Office 365

    Hello,
    Can you please tell me if I can set delegate for user mailbox in Exchange 2010 or Office 365 using Powershell?
    If I can, then how can I do that? (which Powershell commands for setting the delegate?)
    Many thanks, and have a good day!

    Hi,
    If you wanted to add a delegate to possiblly a large number of users or you do this during mailbox provisioning. So the following script will use
    impersonation to access another users mailbox and add a delegate.
    $mbtoDelegate = "[email protected]"
    $delegatetoAdd = "[email protected]"
    $dllpath = "C:\Program Files\Microsoft\Exchange\Web Services\1.0\Microsoft.Exchange.WebServices.dll"
    [void][Reflection.Assembly]::LoadFile($dllpath)
    $service = new-object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1)
    $windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
    $sidbind = "LDAP://<SID=" + $windowsIdentity.user.Value.ToString() + ">"
    $aceuser = [ADSI]$sidbind
    $service.AutodiscoverUrl($aceuser.mail.ToString())
    $service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress,
    $mbtoDelegate);
    $mbMailbox = new-object Microsoft.Exchange.WebServices.Data.Mailbox($mbtoDelegate)
    $dgUser = new-object Microsoft.Exchange.WebServices.Data.DelegateUser($delegatetoAdd)
    $dgUser.ViewPrivateItems = $false
    $dgUser.ReceiveCopiesOfMeetingMessages = $false
    $dgUser.Permissions.CalendarFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Editor
    $dgUser.Permissions.InboxFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Reviewer
    $dgArray = new-object Microsoft.Exchange.WebServices.Data.DelegateUser[] 1
    $dgArray[0] = $dgUser
    $service.AddDelegates($mbMailbox, [Microsoft.Exchange.WebServices.Data.MeetingRequestsDeliveryScope]::DelegatesAndMe, $dgArray);
    Hope this helps.

  • You do not have access to any End User Layer tables

    Hello Guru's!
    I'm having an issue with connecting/using EULs on Disco 10g - I have already installed 10g Admin and configured 2 EULs and also imported the sample data - they are all owned by DISCO user -
    When I connect to http://discoserver:7778/discoverer/viewer, I get a connection screen - no connections are listed, so I click create connection - I give it a name, put in disco as my user, put my password in, put db_connect_string into the appropriate field, where db_connect_string is my actual connect string - and it gives me this error:
    Error
    Authentication Failed.
    (You do not have access to any End User Layer tables)
    I have access to these, as I'm the EUL owner - I've also tried this tho with other users that I have granted access to in the admin too (I've even granted access to these EULs to public - still no luck) - should I be using the db user and password or are there other places in 10g that I set up disco users?
    If I should be using the db user and pass, why won't it see my EULs?

    Hopefully CupJr got his answer as it's been over 2 years!
    However, if you're having the same problem ...
    1. is this an Apps EUL and you're connecting as a database user (ie: the owner of the EUL)?
    2. have you set the gateway connection info correctly (again if an Apps EUL)? - found at: Tools -> Options -> Connection.
    Russ

  • Unable to connect End user layer /You do not have access to any end user Layer tables

    I get the following error message in Disco Admin ver 4.1.33.1.6 :
    1)Unable to connect End user layer
    In disco plus I get the follg error:
    a)You do not have access to any end user Layer tables
    This is despite the fact that my userid/passsword combination@databaseid has acess to all tables in Oracle sqlplus SQL*Plus: Release 8.0.6.0.0 -
    Connected to:
    Oracle8i Enterprise Edition Release 8.1.7.1.0 - 64bit Production
    With the Partitioning option
    JServer Release 8.1.7.1.0 - 64bit Production
    Please reply ASAP if anyone has any ideas
    Thanks
    Gurman
    null

    Have u created a EUL for your user through Administration Edition.
    If not login as a user who has DBA rights and create EUL for your user.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Gurman Sandhu ([email protected]):
    I get the following error message in Disco Admin ver 4.1.33.1.6 :
    1)Unable to connect End user layer
    In disco plus I get the follg error:
    a)You do not have access to any end user Layer tables
    This is despite the fact that my userid/passsword combination@databaseid has acess to all tables in Oracle sqlplus SQL*Plus: Release 8.0.6.0.0 -
    Connected to:
    Oracle8i Enterprise Edition Release 8.1.7.1.0 - 64bit Production
    With the Partitioning option
    JServer Release 8.1.7.1.0 - 64bit Production
    Please reply ASAP if anyone has any ideas
    Thanks
    Gurman
    <HR></BLOCKQUOTE>
    null

  • You don't have access to any End User Layer table

    Hi
    When I created a EUL using Discoverer admin, and also created a business area successfully, then I can't logon using same username in Discoverer desktop, My Discoverer version is 4.1.37. when I logon, I received error message read: You don't have access to any End User Layer table.
    Could someone please give me some instruction, or guide me to do something.
    .

    Hi Prathima
    You should not be able to connect to an Apps mode EUL as an end user in the end user tools.
    As for administration, you need to log in as the owner of the EUL, a database user, and then assign admin rights to an Apps account. Many companies use the SYSADMIN Apps account for this purpose. After you have assigned an Apps user to have admin rights don't forget to grant that user admin privileges over each of your business areas.,
    With this done you should then manage your Discoverer administration using the Apps account.
    Page 14 to 20 of the document called Setting up an Apps mode EUL may help. This document is available for free from my website here: http://ascbi.com/downloads/downloads.htm
    Best wishes
    Michael

  • Unable to connect to : eul4_us@VIS, You do not have access to any End User

    Hi all
    I have configured and created EUL in 11.5.10.2 VISION instance on widows 2003,
    When I tried to connect to Discoever4i on 11i VIS instance I am getting the following error :
    Unable to connect to : eul4_us@VIS
    You do not have access to any End User Layer tables
    But I can connect to eul4_us@VIS via TOAD and SQL*PLUS Client, Also Discoverer Administration Edition can connect to eul4_us@VIS.
    Also with the same Discoverer Release 4 Desktop Edition we can connect to the another VIS instance which is running on solaris 9, Only problem with the VIS at Windows2003,
    Please Can any one give some solutions ASAP
    Thanks
    Divyanand

    Hi,
    In general, with an Apps mode EUL I would expect that you will get the the "You do not have access to any End User Layer tables" when you connect to desktop as the EUL owner. This is because the EUL owner does not have (and does not need) privileges to the Apps tables and functions. You should connect to Desktop as an Apps user.
    Rod West

  • Archive Mailbox Duplicated - Exchange 2010/Outlook 2013

    Hi,
    I have enabled archive mailboxes for a number of users in an Exchange 2010 environment no problem.
    There is one user though,  that is seeing two online archives:
    Online Archive - <Firstname> <Surname>
    Online Archive - <email address>
    Both are replicas of the other.
    Any ideas how to get rid of the duplicate?

    I just encountered the same issue.  This has been going on for months with my mailbox and no one else's.
    I can't tell you how many outlook profiles I created in attempt to fix this.
    Originally I was running Outlook 2010 when the issue happened.  In my case I had one archived named "Online Archive."  The second one was named "Personal Archive."  If I expanded either one, I could see the contents in it without issue, but
    I couldn't expand the other.  I didn't save the error message, but something about being unable to access it.
    Once I started using 2013, both archives changed to be called "Online Archive," and were able to be expanded simultaneously. Any changes made in one were immediately reflected in the other.  But it still left me with the duplicate archives.
    I had reset my password using AD Users and Computers a number of times, but it was always set to the same password.  This went on for probably 4 months.  Finally I reset my password via ctrl+alt+del.  I closed outlook, made sure outlook.exe
    wasn't running, opened it back up, and the duplicate archive is GONE!
    I even reset the password back to the original one via AD Users and Computers and the duplicate archive has not come back.
    Excellent detective skills walshyno_1.  But I really want to know why this happens.  How is it even possible that creating a different password would remove the duplicate Exchange archive view in Outlook?

  • Exchange 2010 and 2013 coexistence Internal and external URL

    Hi all,
    been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
    Still i dont get any smarter.
    Here is scenario:
    Exchange 2010
    Cas1
    Cas2
    Mailbox1
    Mailbox2
    Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
    Exchange 2013
    CAS+Mailbox
    Cas+Mailbox
    DNS
    mail.exchange.com pointing to VIP (kemp loadbalancer)
    Autodiscover ( pointed to same vip ,kemp load balancer)
    Outlook anywhere on all servers (2010 and 2013)
    Internal ( pointing to VIP on Kemp)
    External ( pointing to external IP,then it passes firewall that again passes to kemp)
    Problem we are having is when migrating users from Exchange 2010 - 2013.
    Users using Outlook 2010
    restart of outlook and mail  works fine.
    OWA works fine
    Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
    Users using Outlook 2013
    Outlook in disconnected status,only fix is to create new profile.
    OWA works fine
    Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
    Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
    Where is the config wrong?
    Thanks!
    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! Off2work

    Hi Martina,
    did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
    Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
    Tried repair Outlook profile,no og.Only fix is to setup New account.
    Any more tips?
    thanks!
    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! Off2work

  • Exchange 2010 to 2013 Co-Existence Reverse DNS Issue

    We are running a Exchange 2010 and 2013 coexistence.  Mail Flow is fine on the 2013 side, but for mailboxes still on 2010, some are getting mail delivery failures only for certain external addresses.  One of the deliveries says the Sending IP
    does not have a valid rDNS.  The IP Address it sent back is the main Public IP and not the Public IP assigned to our mail servers.  Not understanding why the 2013 mailbox users can send to these external addresses no problem when 2010 mailbox users
    are being routed through 2013.  Thanks for any help.

    Hi,
    According to your post, I understand that account in Exchange 2010 deliver message failed for certain external addresses, however the user in Exchange 2013 works fine.
    If I misunderstand your concern, please do not hesitate to let me know.
    Whether all user in Exchange 2010 or some special account experience this question?
    If this issue only occur on some specific external address, please contact its administrator to double confirm the configuration of anti-spam filter.
    Besides, I recommend run Message tracking log and Protocol log to check the deliver process. More details about “Analyzing the protocol logs and Message tracking logs in Exchange 2013”:
    http://social.technet.microsoft.com/wiki/contents/articles/23182.analyzing-the-protocol-logs-and-message-tracking-logs-in-exchange-2013.aspx
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Migrate Exchange 2010 to 2013 External Mail Flow

    Dear All,
    I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
    2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
    The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
    How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
    How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
    Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
    Kindly guide if any thing missing that need to address during start the migration activity.
    Thanks in Advance

    Hi ,
    Sorry for delay.
    Question : Thanks for your valuable response. On
    point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
    Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
    2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
    For mailbox connectivity issue in exchange 2013 :
    1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
    2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
    2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
    needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
    3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
    service is not reaching the proxy server if you have on your network.
    In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
    on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
    4.please share me the output for the below mentioned command.
    get-ClientAccessServer -Identity “server name”  | fl AutodiscoverServiceInternalURI 
    5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
    6.On which operating system version those outlook 2007 clients are installed?
    Please reply me if anything is unclear.
    Thanks & Regards S.Nithyanandham

  • Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

    I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
    as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
    Symptoms:
    Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
    from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
    URL to connect to my proxy server for Exchange: webmail.domain.com
    Connect using SSL only: Checked
    Only connect to proxy servers that have this principal name in their certificates: Unchecked
    On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
    On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
    After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
    first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
    Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
    Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
    domain: blank
    username: their AD username
    server: webmail.domain.com
    After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
    begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
    for mobile users in the same way that it's been working for us with Exchange 2010?
    Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

    Hi,
    Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
    Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
    fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
    Please restart the following Exchange service to have a try:
    Microsoft Exchange RPC Client Access
    Microsoft Exchange Mailbox Replication
    Restart IIS service by running IISReset in a Command Prompt window.
    Then check whether the Outlook client can connect to Exchange 2013 or not.
    As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
    Regards,
    Winnie Liang
    TechNet Community Support

  • Manually Move Public Folders from Exchange 2010 to 2013

    Hi all,
    I have a issue to finishing my migration from Exchange 2010 to Exchange 2013, I have been trying to migrate my Public folders but always after a couple hours, the migration state is failed.
    The final error is the following:
    FailureCode                      : -2146233088
    FailureType                      : SourceMailboxAlreadyBeingMovedPermanentException
    FailureSide                      :
    Message                          : Error: Couldn't switch the mailbox into Sync Source mode.
                                       This could be because of one of the following reasons:
                                         Another administrator is currently moving
    the mailbox.
                                         The mailbox is locked.
                                         The Microsoft Exchange Mailbox Replication
    service (MRS) doesn't have the correct
                                       permissions.
                                         Network errors are preventing MRS from cleanly
    closing its session with the
                                       Mailbox server. If this is the case, MRS may continue
    to encounter this error for
                                       up to 2 hours - this duration is controlled by the TCP
    KeepAlive settings on the
                                       Mailbox server.
                                       Wait for the mailbox to be released before attempting
    to move this mailbox again.
    So, after seeing this I started to monitoring all process and I realized that after creating hierarchy the process start to fail and keep in StalledDueMailboxlock status, and the error is:
    FailureCode                      :
    FailureType                      :
    FailureSide                      :
    Message                          : Informational: The request has been temporarily postponed because the mailbox is
                                       locked. The Microsoft Exchange Mailbox Replication service
    will attempt to continue
                                       processing the request after 2/14/2015 12:38:20 PM.
    Finally, digging more into reports of migration I  found this:
    MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to open entry ID. (hr=0x80040115, ec=6)_x000A_Diagnostic context:_x000A_ Lid: 40487 EMSMDBMT.EcDoRpcExt2 called [length=73]_x000A_ Lid: 44583 EMSMDBMT.EcDoRpcExt2
    exception [rpc_status=0x6][latency=0]_x000A_ Lid: 62184 _x000A_ Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a_x000A_ Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 51452_x000A_ Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-02-14T14:25:40.9210000Z_x000A_
    Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2_x000A_ Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 6_x000A_ Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1741_x000A_ Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0_x000A_ Lid: 11672 dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 0_x000A_ Lid: 23260 Win32Error: 0x6_x000A_ Lid: 61553 StoreEc: 0x80040115_x000A_ Lid: 52176 ClientVersion: 15.0.1044.25_x000A_ Lid: 50032 ServerVersion: 14.3.181.6_x000A_ Lid: 50128 _x000A_ Lid: 50288 _x000A_ Lid: 23354
    StoreEc: 0x80040115_x000A_ Lid: 25913 _x000A_ Lid: 21817 ROP Failure: 0x80040115_x000A_ Lid: 22894 _x000A_ Lid: 24942 StoreEc: 0x80040115
    So, would like to know if exist any procedure to migrate/move my Public Folders from Exchange 2010 to 2013 manually, something like Export/Import.
    Regards!

    What script and process you are running to migrate the Public Folders?
    And what do you mean by Manually?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.comTwitter:
    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.

Maybe you are looking for