[Mikey_AGBoston]

I performed a move of mailboxes in Exchange.
These users experienced replication/sync issues.. forcing us to re-active the devices.

It was almost like the BES said:
Hey wait! You were just on DB01.. but where did you go? Oh wait.. I see you.. but you're on DB03, now?! OK, I see you, but I don't like it... so, I am gonna resent that, and cause your lousy Storm2 to act all jacked-up. deal with it.

Anyone else?
No?
I am gonna call RIM.

[CanuckBB]

Are the stores on different servers? and if so, does BESAdmin ave sufficient tights to all servers?

[wistowg]

Haven't implemented Exch2010 yet but moving a user's mailbox between stores on the same server or to a different server has always required a restart of the BES Controller service hasn't it? Is this any different?

[Mikey_AGBoston]

Spoke to RIM.. Here is my answer/executable

KB00140-How to use the handheldcleanup.exe tool when moving mailboxes in Microsoft Exchange

[TargetIT]

Originally Posted by wistowg

Haven't implemented Exch2010 yet but moving a user's mailbox between stores on the same server or to a different server has always required a restart of the BES Controller service hasn't it? Is this any different?

To the same server yes, to a different server no.

[SteveE]

I've had multiple tickets opened over the last 5 months dealing with mailbox moves in 2010. Basically, unless you do it PERFECTLY, the calendar gets all pissy and you have to delete the user / bes information from their mail system, re-add, and re-activate. RIM support is useless I've found, don't even try. Just don't move mailboxes.