Microsoft KB Archive/260202

= XADM: BlackBerry Pager Software Changes Auto Naming Generation =

Article ID: 260202

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition

-



This article was previously published under Q260202



SYMPTOMS
After you install Research In Motion Limited (RIM) BlackBerry Enterprise Server, a two-way text paging software, on an Exchange Server-based computer, the Auto Naming generation rules (on the Tools menu, click Options, and then click Auto Naming) in the Exchange Administration program are changed and any new recipients are created with the display name and alias name in the wrong format.

For example, the Auto Naming feature for display name generation may have originally been set to &quot;Last, First (Smith, John)&quot; which shows as &quot;%Last, %First&quot; in the &quot;Custom&quot; section. After you install the BlackBerry Enterprise Server, the same generation type, &quot;Last, First (Smith, John), is selected in the Administration program, but the &quot;Custom&quot; section defaults to &quot;%First %Last&quot; for display name, and &quot;%First%1Last&quot; for the alias name. All new recipients use this &quot;custom&quot; format to generate display and alias names.



CAUSE
The Auto Naming generation information is not server-specific. This information is set in a user's Microsoft Windows NT profile, the Ntuser.dat file. The Ntuser.dat file is started as a registry hive called HKEY_CURRENT_USER every time that a user logs on to a Windows NT computer.

After you install the BlackBerry Enterprise Server and you start the Exchange Administration program against a server in the site where BlackBerry Enterprise Server is installed, the following registry values are modified in the user's profile or registry:

HKEY_CURRENT_USER\Software\Microsoft\Exchange

Values:

ANGAutotextFormat

DNGAutotextFormat

The &quot;ANG&quot; acronym stands for Alias Name Generation and the &quot;DNG&quot; acronym stands for Display Name Generation. This change only occurs the first time that you start the Exchange Administration program against the server after you install BlackBerry Enterprise Server. Also, if you start the Administration program against another server in the site other than the server where you installed BlackBerry Enterprise Server, you must replicate the BlackBerry Enterprise Server extensions to the Site\Configuration\Add-Ins container on that server before the problem occurs. The names of these extensions are BBMailboxExt and BBServerExt.



RESOLUTION
To resolve this problem, change the Auto Naming generation feature back to the previous setting. This must be performed on each computer on which you have started the Exchange Administrator program against one of the servers in the site.



WORKAROUND
The owner of this product, RIM, is aware of this issue. For more information about this problem, please contact RIM at the following RIM Web site:

http://www.blackberry.net/

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.



MORE INFORMATION
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

259577 XADM: Exchange Administrator Settings Are Windows NT Profile-Specific

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Keywords: kbprb KB260202

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.