Exchange 2010 MoveRequests


So I have done a couple of thousand mailbox moves from Exchange 2003 to Exchange 2010 and have really only found 3 issues, and I wanted to share them with you:

1) In the move log you see something like this:

Error context: ——–
Operation: IDestinationFolder.SetRules
OperationSide: Target
Primary (09ed3203-2965-4649-ad94-fab619e13be1)
Rules: [Rule: Condition: none; Actions: [RuleAction: OOFREPLY TemplateEID:[len=70, data=000000002EA2198C566FD911A2D40011855C8526070024006E7025D91E4A83E66611594894CA0000004D7DE300002DD26E7025D91E4A83E66611594894CA0000004D81590000], TemplateGuid:43b6af84-1a85-45fd-a34f-63494eb33279, Flags:0]; Name ”; Provider: ‘MSFT:TDX OOF Rules’; ProviderData: ; ExecutionSequence: 50; Level: 0; StateFlags: 13; UserFlags: 2; IsExtended: False]

The fix is to remove any OOF messages. I found that some users “copied” other whole mailboxes in to there own! .. So with an Exchange 2003 account, apply full mailbox permissions for the mailbox. Using MDBvu32 locate any OOF message in mailbox folders and remove them.

Resume the move request

2) Mailbox move stays at 10% and doesn’t actually start.

Check the user accounts permissions and make sure Inherited permissions is checked



3) this is my latest one, in the move logs you see:

