How to enable message prepopulation for all BlackBerry smartphone users on a BlackBerry Enterprise Server

Article ID: KB04713

Type: Support Content

Last Modified: 07-25-2012

 

Product(s) Affected:

  • BlackBerry Enterprise Server 5
CollapseEnvironment
  • BlackBerry® Enterprise Server 4.0 SP3 MR2 to 5.0 SP3
CollapseOverview

In versions earlier than BlackBerry® Enterprise Server 4.0 SP3 MR2, email message prepopulation only occurred if the personal identification number (PIN) associated with a BlackBerry® smartphone was changed, for example when a BlackBerry® smartphone user switched to a different BlackBerry smartphone. In all versions since, the email message prepopulation feature also resends existing email messages after all data and applications are erased from the BlackBerry smartphone if the BlackBerry smartphone user's PIN is cleared or they are removed and re-added to the BlackBerry Enterprise Server.

By utilizing the following registry change, it is possible to force email message prepopulation for all BlackBerry smartphone users, even if they have are already activated on the BlackBerry® Enterprise Server and their associated device PIN has not changed. In effect, if this change is implemented, it will not be necessary to remove and re-add a BlackBerry® smartphone user in order to initiate email prepopulation.

Note: This change only comes into effect for wireless activations. A wired activation via BlackBerry® Desktop Software, BlackBerry® Web Desktop Manager, the BlackBerry® Manager, or the BlackBerry® Administration Service will be unaffected by the change. This change will come into effect after the folowing components restart for all future wireless activation attempts:

  • BlackBerry® Controller Service for BlackBerry® Microsoft® Exchange®
  • BlackBerry® Messaging Agent for BlackBerry® Enterprise Server for IBM® Lotus® Domino®

Warning: The following procedure involves modifying the computer registry. This can cause substantial damage to the Windows® operating system. Document and back up the registry entries prior to implementing any changes.

  1. On the BlackBerry Enterprise Server, click Start > Run and type regedit.
  2. For a 32-bit Windows Server®, go to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server
    For a 64-bit Windows Server®, go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Research In Motion\BlackBerry Enterprise Server
  3. Right-click the Agents registry key, then click New > DWORD Value.
  4. Type ForceMsgPrepopOnActivation as the new DWORD Value name.
  5. Double-click ForceMsgPrepopOnActivation.
  6. In the Value data field, type 1, then click OK.

Note: Steps 7-16 only apply to BlackBerry Enterprise Server for Microsoft Exchange.

  1. Right-click the Agents registry key, then select New > DWORD Value.
  2. Type ForceMsgPrepopDays as the new DWORD Value name.
  3. Double-click ForceMsgPrepopDays.
  4. In the Value data field, select Decimal and enter a value of 14, then click OK.
  5. Right-click the Agents registry key, then select New > DWORD Value.
  6. Type ForceMsgPrepopMessages as the new DWORD Value name.
  7. Double-click ForceMsgPrepopMessages.
  8. In the Value data field, select Decimal and enter a value of 750, then click OK.
  9. Close the Registry Editor.
  10. Restart the BlackBerry Controller Service.

Important: Restarting the BlackBerry® Enterprise Server or its services may delay message delivery to BlackBerry smartphones.

Note: BlackBerry® Enterprise Server for IBM® Lotus® Domino® doesn't read the registry keys ForceMsgPrepopDays and ForceMsgPrepopMessages but uses values set with BlackBerry Manager or BlackBerry Administration Service and saved in an SQL database.

CollapseAdditional Information

For BlackBerry Enterprise Server 5.0 SP2 and SP3 for Microsoft Exchange and BlackBerry Enterprise Server 5.0 SP2 and SP3 for IBM Lotus Domino, the message prepopulation settings can now be increased to a maximum of 30 days for prepopulation by message age, and 3000 messages for prepopulation by message count.

If ForceMsgPrepopDays and/or ForceMsgPrepopMessages are set in a BlackBerry Enterprise Server 5.0 environment, the values defined in the BlackBerry Administration Service will take precedence over any values defined in registry keys, however the implementation of ForceMsgPrepopOnActivation will still require the additional keys. To check the values in the BlackBerry Administration Service:

  1. Log in to the BlackBerry Administration Service.
  2. In the Servers and Components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > Email.
  3. Click on the email instance.
  4. Select the Messaging tab.
  5. Verify that the values of Prepopulation by message count and Prepopulation by message age reflect the desired values.

To confirm the proper implementation of the keys, the following configuration lines can be seen in the messaging agent log on startup following the reboot of the BlackBerry Controller, wherein the “*” represents the values implemented in the registry keys:

[40000] (00/00 00:00:00.000):{0x0000} [CFG] Registry Settings: ForceMsgPrepopOnActivation is xxxx
[40000] (00/00 00:00:00.000):{0x0000} [CFG] Registry Settings: ForceMsgPrepopDays is xxxx
[40000] (00/00 00:00:00.000):{0x0000} [CFG] Registry Settings: ForceMsgPrepopMessages is xxxx

Where xxxx contains value of True/False (default)

NOTE : The log lines mentioned above are applicable to BlackBerry Enterprise Server for Microsoft Exchange only.

 

Disclaimer

By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.


Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.