[execbaynes]

Hi all,

I'm here to pick your brains a user of mine is having some issues with his account, it appears his Exchange Mailbox is at fault and needs to trashed/recreated etc as the MAGT Logs are stating that his account is 'Still handled by desktop’ (redirector I presume), as short term solution I have activated his device via Desktop Manager as opposed to Wirelessly but this isn't the solution, we have run DBClean, deleting/reading his BES account several times to no avail, have even moved him onto another Exchange Server (clutching at straws) as this would have minimal impact on his day to day workings as opposed to completely trashing his Exchange Mailbox, this work however is planned for next week out of hours ..

I digress my original query is basically since activating his device via Desktop Manager only the mail items from that point in time onwards are being synced but nothing before, the user is out of the country and therefore unable I'm to to try anything from the device/DM is there anyway his pre activation mail items be force populated to his device from BES?

Sorry to ramble on but all advice would be appreciated

Regards

Chris

[Jadey]

To get pre-population on an EXISTING, RUNNING account on BES, you need to activate the user with a different device for a different PIN.

If a user is on BES with a PIN assigned to them, and you wipe and reactivate that device, you will ~NOT~ get message pre-pop.

Your two options are:

a) Activate the user on a spare device, then wipe "his" device and reactivate on that. Effectively then, you are swapping from original PIN on BES to spare PIN and then back to original PIN, and will get message pre-pop on device.
Advantages: Easy to do, pre-pop will work
Disadvantages: Need a spare device (you can use user SIM) and takes a bit of time for 2 activations to complete

b) Delete the user from BES, re-add, activate on original device. By removing and re-adding , you break the BES link between user and PIN, and pre-pop will work.
Advantages: You only need one device. You get to clear out any duff user history on BES.
Disadvantages: You lose any useful backed up data (bookmarks, custom words, font preferences etc etc). You need to repopulate any account info that had been added (signatures, PIM synch mappings) and/or reapply policies, software configs to essentially a "new" account on BES (how much time this will take depends on config).

[freakinvibe]

There is a registry hack to force pre-population:

Procedure:

1. In the Registry Editor, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents\.
2. Create a new DWORD value named ForceMsgPrepopOnActivation.
3. Set the value to 1 to turn this on.

[execbaynes]

Originally Posted by Jadey

To get pre-population on an EXISTING, RUNNING account on BES, you need to activate the user with a different device for a different PIN.

If a user is on BES with a PIN assigned to them, and you wipe and reactivate that device, you will ~NOT~ get message pre-pop.

Your two options are:

a) Activate the user on a spare device, then wipe "his" device and reactivate on that. Effectively then, you are swapping from original PIN on BES to spare PIN and then back to original PIN, and will get message pre-pop on device.
Advantages: Easy to do, pre-pop will work
Disadvantages: Need a spare device (you can use user SIM) and takes a bit of time for 2 activations to complete

b) Delete the user from BES, re-add, activate on original device. By removing and re-adding , you break the BES link between user and PIN, and pre-pop will work.
Advantages: You only need one device. You get to clear out any duff user history on BES.
Disadvantages: You lose any useful backed up data (bookmarks, custom words, font preferences etc etc). You need to repopulate any account info that had been added (signatures, PIM synch mappings) and/or reapply policies, software configs to essentially a "new" account on BES (how much time this will take depends on config).

Nice one thanks, will keep this in mind for future reference but it doesn't however help me at the moment LOL

Originally Posted by freakinvibe

There is a registry hack to force pre-population:

Procedure:

1. In the Registry Editor, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents\.
2. Create a new DWORD value named ForceMsgPrepopOnActivation.
3. Set the value to 1 to turn this on.

Excuse my ignorance but will these entries need to be amended on the BES Server or the Workstation where the DM Activation was carried out?

Thanks again

C

[Jadey]

On the server. Pre-pop is controlled by BES. Does not matter if wired or wireless activation, pre-pop is determined by BES server.

[execbaynes]

Originally Posted by Jadey

On the server. Pre-pop is controlled by BES. Does not matter if wired or wireless activation, pre-pop is determined by BES server.

Thanks, if this change is made now will this pre-pop all our users mail, circa 450 of them?

[Jadey]

No. Not unless you are planning on wiping and reactivating their BBs.

Message pre-pop refers to devices undergoing the process of being activated. It will do NOTHING to activated, running devices.

[execbaynes]

Originally Posted by Jadey

No. Not unless you are planning on wiping and reactivating their BBs.

Message pre-pop refers to devices undergoing the process of being activated. It will do NOTHING to activated, running devices.

Boooo! OK thanks for your help

[Jadey]

Originally Posted by execbaynes

Boooo! OK thanks for your help

LOL, sorry - am curious. Why Boooo? Why would you want to push a batch of messages to devices that have been running for X months?

[execbaynes]

Originally Posted by Jadey

LOL, sorry - am curious. Why Boooo? Why would you want to push a batch of messages to devices that have been running for X months?

I dont, just to one ..