Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The message class of a freedoc that is forwarded by a public folder rule changes from IPM.Document to IPM.Note in Exchange Server 2003


View products that this article applies to.

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 (http://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows Registry

↑ Back to the top


Symptoms

When a freedoc is forwarded by a public folder rule from its original public folder to another public folder on your Microsoft Exchange Server 2003 computer, the message class changes from IPM.Document to IPM.Note. For example, you may experience this symptom when the following conditions are true:
  • You drag the freedoc to a public folder in Microsoft Outlook.
  • A public folder rule was previously created to forward all items from that public folder to another public folder.
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.

↑ Back to the top


Resolution

Hotfix information

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: Note 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.

Prerequisites

To install this hotfix, you must be running Exchange Server 2003 Service Pack 1 (SP1). For additional information about how to obtain Exchange Server 2003 Service Pack 1, 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

Restart requirement

You do not have to restart your computer to install this hotfix. However, the Microsoft Exchange Information Store service and the Microsoft Exchange Event service are automatically restarted during the hotfix installation.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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
   --------------------------------------------------------------
   26-Oct-2004  20:05  6.5.7232.46     3,230,720  Mdbmsg.dll       
   08-Oct-2004  02:12                      3,304  Redir.asp
   26-Oct-2004  20:44  6.5.7232.46     5,139,968  Store.exe   

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

After you install the hotfix, you can add a registry entry if you want to revert to the old behavior where the message class of freedocs is changed to IPM.Note when a freedoc is forwarded by a public folder rule to another public folder. To do this, follow these steps:

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.
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersPublic
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type Enable Old Forward Method as the entry name, and then press ENTER.
  5. Right-click Enable Old Forward Method, and then click Modify.
  6. In the Value data box, type a value of 1, and then click OK.
  7. Quit Registry Editor.
For additional information about this same problem in Microsoft Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base:
841443� The message class of a freedoc that is forwarded by a public folder rule changes from IPM.Document to IPM.Note in Exchange 2000 Server

For additional information about Microsoft software updates, 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

↑ Back to the top


Keywords: KB886806, kbbug, kbfix, kbexchange2003presp2fix, kbhotfixserver, kbqfe, kbautohotfix

↑ Back to the top

Article Info
Article ID : 886806
Revision : 6
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 311