Quote:
Originally Posted by knottyrope Moving to a different exchange server can help instead of the same server with a new store. BES 4.1.x will pick up the change usually.
Only other way is not to move them unless you can schedule it during the reboot... |
That is
not correct; see below. Please check your facts before publishing them.
Quote:
Originally Posted by tomo999 ...
We have ~150 Blackberry users and once in a while they are either moved to a new mailbox store in Exchange, or they have their mailbox limit changed (usually increased). Whenever this happens I have to run the "HandheldCleanup -u" command and restart the BES.
We are introducing new service levels against our BES and I was wondering what is the bear minimum I have to do to fix the problems that occur when mailboxes within Exchange are modified in this way? I cannot continue to just reboot the BES during office hours, and users don't want to wait a day for these changes to be implemented! I may be able to get away with a service restart here and there.
Can anyone please advise? |
If you move a user between servers, you only need to perform the handheldcleanup.
If you move a user within a server (different mailbox database) you need to either:
1) Restart the server
2) Temporarily assign that user to a
static mailbox agent
Read:
KB00142 - Cannot send or receive email messages because a mailbox has been moved
Restarts of a server are NOT required when moving users from one store to another. When doing a mass move however it does make things easier.