Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XIMS: "Preserve Sender's Display Name" Option Does Not Work in Exchange 2000 Server SP1
Article ID: 303985 - View products that this article applies to.
This article was previously published under Q303985
After you upgrade an Exchange 2000 Server computer to Exchange 2000 Server Service Pack 1 (SP1), the Preserve sender's display name option in the global settings under Internet Message Formats may not work. If you clear the Preserve sender's display name option, the sender's display name is still exposed to the Internet receiver.
This problem can occur because of a regression in Exchange 2000 Server SP1.
A 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. The English version of this fix should have the following file attributes or later:
Component: Information store
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.