Microsoft KB Archive/925376
Article ID: 925376
Article Last Modified on 10/25/2007
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition, when used with:
- Microsoft Entourage 2004 for Mac
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
In a Microsoft Exchange Server 2003 organization, a Microsoft Entourage user may receive a meeting request that does not correspond to the meeting time that is specified by the meeting organizer.
Additionally, the user receives the following confusing message:
Additionally, the Entourage user finds that the start time and the end time that are displayed in the opened meeting request differ from the start time and the end time that are displayed in the table view of the calendar.
This problem occurs if the following conditions are true:
- The Microsoft Outlook client computer from which the meeting request originated and the target Entourage client computer are in the same time zone. However, the Exchange Server 2003 computer is in a different time zone.
- The meeting organizer uses Outlook to send a single-instance meeting request to the Entourage user.
This problem occurs because the following sequence of events occurs:
- For single-instance meeting requests, Outlook stamps the time field in the request by using Coordinated Universal Time (UTC). However, Outlook does not include any time zone information.
- When Exchange Server converts the MAPI format to iCal format, Exchange Server stamps the time field by using the local time on the server.
Therefore, when the Entourage client computer receives the meeting request, the time is incorrect.
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
You must install Microsoft Exchange Server 2003 Service Pack 2 (SP2) before you apply this hotfix.
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
You do not have to restart the computer after you apply the hotfix. However, the Microsoft Exchange Information Store Service and all dependent services are stopped and then restarted after you apply the hotfix.
Note You may also have to restart the Microsoft Exchange Information Store Service after you configure the registry entry that is mentioned in the "Hotfix installation information" section.
Hotfix replacement information
This hotfix does not replace any other hotfix.
The global 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 item in Control Panel.
|File name||File version||File size||Date||Time||Platform|
Hotfix installation information
After you apply the hotfix, you must enable the hotfix. After you enable the hotfix, the confusing information is no longer displayed in Entourage.
Note This hotfix permanently removes the following warning message:
Typically, this message is displayed in Entourage when time zones differ. The message was removed to make it easier to implement the hotfix.
To enable the hotfix, configure the following registry subkey on the computer that is running Exchange Server:
To do this, follow these steps.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
- Start Registry Editor.
- Locate and then click the following registry subkey:
- On the Edit menu, click Add Key, type EXCDO, and then press ENTER.
- On the Edit menu, click Add Key, type Parameters, and then press ENTER.
- On the Edit menu, point to New, click DWORD Value, type NoServerTzComp, and then press ENTER.
- Double-click NoServerTzComp, type 1 in the Value data box, click Decimal, and then click OK.
- Exit Registry Editor.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the terminology that Microsoft uses for software that is corrected after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the naming schema for Exchange software updates, click the following article number to view the article in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages
Additional query words: XCCC
Keywords: kbbug kbfix kbinterop kbqfe kbmeetingminder kbpubtypekc kbhotfixserver KB925376