Prior to deploying a BB device to a new user after activation we manually configure the BB using the device menus with the following user preferences:

1. Change Theme (desktop) from T-Mobile to Default (List). /Tools/Settings/Theme/Default/Activate
2. Change Messages reconciliation from Mailbox to Mailbox and Handheld
/Messages/Click/Options/E-mail Reconciliation/Delete On/Mailbox and Handheld/Save
3. Adjust Kept Messages /Messages/Click/Options/General Options/Keep Messages/Change to 15 days/Save
4. Verify that Date/Time is set to Eastern (-5) /Settings/Options/DateTime/Eastern Time (-5)
5. Change to size 9 font
/Settings/Options/Screen Keyboard/Font Size/9
/Settings/Options/Screen Keyboard/Font Style/Plain
6. Change Font Style to Plain
/Settings/Options/Screen Keyboard/Font Style/Plain
7. Adjust Backlight Brightness to 100%
/Settings/Options/Screen Keyboard/Backlight Brightness/Change Option/ roll wheel to 100 and then save.
8. Change Browser defaults to Browser
/Settings/Options/Browser/Default browser configuration /Change
Option/Browser/Save then, /Settings/Options/Browser/Default MDS
browser configuration/Change Option/Browser/Save

This takes a while and is subject to error. Is there an easier way to do this???

Is there a way to copy an existing user’s device preferences to the new user’s BES account prior to wirelessly activating it? The only thing different would be the new user’s Exchange e-mail account.

I am having the same issue, but i also need to reorder the icons on the display as well.

I have add a look at the IT policy settings that are available for version 4, but nothing includes this.

One other option i was looking at is if it is possible to recompile the blackberry .cod file which handles user settings or if there is a package file which would configure this stuff using the application loader.

i'm sure there must be a way to do this as i have about 3000 users at present, going up to 6000 and i will be involved in a mass deployment of devices.

I agree. It is hard to believe that RIM did not include this feature in V4.1