05-28-2009 10:45 AM
I know with the current version of BES (4.1.6MR5), when you move an exchange user from one exchange server to another you essentially have to restart BES services which causes and effects all your BES users because it then needs to rescan all of the exchange mailboxes. Is or has this issue been resolved in BES 5.0?
For any exchange admin with multiple exchange servers you're moving users around all the time, and this is a real pain.
05-31-2009 11:05 PM
Best Practices for
Managing Your BlackBerry Environment
Run the HandheldCleanup.exe Tool
For Exchange, one of the command line utilities built in to the BlackBerry Enterprise Server is the
HandheldCleanup.exe tool. This tool should be used if users are moved from mail server to mail
server and any changes are made on that account. Running the HandheldCleanup.exe tool can
ensure that the information coincides with the information used by the BlackBerry Enterprise
Information about the specific options that can be used is documented in both the BlackBerry
Enterprise Server Administration Guide and the BlackBerry Enterprise Server Maintenance
The following command dumps the device information for each BlackBerry device on a specified
BlackBerry Enterprise Server:
-d [<filename>] [-p <MAPI profile name>]
Executing the above command causes the prompt for a BlackBerry Enterprise Server name to
appear. This command can be used with the following optional arguments:• <filename> is a file name to which device information will be dumped. If a file name is not
specified, the information is dumped to the screen.
• -p is a flag to signify a profile; it is combined with <MAPI profile name>.• <MAPI profile name> is an existing MAPI profile name.
Use the following command to perform a BlackBerry device mailbox check and update and check
for any mailboxes that have been moved.
-u [-p <MAPI profile name>]
If the mailbox is moved, the ServerDN is set to the Global Address List ServerDN. Any devices
with the ServerDN changed are printed. Otherwise, no output is given.
This command can be used with the following optional arguments:
• -p is a flag to signify a profile; it is combined with <MAPI profile name>.
• <MAPI profile name> is an existing MAPI profile name.• -c “DB Connect String” signifies the ODBC connection string for the database. If the
connection string is not provided, the connection string is retrieved from the registry.
• -h or -? lists all available commands.
06-02-2009 12:40 AM
Also this doesn't work if you move a mailbox from 1 mail store to another.
NOTE: In both cases the move will eventually be picked up by the BES.
06-10-2009 11:38 AM
I'm not sure that the key question was answered- has this been resolved with Bes5.0? By resolved, services are no longer required to be restarted?
Services HAVE NEVER needed to be restarted when moving a user. Review my post previous to yours. It is relevant for 5.0
06-12-2009 08:49 AM
Everything in those KB articles seem to be "workarounds." Why when moving a user in exchange from 1 mail store to another does the BES admin have to do anything?
With Active Sync I can move users where ever I want, and it's free.
06-12-2009 10:34 AM
06-15-2009 02:36 AM - edited 06-15-2009 03:07 AM
Sorry, but I'm a little confused....
Assuming that the issue is NOT fixed in BES 5.0 (I havent looked yet)...
To fix a user who has been moved between excange servers/stores/etc then you need to get the BES to reconnect to the users account.
Restart BES = 20- minutes affecting all users
Delete the current user and reactivate = 20 minsutes and affects only one user...
Yes, when moving users around mail servers, the BES is Seriously affected. But why move users around all the time? Once they are added and working, why move them? If storage is an issue then either enforce Mail quota's or add extar Hard drive storage to handle larger mail stores....
Can you give examples of why users NEED to be moved around exchange servers all the time?