3/9/2012 1:29:23 AM [XHC02] Initializing folder hierarchy in mailbox ‘Primary (aafab1eb-46e8-4818-9611-90e0ea7aacce)’: 31 folders total.
3/9/2012 1:29:24 AM [XHC02] Fatal error MapiExceptionNoSupport has occurred.
Error details: MapiExceptionNoSupport: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80040102, ec=-2147221246)
Diagnostic context:
Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=636]
Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=525][latency=15]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstCopyConfig [83]
Lid: 27962 ROP: ropTellVersion [134]
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 17082 ROP Error: 0x80040102
Lid: 31329
Lid: 21921 StoreEc: 0x80040102
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 —- Remote Context Beg —-
Lid: 1238 Remote Context Overflow
Lid: 39287
Lid: 17916 StoreEc: 0x80040102
Lid: 32252 StoreEc: 0x80040102
Lid: 7915 StoreEc: 0x80040102
Lid: 20320
Lid: 4559 StoreEc: 0x80040102
Lid: 21802
Lid: 19994 StoreEc: 0x80040102
Lid: 20202
Lid: 3305 StoreEc: 0x80040102
Lid: 32762 dwParam: 0xE080003
Lid: 32762 dwParam: 0xE230003
Lid: 32762 dwParam: 0xE270102
Lid: 32762 dwParam: 0xE590102
Lid: 32762 dwParam: 0xFF40003
Lid: 32762 dwParam: 0x10F4000B
Lid: 32762 dwParam: 0x10F5000B
Lid: 32762 dwParam: 0x10F6000B
Lid: 32762 dwParam: 0x300184B0
Lid: 32762 dwParam: 0x300484B0
Lid: 32762 dwParam: 0x3FE4000B
Lid: 32762 dwParam: 0x3FFE0102
Lid: 32762 dwParam: 0x3FE5000B
Lid: 32762 dwParam: 0x36170003
Lid: 32762 dwParam: 0x3FD60040
Lid: 32762 dwParam: 0x3FE00102
Lid: 26346
Lid: 4073 StoreEc: 0x80040102
Lid: 28570 StoreEc: 0x80040102
Lid: 29738
Lid: 3401 StoreEc: 0x80040102
Lid: 1750 —- Remote Context End —-
Lid: 26849
Lid: 21817 ROP Failure: 0x80040102
Lid: 22630
at Microsoft.Exchange.MailboxReplicationService.AsynchronousTransmitter.WaitUntilDataIsProcessed()
at Microsoft.Exchange.MailboxReplicationService.AsynchronousTransmitter.Microsoft.Exchange.MailboxReplicationService.IDataImport.ImportBuffer(Int32 opcode, Byte[] data)
at Microsoft.Exchange.MailboxReplicationService.AsynchronousTransmitter.Microsoft.Exchange.MailboxReplicationService.IDataImport.Flush()
at Microsoft.Exchange.MailboxReplicationService.ProgressTrackerTransmitter.Microsoft.Exchange.MailboxReplicationService.IDataImport.Flush()
at Microsoft.Exchange.MailboxReplicationService.FxProxyTransmitter.Microsoft.Exchange.MailboxReplicationService.IFxProxy.Flush()
at Microsoft.Exchange.MailboxReplicationService.LocalSourceFolder.Microsoft.Exchange.MailboxReplicationService.ISourceFolder.CopyTo(IFxProxy destFolderProxy, PropTag[] excludeTags)
at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.<>c__DisplayClass1.<Microsoft.Exchange.MailboxReplicationService.ISourceFolder.CopyTo>b__0()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceFolder.CopyTo(IFxProxy destFolder, PropTag[] excludeTags)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.CopyFolderProperties(FolderRecWrapper folderRec, ISourceFolder sourceFolder, IDestinationFolder destFolder, FolderRecDataFlags dataToCopy)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass34.<>c__DisplayClass38.<CreateFolderHierarchy>b__31()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass34.<CreateFolderHierarchy>b__30(FolderRecWrapper folderRec, EnumFolderContext context)
at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<CreateFolderHierarchy>b__2d(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CreateFolderHierarchy(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: ——–
Operation: IMapiFxProxy.ProcessRequest
OpCode: TransferBuffer
DataLength: 570

Account failed.

Check out and

Turns out it’s a bug and is fixed with

This will have to wait until I install SP2 RU1 in to pre prod and try to move again

Hope this helped

#BlackBerry March 2012 Daylight Savings Time Information

the March 2012 Daylight Savings Time Update will be made public shortly. It includes the following updates:

New Time Zones:



Time Zone

DST Start



Kaliningrad (GMT +3)*

No Daylight Savings Time

Novosibirsk (GMT +7)*


Apia (GMT +13)

Saturday, September 29 at 3:00AM

Sunday, April 1 at 4:00AM

Updated Time Zones:



Time Zone

DST Start




Friday, March 30, 2012 at 2:00AM

Sunday, September 23, 2012 at 2:00AM



Midnight between Saturday, September 1 and Sunday, September 2, 2012

Midnight between Saturday, April 28 and Sunday, April 29, 2012


Amman (GMT +2)

Midnight between Thursday, March 29 and Friday, March 30, 2012 local standard time

Friday, October 26, 2012 at 1:00 AM


Tehran (GMT +3:30)

Midnight between Tuesday, March 20 and Wednesday, March 21, 2012

Midnight between Thursday, September 20 and Friday, September 21, 2012


Ciuaba (GMT -4)*

Midnight between Saturday, October 20 and Sunday, October 21, 2012

Midnight between Saturday, February 25 and Sunday, Feburary 26, 2012


Fiji (GMT +12)*

Sunday, October 21, 2012 at 2:00AM

Sunday, January 22, 2012 at 3:00AM


Minsk (GMT +3)

DST has been removed and the GMT offset has been set to +3



DST has been removed

Note: Ciuaba (GMT -4) has been renamed from Manaus (GMT -4)

#BlackBerry Enterprise Transporter helps make user migration a breeze

Interesting read if you didn’t know

The new BlackBerry® Enterprise Transporter is designed to make BlackBerry smartphone user migration easier, and is an integral part of BlackBerry® Enterprise Server software version 5.0. This article tells you more about the benefits of the BlackBerry Enterprise Transporter and how this enhanced migration tool works.

As your organization grows, BlackBerry smartphone users may be spread across multiple locations. In turn, administration can become a little more challenging. The BlackBerry Enterprise Transporter may help by allowing you to transfer multiple BlackBerry smartphone user accounts from one BlackBerry® Domain to another with little to no impact on, or action required by, your BlackBerry smartphone users – all through one, centralized console.

When to use it

The BlackBerry Enterprise Transporter is designed to allow organizations to migrate BlackBerry smartphone users to the new BlackBerry Enterprise Server v5.0, rather than updating their live environment. This user migration tool can be accessed using either Windows® Explorer or the command prompt window.

You will find the BlackBerry Enterprise Transporter useful when you are migrating BlackBerry smartphone users from:

1 An earlier BlackBerry Enterprise Server software version to BlackBerry Enterprise Server v5.0

2 A production BlackBerry Domain to a test domain and then back again

3 A BlackBerry Enterprise Server v4.x to an empty BlackBerry Enterprise Server v4.x with a new BlackBerry Configuration Database.

Note: The BlackBerry Enterprise Transporter is not recommended for moving BlackBerry smartphone users from a production instance of BlackBerry Enterprise Server v4.x to another production instance of BlackBerry Enterprise Server v4.x Note: Before running the BlackBerry Enterprise Transporter, you must install the BlackBerry User Administration Service.

Using the BlackBerry Enterprise Transporter

There are two methods of migration using the BlackBerry Enterprise Transporter: Live Mode and Bulk Mode. Live Mode is designed to allow you to move BlackBerry smartphone users between two active BlackBerry Enterprise Server instances. Bulk Mode requires the source BlackBerry Enterprise Server instance to be shut down. Generally, administrators prefer to use Live Mode so that they can try to minimize downtime for their BlackBerry smartphone users.

The following steps describe using the Live Mode migration method – the more commonly used method to move one or more BlackBerry smartphone users from an instance of BlackBerry Enterprise Server v4.1.x to a separate BlackBerry Enterprise Server v5.0 instance.

Moving BlackBerry smartphone users to a separate BlackBerry Enterprise Server v5.0

1) Find the UserMigrationTool.exe From the command prompt window, navigate to UserMigrationTool.exe or double-click the UserMigrationTool.exe file to open the BlackBerry Enterprise Transporter.

2) Create a manifest file Under the Configuration tab click the "New" button to create a manifest file. (You can also create your own manifest file using an XML editor)

