Article ID: 841443
Article Last Modified on 10/25/2007
APPLIES TO
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange 2000 Server Standard Edition
- Microsoft Exchange 2000 Enterprise Server
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
The message class of a freedoc changes from IPM.Document to IPM.Note if the following conditions are true:
- You are using a Microsoft Exchange 2000 Server or Exchange Server 2003 mailbox.
- You drag the freedoc to a public folder in Microsoft Outlook 2000.
- A public folder rule was previously created to forward all items from that public folder to another public folder.
When the public folder rule forwards the freedoc from its original public folder to another public folder, the message class of the freedoc changes from IPM.Document to IPM.Note.
Note A freedoc resides in one of the Exchange folders, but it is not attached to an e-mail message. For example, a Microsoft Office Word document that has been saved directly in the mailbox or in a public folder is a freedoc. Freedocs typically have a message class of IPM.Document.*doc.
RESOLUTION
Exchange Server 2003
Service pack information
To 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:
836993 How to obtain the latest service packs for Exchange Server 2003
Exchange 2000 Server
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3).
Restart requirement
You do not have to restart your computer after you install this hotfix. However, you must restart the Microsoft Exchange Information Store service after you install this hotfix.
Hotfix replacement information
This hotfix does not replace any other software updates.
File information
The 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 -------------------------------------------------------------- 12-Sep-2004 05:02 6.0.6617.6 4,685,824 Store.exe
STATUS
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.
MORE INFORMATION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
You can add a registry entry to revert to the old behavior where the message class of freedocs is changed to IPM.Note. To do this, follow these steps:
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersPublic\ - On the Edit menu, point to New, and then click DWORD Value.
- Type Enable Old Forward Method, and then press ENTER.
- Double-click Enable Old Forward Method.
- Type 1 in the Value box, click Decimal, and then click OK.
- Quit Registry Editor.
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
817903 New naming schema for Exchange Server software update packages
Additional query words: xadm
Keywords: kbqfe kbhotfixserver kbfix kbexchange2000presp4fix kbbug KB841443
