Migrate mailboxes from Exchange 2013 to Exchange 2010

Hello,
We have a merger and would like to know if it is possible to migrate mailboxes from Exchange 2013 to Exchange 2010 in a cross-forest scenario.
Or should we first upgrade destination Exchange 2010 to 2013?
Peteris

Hi Peteris,
Based on my tests, we can move mailboxes from Exchange Server 2013 to Exchange server 2010. You can use the Prepare-MoveRequest.ps1 script in the EMS to prepare mailboxes for cross forest moves.
For more information about it, here is a helpful article for your reference.
Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
Hope my clarification can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

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

Migrating user from Exchange 2010 to Exchange 2013 succeeds but OWA redirects to 2010

Hello everyone,
I am migrating users from exchange 2010 to 2013, Users migration works perfectly and completes without any issue but after the user migration finishes I try to login to OWA but user goes to OWA exchange 2010 not 2013 as if the mailbox has not been migrated.
I have checked the HomeMDB attribute and I can see the new database on 2013 is located there. how to solve this? I have retransfered the user back to 2010 and 2013 but it didn't work.
I would appreciate your help.
Thanks
Mohammed JH

Hi Amit
After 30 mins approximately we checked the inboxes that have been migrted (2) and we found out they are working.
İ wonder why there is this delay ? İ have already done migration before but it never took this much time. İ would appreciate your reply.
Thanks
Mohammed JH

OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

Anyone come across this?
Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
outlook client knows the mailbox has moved as it connects to the new server
Not happening to every mailbox
thak=nks

Hi,
After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Move mailbox from exchange 2010 2003 , Transient error MapiExceptionLogonFailed has occurred.

