Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You cannot use the Active Directory Users and Computers snap-in to generate an e-mail proxy address when the e-mail proxy address contains parentheses in Exchange 2000 or in Exchange 2003
Article ID: 888614 - View products that this article applies to.
In a Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 environment, you cannot use the Active Directory Users and Computers snap-in to generate an e-mail proxy address to include in messages for IBM Lotus Notes recipients when the e-mail proxy address contains parentheses.
Exchange Server 2003
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/836993/ )How to obtain the latest service packs for Exchange Server 2003
Exchange 2000 Server
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesThis hotfix requires Microsoft Exchange 2000 Server Service Pack 3 and update rollup 870540. For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301378/ )How to obtain the latest Exchange 2000 Server service pack
(http://support.microsoft.com/kb/870540/ )Availability of the August 2004 Exchange 2000 Server post-Service Pack 3 update rollup
Restart requirementYou do not have to restart your computer after you apply this hotfix. However, the Microsoft Exchange System Attendant service and all dependent services will be restarted.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------------- 19-Nov-2004 22:30 6.0.6617.24 53,248 Ntspxgen.dll
After you install the hotfixThis hotfix introduces the NonDefaultAllowedCharacters registry entry and the NonDefaultDisallowedCharacters registry entry. You can use these registry entries to add or to remove characters that are not in the default set of characters. After you apply this hotfix on your Exchange 2000 computer, the default set of characters that is enabled for proxy addresses does not change. To add or to remove characters that are not in the default set of characters, you must add the correct registry entry.
For example, to add parentheses to the set of characters that you can use in proxy addresses, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft Exchange Server 2003 Service Pack 2.
Article ID: 888614 - Last Review: October 25, 2007 - Revision: 3.3