3) Save the manifest file Click "Save" after you select the name for your manifest file. The manifest file contains information about the BlackBerry Domain instances, default settings, and email addresses that the BlackBerry Enterprise Transporter requires to run the migration process.

4) Configure source database and test connection In the BlackBerry Enterprise Transporter, under the Configuration tab, click "Configuration" under Source Domain. The information you enter here is added to the manifest file created earlier. Click "Test Connection" to validate the connection with the Microsoft® SQL Server® you entered, and then click "Ok".

5) Configure destination database In the BlackBerry Enterprise Transporter, under the Configuration tab, click "Configuration" under Destination Domain. The information you enter here is added to the manifest file created earlier. Click "Test Connection" to validate the connection with the Microsoft SQL Server you entered, and then click "Ok".

6) Configure User Manifest In the BlackBerry Enterprise Transporter, under the Configuration tab, click "Details". Select the destination BlackBerry Enterprise Server name, group name, IT policy, and software configuration. Once you have selected all your options, click the "Find Users" button.

7) Options for Finding BlackBerry smartphone users Select one of three options to search for the BlackBerry smartphone users you want to migrate. Search for BlackBerry smartphone users at the BlackBerry Domain, BlackBerry Enterprise Server, or Enterprise group level. Select the search option you want to use, click "Find". BlackBerry smartphone users are listed under the Users list. Select the BlackBerry smartphone users you want to add, and click the "Add" button. The BlackBerry smartphone users you select appear in the Select Users column. Click "Done" when you have selected all of the BlackBerry smartphone users.

8) View the BlackBerry smartphone users you’ve selected The BlackBerry smartphone users you selected are listed in the User Manifest Configuration screen. Click "Done".

9) View migration information Click the Preview button to view your migration information so far. When a migration preview is successful, you will see a green check mark. If a migration preview fails, you will see a red X.

10) Almost Done! Begin migrating BlackBerry smartphone users Click "Migrate". The Console tab shows you a step-by-step log file that details what the BlackBerry Enterprise Transporter is doing. This information is also written to the log file that is created in the same location as the UserMigrationTool.exe.

There are three configuration options available:

• Turbo Mode – Skips confirmation of IT administration commands

• Trigger Slow Synchronization (SlowSync) – Starts the wireless synchronization of organizer data when the migration process is complete

• Ignore Warnings – Skips validation warnings

11) You’re done! When the migration is complete, you will see a Migration window and a confirmation message.