We are currently migrating from Exchange 2003 to Exchange 2010, same domain.
We have successfully moved some mailboxes from exchange 2003 to exchange 2010 without any problems.
Now we need to move 1 mailbox back from exchange 2010 to exchange 2003.
After creating the moverequest it stucks on 0% and the log shows the error below.
After using Bing I found this post -> http://social.technet.microsoft.com/Forums/exchange/en-US/ef41ae05-8816-4c0c-968a-c48f0e3d50b5/move-mailbox-back-from-exchange-2010-to-exchange-2003-failure?forum=exchangesvrdeploylegacy
This suggest ->
After I give FULL permissions to each Mailbox Stores on Exchange 2003 server, I was able to move my mailbox back onto the Exchange 2003 server. In details:
Simply right click Storage Group\Mailbox Store and go to Security, in there you may see Exchange Servers group already there, if no add it in, then give it FULL permissions! and thats it!
Create a new move request but still stuck on 0% and error as below
20-3-2014 16:32:10 [ex2010p11] 'contoso.com/Users/exadmin' created move request.
20-3-2014 16:32:11 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'exchangep21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:11 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:11 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:11 [ex2010p21] Request processing started.
20-3-2014 16:32:11 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (1/60).
Error details: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
Diagnostic context:
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: ex2003
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -545057711
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 45169 StoreEc: 0x824
Lid: 44273
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 56945
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 59505 StoreEc: 0x3F2
Lid: 52465 StoreEc: 0x3F2
Lid: 60065
Lid: 33777 StoreEc: 0x3F2
Lid: 59805
Lid: 52209 StoreEc: 0x3F2
Lid: 56583
Lid: 52487 StoreEc: 0x3F2
Lid: 19778
Lid: 27970 StoreEc: 0x3F2
Lid: 17730
Lid: 25922 StoreEc: 0x3F2
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName,
Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize, Client xropClient, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId)
at Microsoft.Exchange.MailboxReplicationService.MapiUtils.OpenSystemMailbox(Guid mdbGuid, String serverDN, String dcName, NetworkCredential cred, String& systemMailboxDn)
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.OpenSystemMailbox()
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncStateStr)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass57.<Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState>b__56()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncState)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.ClearSyncState()
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass23.<CleanupOrphanedDestinationMailbox>b__22(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CleanupOrphanedDestinationMailbox(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IMailbox.SaveSyncState
OperationSide: Target
Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)
Key: F2FA63B0116C564EA4C598D69786443D9E4FB582FF27D2449142F949D567E1E7E0CA914F6695624C98892FA527AAA91E
SyncStateLength: 0
20-3-2014 16:32:41 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'ex2010p21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:41 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:41 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:41 [ex2010p21] Request processing started.
20-3-2014 16:32:41 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (2/60).

Hello，
When you move mailbox from exchange 2010 to exchange 2003, please check if the following situations exist:
http://technet.microsoft.com/en-us/library/dd638157(v=exchg.141).aspx
Before you move mailbox again, please clear the previous move request.
I recommend you use EXBPA to check your exchange server 2003 and exchange 2010.
Please check if inheritable permission is missing on the mailbox store on Exchange Server 2003.
Cara Chen
TechNet Community Support

Export Mailbox from Exchange 2010 and Import to Exchange 2007

Hello,
I exported mailbox (1GB in size) from Exchange 2010 to *.pst file; I need to import it into
Exchange 2007 mailbox. Is it supported ?
The operation completed successfully (no errors) but no items were imported; is it due to unsupported backward compatibility or some other issue ?
Thank you,
Luca
Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

I also have the same issue. Exported mailboxes on Exchange 2010 SP3 latest updates using
New-MailboxExportRequest and then tried to import into mailbox on Exchange 2007 SP3 with latest updates. The 32-bit client machine used for the import has Outlook 2010 SP1 (SP2 and later updates causes a different error). I used Outlook 2010 because the E2K10
New-MailboxExportRequest documentation states that you have to use Outlook 2010 or later. The PST files created can be opened and imported via Outlook but not with the
Import-Mailbox cmdlet (with no error as stated in this thread). Other PSTs, not created from E2K10 export do import just fine. I also ran ScanPST.exe against the exported PST and then ran the import again and it worked, everything got imported. Interestingly
the test mailbox PST file I was using was 761 KB but after the ScanPST it was 1,257 KB - must be some difference in the PST format that the Import-Mailbox cmdlet can't deal with.
Does anyone have any other solutions or
workarounds to this. I've got over 900 mailboxes I need this for due to an
acquisition? Has anyone tried using Outlook 2013 on the machine used for doing
the Exchange 2007 imports or does Outlook 2013 also have the same issue as later versions of Outlook 2010 (Exchange Mailbox import failed with error code 2147221233)?

Migrate UM from Exchange 2010 to Exchange 2013

I have been running Exchange UM since Exchange 2007, using the ps1 script to move all my Auto Attendants into the 2010 environment. I'm at a loss on how to efficiently do this in moving from Ex2010 to Ex2013, though. I've read
http://technet.microsoft.com/en-us/library/dn169226 and it's Step 3 that's got me bewildered. I have 44 Auto Attendants, most of which with up to five custom greetings, numerous key mappings,
etc. That Step 3 indicates having to move each custom greeting individually.
I'm just getting into PowerShell and struggling as-is. Compounding that floundering with the lack of clear documentation on moving custom greetings en mass has me frustrated. Any assistance would be greatly appreciated. Thank you.

Hi David,
Before we migrate all the users to
2013, we would recommend you to test voice mail on
2013 server.
Here are the steps we need to follow
to test VM on 2013 server:
1. Create a certificate for both Unified Messaging service and the Call Router services. Here is an article on how
to create certificates , http://technet.microsoft.com/en-us/library/dn205141(v=exchg.150).aspx
2. Create new dial plan in Exchange
2013. Here is an article on how to create a dial plan, http://technet.microsoft.com/en-us/library/bb123819(v=exchg.150).aspx
3. Run scripts on both Exchange and Lync servers.
4. Create test user and enable the user for both Lync and Exchange.
5. Enable newly created user for UM and test voicemail for that user.
Additionally here is a link which has checklist to upgrade
from Exchange 2010UM
to 2013UM http://technet.microsoft.com/en-us/library/dn169228(v=exchg.150).aspx
Thanks,
James

Move mailbox from Exchange 2010 SP3

Hi all. I implemented Exchange 2013 in my current Exchnage 2010 environment, update this server to version 15.0 build 847.32. Build Exch2010 - 14.3 (build 123.4). Then i move mailbox from exch2010 to exch2013 this request all time "queued" and
not migrate to exch2013:
PS C:\Windows\system32> Get-MoveRequestStatistics Scom
DisplayName StatusDetail TotalMailboxSize TotalArchiveSize
PercentComplete
scom Queued 575.3 KB (589,056 bytes)
0
I restart services Microsoft Exchange Replication, Microsoft Exchange Search, Microsoft Exchange Search Host Controller, but no result(

PS C:\Windows\system32> Get-MoveRequestStatistics Scom | FL
RunspaceId : 64b764aa-8b7c-435e-8bb7-2b5fbe3692ba
MailboxIdentity : polikomm.local/Users/scom
DistinguishedName : CN=scom,CN=Users,DC=polikomm,DC=local
DisplayName : scom
Alias : scom
ExchangeGuid : ed423e14-5c3b-42a8-910d-48fa6e7c4335
ArchiveGuid :
Status : Queued
StatusDetail : Queued
SyncStage : None
Flags : IntraOrg, Pull
RequestStyle : IntraOrg
Direction : Pull
IsOffline : False
Protect : False
DoNotPreserveMailboxSignature : False
Priority : Normal
WorkloadType : Local
Suspend : False
SuspendWhenReadyToComplete : False
IgnoreRuleLimitErrors : False
RecipientTypeDetails : UserMailbox
SourceVersion : Version 14.3 (Build 210.0)
SourceDatabase : Mailbox Database
SourceServer : pc-mail.polikomm.local
TargetVersion : Version 15.0 (Build 847.0)
TargetDatabase : Mailbox Database 0506035495
TargetServer : EXCHANGE2013.polikomm.local
SourceArchiveDatabase :
SourceArchiveVersion :
SourceArchiveServer :
TargetArchiveDatabase :
TargetArchiveVersion :
TargetArchiveServer :
RemoteHostName :
RemoteGlobalCatalog :
BatchName : MigrationService:MoveSCOM
StartAfter :
CompleteAfter :
RemoteCredentialUsername :
RemoteDatabaseName :
RemoteDatabaseGuid :
RemoteArchiveDatabaseName :
RemoteArchiveDatabaseGuid :
TargetDeliveryDomain :
ArchiveDomain :
BadItemLimit : 1000
BadItemsEncountered : 0
LargeItemLimit : 0
LargeItemsEncountered : 0
AllowLargeItems : True
QueuedTimestamp : 15.01.2015 14:46:18
StartTimestamp :
LastUpdateTimestamp : 15.01.2015 14:46:18
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp :
CompletionTimestamp :
SuspendedTimestamp :
OverallDuration : 07:20:29
TotalFinalizationDuration :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration :
TotalFailedDuration :
TotalQueuedDuration : 07:20:29
TotalInProgressDuration :
TotalStalledDueToCIDuration :
TotalStalledDueToHADuration :
TotalStalledDueToMailboxLockedDuration :
TotalStalledDueToReadThrottle :
TotalStalledDueToWriteThrottle :
TotalStalledDueToReadCpu :
TotalStalledDueToWriteCpu :
TotalStalledDueToReadUnknown :
TotalStalledDueToWriteUnknown :
TotalTransientFailureDuration :
TotalProxyBackoffDuration :
TotalIdleDuration :
MRSServerName :
TotalMailboxSize : 575.3 KB (589,056 bytes)
TotalMailboxItemCount : 122
TotalArchiveSize :
TotalArchiveItemCount :
BytesTransferred :
BytesTransferredPerMinute :
ItemsTransferred :
PercentComplete : 0
CompletedRequestAgeLimit : 7.00:00:00
PositionInQueue : 1/1 (Position/Queue Length)
InternalFlags : SkipFolderPromotedProperties, WordBreak
FailureCode :
FailureType :
FailureSide :
Message :
FailureTimestamp :
IsValid : True
ValidationMessage :
RequestGuid : 1b2dc64c-685d-4a60-be75-6c09efdbd1da
RequestQueue : Mailbox Database 0506035495
Identity : polikomm.local/Users/scom
DiagnosticInfo :
Report :
ObjectState : New
statusDetail "Queued"

Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

Hi,
I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
Configuration server Exchange 2007 SP3 :
Domain : test.com
OS : Windows 2008 server SP2 (not R2)
Firewall : OFF
Exchange roles are on separate three servers : CAS - MAILBOX - HUB.
Configuration Server Exchange 2013 :
Domain : new.com
OS: Windows 2012 R2
Firewall : OFF
This environment is on a closed network unable to reach internet.
I have try to restart the Replication service, but it didn't worked.
I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
Anyone ever had this issue?
Thanks you and have a nice day.

Hi ,
Based on my knowledge below things need to checked.
1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
DataMoveReplicationConstraint : None
Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
3.Restart the Microsoft exchange mailbox replication service and check the results.
4. Have you tried moving the same mailboxes to the different databases.
5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Migrating mailboxes from 2010 to 2013

I have tried to migrate a mailbox between forest from Exchange 2010 to Exchange 2013 but when I run the new-moverequest on Exchange 2013 I get the following error
RemoteLegacy moves must involve Exchange 2010 or lower versions only.
Remote Moverequest dosn't work (The call to ‘https://mail.com/EWS/mrsproxy.svc’ failed. Error details: Could not establish trust relationship for the SSL/TLS secure channel with authority ‘mail.com’. –>
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. –> The remote certificate is invalid according to the validation procedure.)
Can i use RemoteLegacy moves, or only Remote?
Thanks.

When migrating mailboxes from Exchange 2010 to Exchange 2013, a Remote Moverequest must
be used.
Example:
$Cred = Get-Credential (source\account)
New-MoveRequest -Identity [email protected] -Remote
-RemoteHostName mail.sourcedomain.com -RemoteCredential $Cred -TargetDeliveryDomain targetdomain.com
So with the above example, the certificate installed on the source server must include the name mail.sourcedomain.com and target server must trust the certificate.
Martina Miskovic

How many system mailboxes should be in exchange 2013 after moving from exchange 2010?

Hi, I am moving mailboxes from exchange 2010 to exchange 2013, I noticed that in exchange 2013, besides discovery search mailbox, there are other 5 system mailboxes.(especially, there are 2 x Microsoft Exchange system mailboxes) Please see the pic attached.
Does this look right? thanks

Looks perfectly fine - Why MS decided to name two of the five arbitration mailboxes the same (Microsoft Exchange) is unclear but it is what it is :)
In EMS:
Martina Miskovic

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.

Planning a migration from Exchange 2010 to Exchange 2013

Hello,
I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

Hello,
Is there any update?
If
you have any feedback on our support, please click here
Cara Chen
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.

Copy UCC from Exchange 2010 to 2013

I'm starting to setup my Exchange 2013 server. I'm able to migrate users from 2010 and access their mailbox. I'd like to export the UCC SSL cert from 2010 to 2013. The cert if from GoDaddy. Do I need to add the SAN name of the new Exchange 2013 server to
the certificate? If so, how will that affect my 2010 server?
Is the process to export from Exchange 2010 and do an import on the 2013 server? What else am I missing?

Hi,
Do you access the 2013 FE server’s address and log on a Exchange 2010 user? If so, it is a expected behavior, see below:
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
If an Exchange 2013 user log on the Exchange 2013 OWA but he is still redirected to the Exchange 2010 OWA, I suggest we check the redirection setting on the Exchange 2013 ‘s Default
web site and OWA Virtual Directory.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Migrate mailboxes from Exchange 2013 to Exchange 2010

Similar Messages

Maybe you are looking for