Microsoft KB Archive/931667

= How to address time zone changes by using the Time Zone Data Update Tool for Microsoft Office Outlook =

Article ID: 931667

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Office Outlook 2007
 * Microsoft Office Outlook 2003
 * Microsoft Outlook 2002 Standard Edition
 * Microsoft Outlook 2000 Standard Edition

-



Important This article contains information about how to modify the registry. Make sure that you 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



Notice
If you use Microsoft Office Outlook as part of a corporate messaging environment, check with the IT administration before you run any tools or apply any updates to the computer.



INTRODUCTION
Daylight saving time (DST) is a system of setting clocks ahead so that both sunrise and sunset occur at a later hour. The effect is additional daylight in the evening. Many countries observe DST, although most have their own rules and regulations for when it begins and ends. The dates of DST may change from year to year, and users have to update their Microsoft Office Outlook calendar every time that DST law or rules change. The dates between the previous time zone rules and the current time zone rules are referred to in this article as the &quot;extended DST period.&quot;

This article focuses on the actions that you can take to address calendar items in Microsoft Outlook that occur during the extended DST period. For more information about how to prepare for changes in daylight saving time for all affected Microsoft products, visit the following Microsoft Web site:

http://support.microsoft.com/gp/cp_dst



Glossary of terms
Be aware of the differences among the following Outlook items that are discussed in this article:
 * Appointment: A calendar item that users create for themselves and that has no attendees other than the organizer.
 * Meeting: A calendar item for which there are attendees in addition to the organizer.
 * Calendar item: An item on the user’s calendar. This can be an appointment or a meeting.

What you should do
If you updated the operating system, ran the Outlook Time Zone Data Update Tool, and followed the instructions for the initial extended DST time frame, no action is required for future extended DST time frames.

However, if you have not previously run the Outlook Time Zone Data Update Tool, or if you previously manually updated your calendar items for time zone changes, the content of this article is still applicable. You should review and then implement the information in this article as needed. For users in a Microsoft Exchange environment, you should contact the Exchange administrator because the tool may have been run at the server level. If this is true, no action is necessary. We recommend checking your individual calendar and any calendars for which you are responsible during the applicable extended DST period.

If users are in the Jerusalem, Central Brazilian, or E. South American time zone, click the following article number to view the article in the Microsoft Knowledge Base:

943390 Some Outlook calendar items are rebased incorrectly when you use the Outlook Time Zone Data Update Tool to adjust for daylight saving time changes in certain time zones

Microsoft Outlook
In August 2007, the Time Zone Data Update Tool for Microsoft® Office Outlook® (Time Zone Data Update Tool or &quot;Outlook tool&quot;) became available from Microsoft Download Center. The Time Zone Data Update Tool can update calendar items in Outlook to accommodate the time zone changes during the extended DST period. If you have earlier versions of the tool, please remove those from the system and install the newest release.

The Time Zone Data Update Tool is required to update calendar items that occur during the extended DST periods for the following versions of Microsoft Outlook:
 * Microsoft Office Outlook 2007
 * Microsoft Office Outlook 2003
 * Microsoft Outlook 2002
 * Microsoft Outlook 2000

Microsoft Office Outlook 2007 can automatically detect the time zone change and prompt the process that updates a person’s calendar to comply with the new daylight saving time rules. However, the Time Zone Data Update Tool contains enhancements that improve what is available in Outlook 2007 and should be run instead of the out-of-the-box Outlook 2007 experience.

The following table describes the situations in which you should download and run the Time Zone Data Update Tool.

Note You do not have to run both the Outlook and Exchange Server versions of the Time Zone Data Update Tool. We encourage you to read all the documentation about each tool and then determine which tool will best suit your specific environment and needs.

Tools that you can use to update DST in calendaring applications
The following file is available for download from the Microsoft Download Center:

Download the Time Zone Data Update Tool package now.

Note The Time Zone Data Update Tool must be downloaded from the Microsoft Download Center and then run by the user. The Time Zone Data Update Tool will enable users to update their calendars to accommodate the change in time zone rules. The Time Zone Data Update Tool will not be distributed through Microsoft Update or through Windows Update.

Release Date: August 31, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

The English version of this tool 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.

When you run the Time Zone Data Update Tool without using any command-line switches, the following Outlook items that occur during the extended DST period are updated:
 * Meetings for which the user is the organizer and which reside in the user’s default calendar

Note The tool then automatically sends updates for those meetings to all other attendees.
 * Single-instance and recurring appointments created in his or her default calendar
 * Reminders on mail, task, and calendar items

Another version of the Time Zone Data Update Tool is available for servers that are running Exchange Server. Administrators can run the server-side tool to automatically update specific client mailboxes. Individual user interaction will not be required.

For more information about the Exchange updates and the Exchange Calendar Update Tool, click the following article number to view the article in the Microsoft Knowledge Base:

941018 How to address daylight saving time by using the Exchange Calendar Update Tool

Additionally, administrators must address Collaboration Data Objects (CDO) that are used by Microsoft Exchange. CDO has its own internal table of time zone definitions that is independent of the local computer definition of a time zone. The CDO update changes the CDO binaries to contain the correct time zone information. For more information about the tools and resources that are available to update Microsoft Exchange for DST, visit the following Microsoft Web site:

http://www.microsoft.com/DST2007

Summary of the key changes in the Time Zone Data Update Tool 2.0 for Outlook
The Time Zone Data Updated Tool 2.0 for Outlook includes the following changes:
 * All the hotfixes that were made to the Time Zone Data Update Tool 1.0.2.
 * Key fixes, most notably those that allow for accurate updates in New Zealand and in Western Australia.

Important Note The behavior of the previously released tool is incorrect in various ways when the tool is used for New Zealand and Western Australia. Any use of this version of the tool for these specific regions is not supported by Microsoft.


 * A streamlined user interface that does not confuse the end-user with options that are related to physical moves between time zones. Physical time zone moves now have to be performed by using the /PHYSICALMOVE command line option.

General sequence of update actions
Many calendaring environments have an interconnected system of programs. Therefore, each program must be adjusted to accommodate the new time zone rules. To update the computer for the extended DST period, follow these steps based on the appropriate environment:  Apply updates to Windows operating systems on Windows Servers. For more information about how to update the operating system, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

 Apply updates to Windows operating systems on individual workstations, and apply Windows Mobile updates to all mail-enabled mobile clients. For more information about how to update the operating system, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

941898 An August 2007 daylight saving time update for Windows Mobile-based devices is available

 The IT administrator can use one of the following methods:  Run the Exchange Calendar Update Tool against all affected users, servers, or both. Push out the Outlook Time Zone Data Update Tool to the clients and let the users update their own mailboxes. Run the Exchange Calendar Update Tool against all affected users, servers, or both. However, only modify recurring appointments. Then, ask users to rebook single instance appointments that fall into the extended DST period, or ask them to run the Outlook Time Zone Data Update Tool.</li> Run neither the Exchange Calendar Update Tool nor the Outlook Time Zone Data Update Tool. Ask users to examine their calendars and rebook as necessary.</li></ul>

We strongly advise IT administrators to refer to the Exchange Calendar Update Tool and to consider all potential effects on your IT environments and on your user base before you run the Exchange Calendar Update Tool.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

941018 How to address daylight saving time by using the Exchange Calendar Update Tool

</li> Apply the appropriate Exchange Server DST updates.

The following list is organized by Exchange Server version and service pack level. Install the updates for your version of Exchange in order.

Exchange 2007

940006 Description of Update Rollup 4 for Exchange 2007

Update rollup 940006 includes the following DST fixes: <ul> 

937656 You experience problems in Outlook Web Access for Exchange 2007 after daylight saving time (DST) starts in New Zealand in 2007

</li> 

932561 Appointments that are sent from one Exchange organization to another by using Exchange 2007 may be incorrect by one hour if one organization is in the Western Australia time zone

</li></ul>

Exchange 2003 SP2

926666 Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 2

931915 Update for daylight saving time changes in Newfoundland in 2007 for Exchange Server 2003 Service Pack 2

929895 Appointments that are sent between different Exchange Server organizations may be incorrect by one hour when one of the organizations is in the Western Australia time zone

937653 You experience one or more issues in Exchange Server 2003 after the daylight saving time period for New Zealand changes in 2007

Exchange 2003 SP1

940123 You experience problems in Exchange 2003 Service Pack 1 after daylight saving time (DST) starts in New Zealand in 2007

Note If you run the Outlook tool or the Exchange tool on a client computer that is running Windows Vista, and you run the tool against mailboxes where the home time zone is New Zealand Standard Time, you must run the tool a second time on or after January 1, 2008. For more information, see the Known issues and limitations section.</li></ol>

For small business, home, or consumer computer users who run Windows and Outlook but not Exchange Server
<ol> Apply updates to Windows operating systems on individual computers. For more information about how to update the operating system, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

</li> Download and run the Time Zone Data Update Tool from the Microsoft Download Center. To do this, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568

</li></ol>

Differences between the Outlook tool and the Exchange tool
The server-side tool is merely a wrapper around the client-side tool. Therefore, the server-side tool provides no semantics that are not also exposed by the client-side tool for the actual job of updating a user’s calendar. In short, any calendar or reminder update that can be made through the Exchange tool can be made exactly as in the Outlook tool.

Any other differences between the server-side and client-side tools relates to how they are configured and run. The differences do not relate to how the tools identify or update appointments that have to be updated.

For individual users
Download and run the Time Zone Data Update Tool from the Microsoft Download Center. To do this, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568

We recommend that users run the Time Zone Data Update Tool as soon as possible after IT administrators apply the updates to the server that is running Exchange Server.

For more information about other Microsoft products that are affected by the extended DST period, visit the following Microsoft DST Web page:

http://www.microsoft.com/DST2007

How to minimize the effect of the extended DST period
To minimize confusion for users during the extended DST period, follow these steps: <ol> When a meeting is organized during the extended DST period, write the correct meeting time in the subject line or the body of the message. For example, include the following text in the subject line or the body of the message:

Project planning meeting – 8:30 a.m. PST

</li> Consider any calendar items in the extended DST period to be suspect. If you are not sure, verify the correct time with the organizer.</li> To help keep track of the calendar items that are scheduled during the extended DST period, print your weekly calendars for the extended DST period. Do this before you perform the following actions: <ol style="list-style-type: lower-alpha;"> Apply the Windows update that contains the updated time zone definitions.</li> Run the Time Zone Data Update Tool.</li></ol> </li></ol>

Important After you install the new time zone rules from a cumulative time zone update for Windows operating systems, calendar items are created by using the correct time zone definitions. For more information about this update, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

When you run the Time Zone Data Update Tool, the tool still detects single-instance appointments and single-instance meeting requests that you organized. The tool still shows these items that were created on or after the date that you installed the Windows time zone update. However, these items will be in an unselected state.

If you suspect that the time is still wrong on any calendar items that are created after the update is installed, you must click to select the check box that appears next to these items. However, after the items are updated, later runs of the Time Zone Data Update Tool will not detect the items for correction.

Why the Time Zone Data Update Tool is required
Calendar items are created in Outlook by using Coordinated Universal Time (UTC) format. UTC is an international standard 24-hour timekeeping system. Time zone information for Outlook is obtained from the Windows operating system in which the calendar items are created and is obtained at the time that the calendar items are created.

For example, an 8:00 A.M. appointment on October 26, 2007 in Redmond, Washington is stored in Outlook as UTC 4:00 P.M. In this case, DST has not yet started, and Redmond time is eight hours behind UTC.

When an update is applied to the Windows operating system to accommodate the new DST definitions, the computer’s local time is changed to the extended DST time. However, the UTC is not adjusted when the local time on the computer is adjusted. Therefore, calendar items that are added to Outlook during the extended DST period are off by one hour.

The Time Zone Data Update Tool is intended to update the targeted Outlook data store to correctly reflect the new time zone rules. A data store can be a .pst file, an .ost file, or the user’s Exchange mailbox if the user is running in Online mode.

For example, consider the following scenario:
 * Windows has not been updated for the extended DST period.
 * The Time Zone Data Update Tool has not been run on the computer.
 * An appointment is scheduled for 8:00 A.M. on October 15, 2007 in Redmond.
 * During the extended DST period, the start time for the appointment is set at 9:00 A.M. instead of 8:00 A.M.

In this scenario, the appointment is originally stored in Outlook as 4:00 P.M. UTC. To calculate the local time in Redmond, the &quot;UTC - 8 hours&quot; formula is used. In this case, 4:00 P.M. UTC minus 8 equals 8:00 A.M.

However, after the DST update is applied to Windows, local time is calculated by using the &quot;4.00 P.M. - 8 hours + 1 hour&quot; formula for DST. Therefore, the time in the appointment is set to 9:00 A.M. To correct this issue, the Time Zone Data Update Tool must be run on the computer.

For more information about how to support DST changes in Windows operating systems, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

The effects that occur when the Time Zone Data Update Tool is not run
If you do not run the Time Zone Data Update Tool, the time that is set for appointments and reminders in Outlook will be one hour off during the extended DST periods. All-day events will span two days because these events are associated with 24 specific hours instead of an individual date.

How to manually update calendar items
The Time Zone Data Update Tool is intended to automate the update process. However, users do not have to run the tool in order to update their calendar items. You can manually correct the times on these items during the extended DST period. This may be a good strategy for users who meet these specific requirements:
 * The users have recurring items that have exceptions before the extended DST period, and the past exceptions must be saved.
 * The users have many items in the extended DST period that were created by using previous time zone rules, and have other items that were created by using new DST rules.
 * The users want to maintain complete control over every item that must be changed in the extended DST period.
 * The users have run the Time Zone Data Update Tool. However, the tool did not update a given item that the users now want to update manually.

To manually change your calendar, follow these steps:
 * 1) Print a copy of your calendar during the extended DST period for reference.
 * 2) Manually move meetings that you organized to the correct time.
 * 3) Send an update for the meeting that you moved to all attendees so that the attendees' calendar reflects the correct time.
 * 4) Manually move all single-instance appointments.
 * 5) Manually move all recurring appointments within the extended time zone period.

Be aware that you may have to follow the same procedure for all future extended time zone periods if you created calendar items that occur many months in the future in your calendar. This is why we recommend that you use the Time Zone Data Update Tool to correct your calendar.

Important If you choose to manually update your calendar, do not run the Time Zone Data Update Tool. If you also run the Time Zone Data Update Tool, items that were manually updated may be over-corrected. Instead, wait until the extended DST period has passed, and then run the tool to automatically correct all future occurrences. When you do this, you do not have to manually make corrections for the next extended DST period.

Recurring item exceptions may be lost after calendars are updated
Before you run the Time Zone Data Update Tool, be aware that recurring items with exceptions are only updated for future exceptions.

Note The term &quot;exceptions&quot; refers to individual instances of the recurring item that were changed separately from the recurrence.

Any past exceptions to the series will be lost after you use the Time Zone Data Update Tool. If you have to save the information from the past exceptions, we recommend that you manually update the recurring item.

Different scenarios in Outlook
Appointments can be created under previous time zone rules or after time zone rules have been updated in Windows. Similarly, these same appointments can be viewed on computers that continue to operate under previous time zone rules or that have been updated to reflect new time zone rules.

When you view items on computers that have time zone rules that differ from the computer on which the item was created, the item will be shifted by one hour. For example, if you create an appointment by using previous time zone rules and then view the appointment under new time zone rules, the appointment time is shifted by one hour.

The following tables list the four scenarios that can exist and the actions that should be taken in these scenarios.

For more information about this update, visit the following Microsoft Update Web site:

http://update.microsoft.com/microsoftupdate/v6/default.aspx

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

Calendar items that are created in a Mexican time zone are not detected by the tool
Mexico has not adopted the DST changes that were made in the United States in 2007. However, Mexico intersects with three of the five U.S. time zones. These time zones are the Pacific, the Mountain, and the Central time zones.

This results in new time zones with the same &quot;GMT&quot; modifier. For example, when the DST update is applied to Windows, the following &quot;GMT -08:00&quot; time zones exist:
 * GMT -08:00 Pacific Time (US & Canada)
 * GMT -08:00 Tijuana, Baja California

If a particular user is located in Tijuana, GMT -08:00 Tijuana, Baja California is now that user's base time zone in Windows.

Consider the following scenario:
 * A user who lives Tijuana, Mexico has the GMT -08:00 Pacific Time (US & Canada); Tijuana home time zone. The following calendar items are created during the extended DST period by using pre-2007 DST rules and by using Outlook 2000, Outlook 2002 or Outlook 2003:
 * Single instance appointment
 * Recurring appointment
 * A single-instance meeting request or a recurring meeting request
 * Windows is updated on the computer to reflect the 2007 DST rules changes. The Windows time zone is changed to GMT -08:00 Tijuana, Baja California to match the appropriate time zone for Tijuana.

Note If the update for the 2007 DST changes is installed, the user’s time zone may automatically be moved. This process makes this step unnecessary.
 * Time Zone Data Update Tool is run. The user includes the following settings to address the previously created calendar items:
 * The user clicks Original Time Zone and then selects (GMT -08:00) Tijuana, Baja California.
 * The user clicks OK.

In this scenario, the Time Zone Data Update Tool does not detect any of the calendar items. Additionally, the user receives the following message:

No appointments, meetings or reminders were found that need to be moved to the new time zone.

However, no action is required. The items do not have to be updated because Mexico does not observe 2007 DST changes.

The scenarios in the previous tables describe cases in which calendar items may still reflect the incorrect times even after the operating system is updated and the Time Zone Data Update Tool is run on the local computer. In particular, you must pay attention to the following scenarios:
 * You are an attendee to a meeting that was sent by an organizer who has not updated the operating system and run the Time Zone Data Update Tool.
 * You view a calendar item on a computer or mobile device that has not been updated to reflect the new DST rules.

The Time Zone Data Update Tool is available to help users adapt to the changes in time zone rules. However, only users know whether their calendars are correct. Users must be made aware of this issue and must be instructed to review affected calendar items carefully. Users must verify the times of calendar items themselves and with any other invitees. Extra attention and communications, such as writing out the appointment or meeting time in the body of the item request, will also help address this issue.

Considerations for users in time zones that are not affected by time zone changes
Users who are in time zones that are not affected by the time zone changes technically do not have to install the cumulative time zone update for Windows that is described in article 933360 in the Microsoft Knowledge Base. However, we recommend that users everywhere install the cumulative time zone update for Windows. Some applications may use the local time zone database to perform date and time calculations for events elsewhere in the world. Therefore, all computers should be updated with these time zone updates regardless of whether the computers are located in a time zone that is affected by changes to the time zone. Common scenarios of how a global user may interact with time zones that are affected by time zone changes include, but are not limited to, the following examples:
 * When a user delegates access
 * When a user views another Exchange user's calendar
 * When a user travels with a laptop to a time zone that is affected by changes to their home time zone.
 * When meetings that a user receives from other users in affected time zones require that the recipient have updated time zone 2007 rules during extended periods.

Installation of the cumulative time zone update for Windows does not require any special effort or steps other than the installation itself. If you are in a time zone that is not affected by changes in time zone rules, you do not have to update your calendar. Therefore, you do not have to perform additional steps unless you are specifically asked to do this by the Exchange administrator.

How to install and to use the Time Zone Data Update Tool
To do this, follow these steps: <ol> Update Windows to apply the new DST rules. This update is available on the Windows Update Web site. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

</li> Install the Time Zone Data Update Tool.

Note Installation requires administrator credentials on the destination computer.

If you install and run the Time Zone Data Update Tool on a computer that is running Windows XP Service Pack 2 (SP2), be aware of the following issue: <ul> When a user who has standard user permissions double-clicks Tzmove.exe to install the tool, the user receives the following error message:

Time Zone Data Update Tool for Microsoft Office Outlook

You do not have sufficient privileges to complete this installation for all users of the machine. Log on as administrator and then retry this installation.

</li></ul>

A local administrator or a domain administrator must enter the correct credentials for installation to continue. After the Time Zone Data Update Tool is installed, a user who has standard user permissions can run the tool against the user's mailbox.

If you install and run the Time Zone Data Update Tool on a computer that is running Windows Vista, be aware of the following issue: <ul> When a user who has standard user permissions double-clicks Tzmove.exe to install the tool, the user receives the following message:

A program needs your permission to continue

If you started this program, continue. To continue, type an administrator password, and then click OK.

</li></ul>

A local administrator or a domain administrator must enter the correct credentials for installation to continue. After the Time Zone Data Update Tool is installed, a user who has standard user permissions can run the tool against the user's mailbox.</li> The Time Zone Data Update Tool will automatically start.

By default, when the tool starts, the default mailbox is selected, the current time zone is read from the operating system settings, and then the tool selects the Update to reflect changes to Windows time zones option.

If you want to move meetings that you organized to the new time zone, you must use the /physicalMove command-line switch.

If you want to run the tool against a different folder in your profile, click Custom.

If you are running Windows under the context of a non-administrator and enter an administrator’s credentials to run the Time Zone Data Update Tool for that user, the tool will return the following error and not update the non-administrator user’s items.

Microsoft Office Outlook

No profiles have been created. To create a new profile, use the Mail icon in Control Panel.

</li> <li>Click OK.</li></ol>

Important Tzmove.exe is the name of both the installer and the application. It may be confusing to know which version of Tzmove.exe to use because the installation does not create a shortcut on the desktop or on the Programs menu. This is especially true when you use the Exchange Calendar Update Tool.

The Time Zone Data Update Tool will not run on a computer that does not have Outlook installed
The Time Zone Data Update Tool requires Outlook. Users who try to install and then run the tool on a computer that does not have Outlook installed receive the following message:

Microsoft Office Outlook

No profiles have been created. To create a new profile, use the Mail icon in Control Panel.

When the user clicks OK, the user may receive the following error message:

Change Calendar Time Zone

The server is not available. Contact your administrator if this condition persists.

To resolve this issue, install Microsoft Office Outlook. Or, create an Outlook profile for the user.

How to determine whether the Time Zone Data Update Tool completed successfully
To determine whether the Time Zone Data Update Tool completed successfully, view the Application log on the computer on which you ran the tool, and then look for the following event. Event Type: Information

Event Source: TZMOVE

Event Category: None

Event ID: 32

Date:

Time:

User: N/A

Computer:

Description:

The Time Zone Data Update tool for Microsoft Office Outlook completed. 1 items updated in 'Mailbox - '. Additional information in %Temp%\Outlook Time Zone Update.log.

Update mode
The following table describes how the DST update process affects calendar items that are created in the following programs:
 * Outlook 2003
 * Outlook 2002
 * Outlook 2000
 * Outlook Web Access
 * Exchange Server 2003
 * Mobile devices

Command-line parameter options
/quiet

The Time Zone Data Update Tool can be installed silently by using the /quiet command-line parameter. Do to this, follow these steps: <ol> <li>Deploy the tool with the /quiet command-line parameter. This will install it but does not run the tool after installation is complete. The tool is installed to the default location that is described in step 2.</li> <li>After installation is complete, run the tool with one of the following command-line parameters, depending on whether the operating system is a 32-bit or 64-bit operating system: <ul> <li>For a 32-bit OS, type the following command:

“%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe” /quiet

</li> <li>For a 64-bit OS, type the following command:

“%PROGRAMFILES (x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe” /quiet

</li></ul> </li></ol>

When you run the Time Zone Data Update Tool in quiet mode, the tool updates profiles and anything that it finds in the default Calendar and the reminders folders, for example, appointment reminders, task reminders, and flagged mail. If you have multiple profiles on the computer, you must run the tool again in interactive mode and then manually select the additional profiles.

The installation of the Time Zone Data Update Tool creates an installation log file that is named &quot;Time Zone Data Update Tool for Microsoft Office Outlook(#).log&quot; in the temp directory of the computer. When you run the tool, the log file that is named &quot;Outlook Time Zone Update.log&quot; is created in the temp directory. The execution log is appended every time that you run the tool so that previous results are maintained. If no items require an update, no warning message is generated. Additionally, no log file is created or appended.

To find the temp directory on the computer, follow these steps:
 * 1) Click Start, click Run, type %temp%, and then click OK.
 * 2) Locate the &quot;Time Zone Data Update Tool for Microsoft Office Outlook(#).log&quot; file and the &quot;Outlook Time Zone Update.log&quot; file.

<div class="moreinformation_section">

/ONLYRECURRING

The /ONLYRECURRING command-line parameter option is used only to update recurring appointments in the selected calendar.

/MAXAPPTS

The Time Zone Data Update Tool will update only Outlook calendar items that fall within the DST transition periods. However, administrators can use the /MAXAPPTS command-line parameter to stamp the time zone property on all appointments that occur inside and outside the future extended DST times. The following table describes the effect of the /MAXAPPTS command-line parameter.

Move mode
The Time Zone Data Update Tool serves two purposes. Although you can use this tool to update calendar items for time zone rule changes, you can also use this tool to help move to a new time zone.

When to change the Outlook home calendar time zone
You may want to move the Outlook calendar to a different time zone in one of the following scenarios:
 * You permanently move to a different time zone.

For example, if you move from New York to Los Angeles, all-day appointments such as birthdays will start and end at 9:00 PM Pacific time instead of appearing as single all-day events, for example, from midnight to midnight.
 * You move to a different time zone because of a change in time zone rules.

For example, five counties in Indiana moved from Central time to Eastern time in November 2007. Also, Venezuela will move to a new time zone that has a new offset from GMT. This move is likely to occur in late 2007 or early 2008.

In these scenarios, you must adjust the operating system time zone and update the Outlook home calendar time zone. When you do this, all Outlook calendar items are affected. Although it is possible to manually update Outlook calendar items, the Time Zone Data Update Tool for Microsoft Office Outlook is the most efficient and complete method to use to update all the affected items.

Differences between a time zone move operation and a time zone update operation
Moving between time zones by using the Time Zone Data Update Tool for Microsoft Office Outlook resembles rebasing an Outlook calendar that is based on an updated definition of a time zone. This operation is documented in this article.

Specifically, you run the tool to find and update all affected calendar items that you have organized. Also, this action sends updates to each meeting attendee for the meetings that you have organized. However, some key differences exist between a time zone move operation and a time zone update operation. These differences are as follows:
 * The Exchange Time Zone Data Update tool does not support moving among time zones. Therefore, you must use the Time Zone Data Update Tool for Microsoft Office Outlook to perform time zone move operations.
 * Many of the special command-line options that are available for the Time Zone Data Update Tool for Microsoft Office Outlook are not supported when performing a time zone move operation. For example, the /QUIET option is not supported.

Note These first two differences effectively force the end-users to be aware of a time zone move operation. Also, these two differences require that the end-users play a part in the calendar modification that the move operation performs.
 * The concept of the patch date is replaced by the time at which the local time zone was changed on the operating system. This is the time when the user changed the current time zone setting in Windows. Therefore, there is no support for a command-line option such as the /ONLYCREATEDPREPATCH option. Therefore, it is best to rebase before you create any new calendar items from a computer that has been moved to a new time zone.
 * You must run the Time Zone Data Update Tool for Microsoft Office Outlook tool together with the /PHYSICALMOVE command-line option.

Important This is not the default mode for the tool. Also, this is not the mode in which the tool starts when the tool is automatically started by the Setup program.

To perform a move operation
To perform a time zone move operation, follow these steps: <ol> <li>Apply all the operating system updates that are required to support the destination time zone for the move operation. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

914387 How to configure daylight saving time for Microsoft Windows operating systems

</li> <li>Change the time zone on the computer to the destination time zone.</li> <li>Download and install the Time Zone Data Update Tool for Microsoft Office Outlook tool. To obtain this tool, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568

Note The tool automatically starts after it is installed. In this scenario, click Cancel to exit the tool. This action is required because the tool starts in time zone update mode instead of in physical move mode.</li> <li>Start the tool together with the /PHYSICALMOVE command-line option. To do this, use one of the following commands, as appropriate for the operating system: <ul> <li>For a 32-bit operating system, run the following command:

&quot;%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe&quot; / PHYSICALMOVE

</li> <li>For a 64-bit operating system, run the following command:

&quot;%PROGRAMFILES(x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe&quot; / PHYSICALMOVE

</li></ul> </li> <li>In the Change Calendar Time Zone dialog box that appears, click the original time zone in the Original Time Zone list, click the destination time zone in the New Time Zone list, and then click OK.

Note By default, the tool updates all the affected items in the Outlook calendar and in the Outlook Reminders folder. If you want to update additional items such as items in an additional calendar or such as items in a Personal Folders (PST) file, click Custom, and then select the appropriate folder.</li> <li>Follow the remaining steps in the tool to move the items to the new time zone. These steps resemble the steps to run the tool in time zone update mode.</li></ol>

Additional information for administrators
In addition to running the tool by using the steps in the &quot;To perform a move operation&quot; section, you may want to perform the following actions to streamline move operations:
 * Instead of downloading and installing the Tzmove.exe program every time that you perform a move operation, create a local copy of the Tzmove.exe file. Then, install the Time Zone Data Update Tool for Microsoft Office Outlook by using the /QUIET command-line option. When you do this, the tool does not automatically start after it is installed. Therefore, you do not have to click Cancel to exit the program.
 * Automatically start the tool in time zone move mode after you install it in quiet mode.

The following is an example of a batch ( .bat) file that you can use to perform these actions. @echo off <path of Tzmove.exe>\tzmove.exe /quiet &quot;%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe&quot; /physicalMove @echo on In this batch file, perform the following actions: <ul> <li>Replace  with the path of the Tzmove.exe file that you obtained from the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568

</li> <li>Modify the command-line if you are running the .bat file on a 64-bit operating system. The command-line is configured to use the default installation location for the Outlook Time Zone Data Update Tool on a 32-bit operating system.</li></ul>

Note This .bat file requires administrative rights to run.

Reporting Mode
To view the modifications that are made by the Outlook Time Zone Data Update tool, use the /REPORTINGMODE option. This option creates a log that can be used for planning. The /REPORTINGMODE option does not perform any modifications. Instead, it notes the items that would be modified if the tool were not run in Reporting Mode and logs these items to the Application log.

Additional command-lines
The tool provides additional command-lines. However, special consideration should be given to each of these options. Microsoft recommends that you thoroughly test these in a controlled, non-production environment before you use them with actual user data. In this way, you can fully understand what each does. Additionally, you can understand the end result of each.

Scenario 1: Rebase single-instance items after a Windows time zone updates is applied
Single-instance calendar items that are created after Windows time zone updates have been applied do not have to be rebased because these items are created by using the new DST rules. If the items are rebased, they are moved to one hour earlier. This may cause confusion or missed meetings.

To help prevent the rebasing of single-instance items that are created after Windows time zone updates have been applied, the Outlook Time Zone Data Update tool can determine when the update was applied. The tool does this by examining the following registry subkey:

 

By examining this registry subkey, the Outlook Time Zone Data Update tool can determine whether the following updates are installed, based on the Knowledge Base (KB) article IDs for the updates:
 * KB928388
 * KB931836
 * KB933360

Command-line options and usage

To prevent the rebasing of single-instance items that were created after the Windows time zone update was applied, you can use the following two command-line options. Additionally, a new default behavior has been added in which /ONLYCREATEDPREPATCH logic is used to prevent rebasing. <ul> <li>/ignorePatchDate

This option lets you run tzmove without detecting operating system update dates. Therefore, all appointments will be examined for rebasing. Use this option to restore the previous default behavior to ignore update installation date information.</li> <li>/ONLYCREATEDPREPATCH: 

This option configures the Outlook Time Zone Data Update tool to rebase the following: <ul> <li>All recurring items</li> <li>The single-instance items that were created before the specified date</li> <li>The single-instance items that were created before the dates of the knowledge base article IDs that are specified in a KB Input File.</li></ul>

The UTC date and time must be specified in the following format:

/ONLYCREATEDPREPATCH[:  Z]

The following is an example command-line:

/ONLYCREATEDPREPATCH:2007-02-16T12:00:00Z

</li></ul>

Notes
 * You may use either of the above options together with the /FORCEREBASESUPPRESSALLUPDATES(SuppressAll) command-line option or together with the /FORCEREBASESUPPRESSEXCHANGEUPDATES(SuppressExchange) command-line option. If you use /ONLYCREATEDPREPATCH, you must specify a time. Otherwise, behavior across multiple computers will be unpredictable. Correct syntax for usage would be as follows:

/ONLYCREATEDPREPATCH:2007-02-16T12:00:00Z /FORCEREBASESUPPRESSALLUPDATES

/IGNOREPATCHDATE /FORCEREBASESUPPRESSALLUPDATES

Issues for Scenario 1

When you use the command-line options to address scenario 1, be aware of the following issues and limitations: <ul> <li>If a time zone update has been installed on an operating system but the registry value for that update is missing or incomplete, the Outlook Time Zone Data Update tool will not correctly detect the update. In this case, the Outlook Time Zone Data Update tool will log an event to the Application log.</li> <li>If a time zone update was performed manually to the system, the Outlook Time Zone Data Update tool cannot detect the update. For example, if you performed the procedure that is described in following knowledge base article, neither the command-line options nor the Outlook Time Zone Data Update tool will be able to detect this update:

914387 How to configure daylight saving time for the United States in 2007

</li> <li>Windows Vista includes built-in, dynamic time zones. Therefore, updates do not exist in Windows Vista for the Outlook Time Zone Data Update tool to detect.</li> <li>The registry contains only the date on which an update was installed. It does not contain the time at which it was installed. Rebasing occurs on items that are created in UTC time before the date on which an update was installed. Therefore, items that are created on the same day in which the update was applied but before the update was applied will not be rebased. This issue occurs even though these items have to be rebased.</li> <li>Consider the following scenario: <ol> <li>A single-instance calendar item is created before the DST updates are installed on the operating system. The calendar item uses the previous DST rules.</li> <li>You install the DST updates on the operating system. The system now has the new time zone rules.</li> <li>You manually update the calendar items by using the new DST rules.</li> <li>You run the Outlook Time Zone Data Update tool.</li> <li>The single-instance calendar item is rebased to the wrong time.</li></ol>

In this scenario, the single-instance calendar item is rebased when you use the /ONLYCREATEDPREPATCH option or when you run the default behavior. This is because the item was created before the DST updates were installed on the operating system. The item is rebased even though the item was updated manually.</li> <li>The Outlook Time Zone Data Update tool cannot update items that are affected by many users who are using different time zone rules. For example, consider the following scenarios: <ul> <li>A delegated user is using the previous DST rules. The delegate's manager is using the new DST rules. The delegate creates items in the manager’s calendar between the time in which the Windows time zone update was installed on the manager’s computer and the time in which the Outlook Time Zone Data Update tool is run. In this scenario, the items that the delegate created will not be updated.</li> <li>You use a client computer that uses the previous DST rules. Then, you use another client computer that uses the new DST rules. You create items on the client computer that is using the previous DST rules, and then you run the Outlook Time Zone Data Update tool on the client computer that is using the new DST rules. In this scenario, the items that are created by using the previous DST rules will not be updated by the Outlook Time Zone Data Update tool.</li> <li>An item is created by a mobile device or by a program that creates items under the previous DST rules. This item is created after you install the new DST updates but before rebasing has occurred. In this scenario, the item is created by using the previous DST rules. However, because the calendar uses the new DST rules, the items will not be rebased when you run the Outlook Time Zone Data Update tool.</li></ul> </li> <li>Consider the following scenario: <ol> <li>An end-user installs the new Windows time zone update.</li> <li>The user creates some single-instance items under the new DST rules.</li> <li>The user uninstalls the Windows time zone update.</li> <li>The user creates more items under the previous DST rules.</li> <li>The user reinstalls the Windows time zone update.</li> <li>The user runs the Outlook Time Zone Data Update tool.</li></ol>

In this scenario, the user will have some items that were created under the new DST rules before the update installation date that is listed in the registry. These items will be rebased to the wrong time.</li></ul>

Scenario 2: Force rebase calendar items and suppress the calendar updates that result from the time zone rebasing
This section provides a summary analysis of the results of rebasing calendar items by using the Outlook Time Zone Data Update tool and suppressing the calendar updates that result from the time zone rebasing.

Command-line options and usage

To suppress calendar updates that are generated as the result of a rebasing operation, you can use the following two command-line options together with the Outlook Time Zone Data Update Tool: <ul> <li>/FORCEREBASESUPPRESSALLUPDATES

This option is known as &quot;SuppressAll&quot; in this article. SuppressAll is used to rebase all single-instance items if a time zone property does not exist. It is also used to rebase any recurring items that were created by using the previous DST rules. The rebase occurs regardless of who the organizer is. This mode will not send any updates for any reason.</li> <li>/FORCEREBASESUPPRESSEXCHANGEUPDATES

This option is known as &quot;SuppressExchange&quot; in this article. SuppressExchange is used to rebase all single-instance items if a time zone property does not exist. SuppressExchange is also used to rebase any recurring items that were created by using the previous DST rules. The rebase occurs regardless of who the organizer is.

When you use this option, updates are sent only when the meeting organizer runs the tool and the updates are sent only to non-Exchange meeting attendees. Exchange attendees and non-Exchange attendees are determined by examining the PR_ADDR_TYPE property of each attendee. If the value for this property does not equal SMTP or EX with a valid PR_EMS_AB_TARGET_ADRESS, the attendee is skipped, and the attendee will not receive an update. This operation will consume more resources because of the overhead that is added by the detection of non-Exchange attendees. It also includes the expansion of all distribution list attendees to determine whether the distribution list contains any non-Exchange attendees. By default, all distribution list attendees and nested distribution list attendees will be expanded and examined.

You can limit the distribution list expansion depth by using the MaxDepth option. MaxDepth can be any number between 0 and 9999 to represent the maximum depth of distribution lists that will be expanded. You can set MaxDepth to 0 to cause only top-level recipients to be processed. This option is used in the following format:

/FORCEREBASESUPPRESSEXCHANGEUPDATES: MaxDepth

The following is an example command-line:

/FORCEREBASESUPPRESSEXCHANGEUPDATES:2

</li></ul>

If you use both command-line options, SuppressAll overrides SuppressExchange.

Note These options may be used together with either the /ONLYCREATEDPREPATCH: or the /IGNOREPATCHDATE command-line options.

Issues for Scenario 2

For information about issues that you must consider when you use the SuppressAll option and the SuppressExchange option, visit the following Microsoft Web site:

http://support.microsoft.com/gp/cp_dst

For more information about additional issues to consider, click the following article numbers to view the articles in the Microsoft Knowledge Base:

941018 How to address daylight saving time by using the Exchange Calendar Update Tool

Additionally, consider the following issues when you use the SuppressAll command-line option and the SuppressExchange command-line option.

Note This is not a comprehensive list. This list contains the issues of which we are currently aware. However, additional issues may be discovered in the future. <ul> <li>If items do not have a time zone property, Outlook cannot verify what the source time zone should be. For example, this issue occurs with single-instance items. Outlook determines which calendar items will be updated based on the source time zone of the mailbox or based on the source time zone of the client computer’s operating system if the mailbox information is not present. Therefore, it may be better for meeting organizers to rebase their own items.</li> <li>People may be in time zones that are affected in different ways by the DST changes. For example, this situation occurs when the meeting organizer is in one time zone where items are being shifted and a recipient is in a different time zone where items are not being shifted. Consider the following scenarios: <ul> <li>An organizer in the Pacific Time zone has a meeting that is scheduled with an attendee in an area that does not observe DST, such as an attendee in Arizona or Hawaii. When the organizer’s calendar is rebased, the meeting is shifted by one hour. If the rebasing is performed by using either the SuppressAll option or the SuppressExchange option, an update is not sent to the recipient in the non-observing time zone. Therefore, the attendee's calendar will be wrong by one hour. Additionally, the attendee may be an hour late for the meeting.</li> <li>A resource is updated by many organizers who are in different time zones. Some organizers are in time zones that observe DST, and some organizers are in time zones that do not observe DST. Because the SuppressAll option and the SuppressExchange option base their logic on the time zone information of the resource account, that information may not match the time zone information of all organizers. In this scenario, meetings may not shift as expected. This may cause unpredictable behavior.

Note Because of their intrinsic nature, resource calendars provide an easy way to see the unexpected behavior that can occur across time zones that observe DST differently. This is especially true for resources that are not rooms and that do not have a specific time zone, such as conferencing equipment.</li></ul> </li> <li>This solution must be used for all mailboxes in the organization. The SuppressAll option and the SuppressExchange option cannot be used together with any other methods. Because no updates will be sent, this solution relies on everyone’s calendars being rebased. If the solution is not used for all mailboxes in the organizations, some users’ items will not be rebased.</li> <li>Tracking will not be accurate because updates are not sent to attendees. Each meeting has a time stamp that is used by the organizer and by the attendees to detect whether another request or response to the same item is out of date. This is required because requests and responses may not arrive in the same order in which they were sent. Additionally, these items may be processed in a different order than the order in which they were received. The ForceRebase option only updates the time stamp on the organizer’s items. This guarantees that the attendee can always receive updates from the organizer. However, this behavior will prevent the organizer from tracking responses from the attendee because the organizer will consider the response to be out of date.

For example, consider the following scenario: <ul> <li>The organizer uses the previous DST rules to send a meeting request that falls within the new extended DST 2007 period. The organizer and the attendee update their systems with the new DST rules. Then, the Outlook Time Zone Data Update tool is run together with the SuppressAll option. The attendee sends a response that is processed by the organizer. In this scenario, the response is not tracked on the calendar item. Additionally, they receive the following message on the InfoBar:

The meeting was updated after the attendee sent this response.

After the updates have been run, if the attendee forwards the meeting to another person and that person accepts the meeting, the second person will not be added to the meeting. Therefore, if the organizer sends an update, the person to whom the meeting was forwarded will not receive the update.</li></ul> </li> <li>A personal distribution list that uses the SMTP address of the GAL entry will send updates. This occurs even when the SuppressExchange option is used. When you click Add to Contacts from the global address list (GAL) or you add someone from the GAL to a personal distribution list, Outlook uses the SMTP address of the entry instead of the EX address. When you run the Outlook Time Zone Data Update tool together with the SuppressExchange option, an update is mistakenly sent to these recipients.

For example, consider the following scenario: <ul> <li>A mailbox includes a contact that was created from the GAL by using the Add to Contacts feature. Or, the mailbox includes a personal distribution list that was created from the GAL. You send a meeting request to this contact or to this personal distribution list. Then, you run the Outlook Time Zone Data Update tool together with the SuppressExchange option. The Outlook Time Zone Data Update tool rebases this meeting and sends an update to the recipient, even though the recipient is internal. For single-instance meetings that do not have a time zone property, the internal recipient attendee will receive the update and process it. However, if this recipient then runs the Outlook Time Zone Data Update tool, the item may be rebased again. The recipient does not know that the second rebasing occurred. Therefore, the recipient may miss the meeting.</li></ul>

Additionally, the following are examples of how you can have an SMTP address for an internal recipient: <ul> <li>You use the Add to Contacts feature to add a mobile phone number for a coworker.</li> <li>You type the SMTP version of an internal address directly on the To line. This puts the SMTP address in the Outlook nickname cache. The nickname cache is always used first by the AutoComplete feature.</li> <li>The name resolution is set to resolve against the Contacts folder first and to resolve against the GAL next. You may have many meetings with SMTP addresses for attendees, even though the attendees are internal and have Exchange addresses.</li></ul> </li> <li>Incorrect behavior may occur if the organizer or the attendee updates the meeting between the times that the Outlook Time Zone Data Update tool is run on either of their mailboxes. If the organizer updates a meeting between the time that the organizer and the attendee rebase, the item will be either an hour early or an hour late in the attendee's calendar. This depends on who rebases first.

For example, consider the following scenario in which the organizer rebases first: <ol> <li>The organizer and the attendee have a single-instance meeting in the delta time period.</li> <li>The Outlook Time Zone Data Update tool is run on the organizer’s mailbox first.</li> <li>The organizer sends an update for the meeting because of a change of location. This update uses the new DST rules.</li> <li>The attendee accepts the meeting update.</li> <li>The attendee rebases his or her calendar and causes the meeting to be one hour off.</li></ol>

Or, consider the following scenario in which the attendee rebases first: <ol> <li>The organizer and the attendee have a single-instance meeting in the delta time period.</li> <li>The Outlook Time Zone Data Update tool is run on the attendee’s mailbox first.</li> <li>The organizer sends an update for the meeting because of a change of location.</li> <li>Because the organizer controls the meeting, the meeting shifts back to the previous DST rules.</li> <li>The organizer rebases their calendar and causes the meeting to be one hour off.</li> <li>The attendee does not know to run the Outlook Time Zone Data Update tool again. Additionally, if the attendee runs the Outlook Time Zone Data Update tool again, this will rebase any new items that were created.</li></ol> </li> <li>You may be unable to determine whether a non-Exchange recipient will be designated as a Required attendee, an Optional attendee, or a Resource attendee. This depends on when the non-Exchange recipient is found. For example, if an optional non-Exchange recipient is part of a distribution list that is a Required attendee, and the distribution list is processed first, the recipient update will list the non-Exchange recipient as Required. However, if the individual recipient is processed first, the update will mark the recipient as Optional.</li> <li>If outgoing requests are sent to Optional or Resource attendees, the requests may appear malformed when they are viewed.</li> <li>Cross-forest entries in the GAL use the SMTP address and not the EX address. Therefore, if you run the Outlook Time Zone Data Update tool together with the SuppressExchange option, you will send an update to these recipients when you should not send one. We recommend that you do not use this option in environments that have multiple Exchange forests.</li></ul>

Notes about the analysis for Scenario 2
 * Unsent updates are a known cause of disappearing or duplicate meetings.
 * Corrupted meetings generally are not deterministic. But they are a large concern for calendar items.
 * No testing was done for CDO-based applications such as BlackBerry and other devices.
 * No testing was done for users who are not connected or for environments that are not joined to a domain.

Scenario 3: Rebase direct booking and resource calendars
Rebasing of automated systems such as Auto Accept Agent and Direct Booking may be problematic because the timing of the rebasing must be deterministic. Because this cannot be done by using the Outlook Time Zone Data Update tool, the following alternative scenarios have been created. These scenarios use the /FORCEREBASESUPPRESSALLUPDATES command-line option that is discussed in Scenario 2.

Update resource mailboxes for new time zone rules

As a Microsoft Exchange administrator, you can use the Outlook Time Zone Data Update tool to update calendars in resource mailboxes. To do this, follow these steps: <ol> <li>The Auto Accept Agent service must be running on the server that is running Microsoft Exchange Server. For more information about the operation and management of Auto Accept Agent, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/aa997184.aspx

</li> <li>Install the Windows time zone DST 2007 update.

For more information about Windows time zone update, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

</li> <li>Run the Outlook Time Zone Data Update tool together with the /FORCEREBASESUPPRESSALLUPDATES option. This option should be used for all resource mailboxes that have Auto Accept Agent enabled.</li> <li>Verify that the Auto Accept Agent service is running again. The Auto Accept Agent service must be running for users to receive acceptance messages for updates to the meetings that they have organized.</li></ol>

Note When you rebase a whole Exchange environment, run the Outlook Time Zone Data Update tool without the /FORCEREBASESUPPRESSALLUPDATES option against all the other mailboxes. This includes mailboxes that organized meetings with the resource mailboxes.

Update resource mailboxes that contain directly booked resources

To update calendars in resource mailboxes that contain resources that were directly booked, you must use the Outlook Time Zone Data Update tool. To update these calendars, include the /FORCEREBASESUPPRESSALLUPDATES option when you run the Outlook Time Zone Data Update tool against all resource mailboxes. This will move directly booked resources to the correct times. Resource mailboxes receive updated meeting requests, but user mailboxes will not receive meeting requests.

Notes
 * After you rebase all mailboxes, Auto Accept Agent will reject the conflicting direct booking attempt if the option to reject conflicts is enabled. This occurs even when meetings in resource mailboxes are labeled as Tentative.
 * When you rebase a whole Exchange environment, run the Outlook Time Zone Data Update tool without the /FORCEREBASESUPPRESSALLUPDATES option against all the other mailboxes. This includes mailboxes that organized meetings with the resource mailboxes.

Scenario 4: Rebase public folder calendars
Items in shared calendars that are stored in public folders must also be updated to the new DST rules. You can use the update for the Outlook Time Zone Data Update tool to rebase items on calendars that are stored in public folders.

You can rebase public folder items by using the Outlook Time Zone Data Update tool. You can do this by using the graphical user interface for the tool or by using Quiet mode and providing the path of the public folder calendar.

Providing a calendar path is supported only when you use Quiet mode. You can use either –Q or –QUIET as the command-line option to specify Quiet mode. The path must be the last item that is specified on the command line. The path must be preceded by two backslashes (\\), and it must use a single backslash (\) to delimit the hierarchy. If one or more of the public folders in the path contains a backslash as part of its name, you must use a double backslash.

For example, command lines for rebasing public folder calendar items may include the following:
 * tzmove.exe -QUIET \\Public Folders\All Public Folders\Folder1\Sub Folder\Calendar
 * tzmove.exe -Q –ONLYRECURRING \\Public Folders\All Public Folders\ProjectZ\Meetings\\Notes\Calendar

In the second example, a public folder that is named Meetings\Notes contains the public folder calendar. Because this public folder name includes a backslash, the path that represents the folder must contain a double backslash.

You can also rebase calendar items that are stored in additional calendars that may exist in a user's mailbox. For example, a command for rebasing the items in an additional calendar in a user's mailbox may resemble the following:

tzmove.exe -Q \\Mailbox - User\Second Calendar

When you rebase a public folder calendar or rebase an additional calendar that may exist in a user’s mailbox, the rebased items use the Sent on Behalf of message in the From field. Therefore, the updates do not change the owner of the calendar item. The updates appear to be from the account that rebased the calendar on behalf of the account that organized the meeting.

Notes
 * You cannot use this path option if you are running the Outlook Time Zone Data Update tool from a UNC path. You will receive an error message.
 * Appointments or meetings that are scheduled by a user who is not in a time zone that is affected by the DST changes are incorrectly shifted forward by one hour. Therefore, all the items on the calendar must be scheduled by users who are in time zones that are affected by the DST changes.

Other issues that are addressed by the Outlook Time Zone Data Update tool
The Outlook Time Zone Data Update tool also includes fixes for the following two issues:
 * When you run an earlier version of the Outlook Time Zone Data Update tool, any calendar items that are in an unsent state are processed. When this occurs, updates are sent for original calendar items that had not been sent.

This condition represents a potential privacy concern, because the draft meeting request may include sensitive or confidential information that would not be included in the meeting request that was eventually sent.
 * Support for nondefault calendars has been added to update calendars in public folders and nondefault calendars in user mailboxes. Additionally, support has been added to update calendar items that have been sent by one user on behalf of another user.

Glossary of command-line options for the Outlook Time Zone Data Update tool
The following list describes the command-line options that are included in the Outlook Time Zone Data Update tool. For more information about the specific uses of these command-line options and about the issues that are associated with each of these options, see the &quot;Scenarios&quot; section.
 * /SENDRESOURCEUPDATES

This option changes the new default behavior and restores the behavior of the older version of the tool so that Bcc recipients and resources receive updates.
 * /PHYSICALMOVE

This option runs the Outlook Time Zone Data Update tool in the mode that lets you move the base time zone of all appointments that are stamped with a time zone property to a new time zone. You should use this option when a user moves physically from one time zone to another. This switch is not applicable for daylight saving time changes.
 * /IGNOREPATCHDATE

The tool's new default behavior is to look up the update installation date for the specified time zone and to touch only the single-instance appointments that were created before the update installation date. If you want all appointments to be rebased, even the ones that were created after the update installation date, use this switch to ignore the update installation date and to select all single-instance appointments.
 * /ONLYCREATEDPREPATCH[:  Z

This option configures the Outlook Time Zone Data Update tool to rebase all recurring items and only the single-instance items that are created before the specified date or before the dates of the KB article IDs that are specified in a KB Input File.
 * /FORCEREBASESUPPRESSALLUPDATES

This option is used to rebase all single-instance items if no time zone property exists and to rebase any recurring items that were created by using the previous DST rules, regardless of who the organizer is. This mode will not send any updates for any reason.
 * /FORCEREBASESUPPRESSEXCHANGEUPDATES

This option is used to rebase all single-instance items if no time zone property exists and to rebase any recurring items that were created by using the previous DST rules, regardless of who the organizer is. When you use this option, updates will be sent only to non-Exchange attendees.
 * /FORCEREBASESUPPRESSEXCHANGEUPDATES[:MaxDepth]

This option is used to specify a number between 0 and 9999 to represent the maximum depth of distribution lists that will be expanded. Setting MaxDepth to 0 causes only top-level recipients to be processed.
 * /REPORTINGMODE

This option does not perform any modifications. Instead, it notes the items that would be modified if the tool was not run in Reporting Mode and logs these items to the Application log.

Suppress the Change Calendar Time Zone Tool in Microsoft Office Outlook 2007
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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Outlook 2007 SP1 disables any auto-prompting to change the calendar time zone that occurs in Outlook 2007 RTM when a change to the local time zone definition is detected. If you are still using Outlook 2007 RTM, you can prevent this auto-prompting from running by using a Group Policy or by modifying the Windows registry on the particular computer.

You can use the following administrative template to create a Group Policy object to prevent the Change Calendar Time Zone Tool in Outlook 2007 from running. POLICY !!L_Disableautomaticupdatestoappointments KEYNAME Software\Policies\Microsoft\Office\12.0\Outlook\Options\Calendar VALUENAME DisableTimeZoneAutoPrompt VALUEON NUMERIC 1 VALUEOFF NUMERIC 0 EXPLAIN !!L_DisableautomaticupdatestoappointmentsExplain END POLICY To obtain policy template files for 2007 Office System administrative templates (.adm files), visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=92D8519A-E143-4AEE-8F7A-E4BBAEBA13E7

Known issues and limitations
<ul> <li>Reminders are included in the total count of items that have to be updated. When you run the Time Zone Data Update Tool, any reminders that you have on the calendar items that have to be updated will be included in the total number of items being scanned.

For example, if you have 25 calendar items and 20 of them have reminders, the Time Zone Data Update Tool will report that it is scanning 45 items.</li> <li>If you flag a reminder on an e-mail item in Outlook 2000, in Outlook 2002, or in Outlook 2003, and then run the Time Zone Data Update Tool, the reminder is correctly updated and moved to the proper time. However, the InfoBar (UI) displays the incorrect time.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.</li> <li>When you run the Outlook or Exchange update tools, appointments are off by one hour on mailboxes where the home time zone is New Zealand Standard Time. This behavior occurs when the following scenarios are true: <ul> <li>You run the Outlook or Exchange update tools on a computer that is running Windows Vista.</li> <li>The home time zone of the mailboxes that are being updated is New Zealand Standard Time.</li></ul>

To work around this problem, you must run the Outlook or Exchange update tools again against the mailboxes on or after January 1, 2008.

This behavior occurs because Windows Vista handles time zone information differently than other versions of Windows. If you do not run the Outlook or Exchange update tools again on or after January 1, 2008, all appointments in the second DST event will be off by one hour. The second DST event includes dates from March 16, 2008 through April 6, 2008. If you do not want to wait until January 1, 2008 to update appointments in the second DST event, you can run the Outlook or Exchange update tools from a computer that is running Windows XP or Windows Server 2003. Please notice that any calendar items created on a Windows Vista computer before January 1, 2008 will still be created by using the incorrect time zone definition and must be rebased after January 1, 2008.</li> <li>Your secondary time zone in the Outlook Calendar is incorrect after you update your OS time zones.

To work around this problem, manually turn off the additional column, and then turn it on again.

</li></ul>

<div class="moreinformation_section">

<ul> <li>You may receive error code 0x80001081, 0x80001082, or 0x80001083 after you run the Time Zone Data Update Tool.

After you run the Time Zone Data Update Tool, the following information may be logged in the &quot;Outlook Time Zone Update.log&quot; file:

<pre class="fixed_text">Type: Appointment ID: 040000008200e00074c5b7101a82e00800000000c8a7e927f3a1eb5f428868471a4754c1168cc49bd064fbcb3eeff51a574f8330 Subject: My weekly business meeting Old Start Time: Tuesday, March 20, 2007 3:00:00 PM New Start Time: Tuesday, March 20, 2007 2:00:00 PM Old End Time: Tuesday, March 20, 2007 4:00:00 PM New End Time: Tuesday, March 20, 2007 3:00:00 PM Recurring: No Result: Success Result: Error (The client operation failed.) (0x80001083, 0x80004005, 0x1020)

Error 0x80001081, 0x80001082, or 0x80001083 is likely related to incorrect Free/Busy information. To resolve this issue, run Outlook together with the /CleanFreeBusy option. Perform this action on the computer that experiences problems publishing Free/Busy information. This action refreshes the Free/Busy information. To do this, follow these steps: <ol> <li>Click Start, click Run, type Outlook.exe /cleanfreebusy, and then click OK.</li> <li>Examine the published Free/Busy information from another computer.</li></ol> </li> <li>You must accept the meetings that have been forwarded to you to receive updates when the meeting organizer runs the Time Zone Data Update Tool.

For the recipient of the forwarded meeting request to be added to the original meeting, that user must send a response to the request. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

909109 In Outlook 2003, a user does not receive meeting updates if the user clicked the &quot;Don't send a response&quot; option in response to a forwarded meeting request

</li> <li>When an attendee clicks the Calendar button in a Time Zone Data Update Tool update meeting in the Inbox, the date changes to August 31, 4500 instead of to the correct date. This problem seems to only affect users who have mailboxes on Exchange Server 5.5.

In some scenarios, the meeting update might be missing some legacy properties in Exchange 5.5. The missing legacy properties cause this behavior in Outlook. If this problem occurs, the attendee should click Accept in the updated meeting. The meeting will then be correctly placed in the attendee’s calendar.</li></ul>

Frequently Asked Questions (FAQs)
Q: How is the target time zone reflected in Outlook items?

A: Single-instance appointments are stored in UTC. The UTC time is determined by the computer that is used to create the appointment. Versions of Outlook that are earlier than Outlook 2007 do not indicate in which time zone an appointment is created.

Note Outlook 2007 does store target time zone information about single-instance appointments.

Recurring appointments have the full-time zone definition embedded in the data. Therefore, no additional data is required to compute time zone definition and DST transition dates.

Q: At a high level, how does the Time Zone Data Update Tool work?

A: The Time Zone Data Update Tool can detect that there are new rules for a given time zone based on a new concept of &quot;dynamic time zone rules.&quot; These rules have start dates and end dates that describe when the rules are in force. If the Time Zone Data Update Tool detects that there are new rules for a given time zone, the tool can automatically try to transition any calendar items that are affected by the change into the new &quot;version&quot; of the time zone.

This process can occur in the following cases:
 * Recurring appointments These appointments have the exact time zone definition embedded in them so that the Time Zone Data Update Tool can compare that time zone definition to the &quot;pre-image&quot; of the updated time zone. If the definition matches, the tool can rewrite the appointment by using the &quot;new version&quot; of the time zone information.
 * Single-instance appointments These appointments are more difficult to process. In versions of Outlook that are earlier than Outlook 2007, these appointments contained no time zone information. Therefore, it is impossible for the Time Zone Data Update Tool to tell whether they have to be updated.

Currently, the tool assumes that any unstamped single-instance appointments that were created before the Windows time zone update was installed and that are in the extended DST period were generated by using the old time zone rules. Then, the tool offers to update them.

Some single-instance appointments were created for an unaffected time zone but fall within the affected dates of a time zone that is being transitioned. Those appointments will also be identified by the Time Zone Data Update Tool as requiring an update. In these cases, only the user knows whether a particular appointment should be updated. The user should take action accordingly.

Q: When will my Windows time zone definitions be updated if I am using Windows Vista?

A: Windows Vista is prepared for the new time zone rules. Windows Vista automatically updated its time zone definitions on January 1, 2007. As new updates become available, all Windows operating systems will receive time zone updates through Windows Update and Microsoft Update. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

933360 August 2007 cumulative time zone update for Microsoft Windows operating systems

Q: When should I run the Time Zone Data Update Tool?

A: The Time Zone Data Update Tool must be run manually at the discretion of the user or the administrator after the operating system time zone definitions have been updated.

It is better to run the Time Zone Data Update Tool or the Exchange tool as close as possible to the time at which the operating system time zone update was applied to all computers. When you do this, there is less of a possibility of having single-instance appointments that were booked after the Windows time zone update was applied but before the Time Zone Data Update Tool or the Exchange tool was run.

Outlook 2007 has this functionality already embedded. Therefore, the Outlook 2007 user is not required to manually run the Time Zone Data Update Tool. Outlook 2007 will automatically detect that the change is required and will prompt the user when it runs the tool. When you install Outlook 2007 SP1, the tool will no longer auto-prompt to run.

However, the Time Zone Data Update Tool contains code changes that refine the experience. The tool is the preferred method of updating your calendar. You can run the tool by clicking Cancel in the dialog boxes that appear automatically in Outlook 2007 and by following the instructions to download and to run the Time Zone Data Update Tool instead.

'''Q: The Time Zone Data Update Tool is more recent than what was built into Outlook 2007. Should I use the Time Zone Data Update Tool instead?'''

A: Yes. The Time Zone Data Update Tool has enhancements that make it the better method to update even your Outlook 2007 calendar, regardless of the automatic prompt that Outlook 2007 displays. To run the tool, close the prompt dialog box, or click Cancel. Then, install and run the more recent update on your calendar. To see instructions for how to do this, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568

Q: Which appointments does the Time Zone Data Update Tool try to fix?

A: Because of the method in which a target time zone is reflected in appointments, the Time Zone Data Update Tool will try to update the following appointments:
 * All single-instance appointments that fall into the affected date ranges and that were created before the Windows time zone update was installed
 * All recurring appointments that have instances in the affected date ranges and that were not created for other time zones

Note The tool will try to update all such single-instance appointments because the tool cannot tell the time zone to which they are targeted. This condition does not apply if the appointments were created in Outlook 2007 or were already updated by a previous run of the Time Zone Data Update Tool.

Q: Why doesn't the Time Zone Data Update Tool update all my affected meetings?

A: The Time Zone Data Update Tool updates only those meetings for which the user is the organizer. The tool then automatically sends updates for those meetings to all other attendees.

Q: What happens if I run the Time Zone Data Update Tool multiple times?

A: The Time Zone Data Update Tool correctly stamps the calendar items that the tool updates with the time zone information in which the calendar items were encoded. This process is already included for recurring appointments. However, this is not the case for single-instance appointments. Therefore, it is generally safe to run the Time Zone Data Update Tool multiple times as long as you do the following:
 * Consider the version of Outlook that you use to create new items after you run the tool
 * Consider how many items that you create between the first run and subsequent runs of the tool.

The tool will see and will ignore all calendar items that were already updated.

Note After you run the tool, any single-instance items that are created by using Outlook 2000, Outlook 2002, or Outlook 2003 are moved and updated when you next run the tool.

However, if the user explicitly asks the Time Zone Data Update Tool to ignore a set of calendar items, the tool will continue to discover those calendar items in future runs. In this case, the user has to explicitly ignore those calendar items on each run.

For example, this can occur when the user has single-instance appointments that are targeted at a different time zone. Additionally, this can occur when the user has appointments that the user created after the time zone rules were updated but before the user ran the Time Zone Data Update Tool.

Q: What are some situations in which I might want to run the Time Zone Data Update Tool multiple times?

A: It is good practice to run the Time Zone Data Update Tool multiple times if the following conditions are true:

Condition A

 * You run the Time Zone Data Update Tool on the users' mailboxes.
 * After you do this, users create appointments or meetings from computers or devices that do not contain new DST rules.

Condition B
A recurring appointment that did not have any instances that fell into the extended DST times is extended in such a way that one or more of the additional instances now fall in an extended DST time.

In this case, the Time Zone Data Update Tool did not update the given recurrence because the tool had no instances that were affected by the DST changes. However, now that such occurrences exist, the tool has to be run again so that it can find and update the time zone information appropriately.

Q: What are some situations in which I explicitly want to avoid running the Time Zone Data Update Tool multiple times?

A: It is best to make sure that only one instance of the Time Zone Data Update Tool is running against a given mailbox at a time. Trying to update the same calendar from multiple computers at the same time may cause conflicts and other anomalies.

In one non-obvious case, the Time Zone Data Update Tool is run against an .ost file that is in Offline mode or in Cached Exchange mode. In such a case, you have to carefully consider at what time you will synchronize those changes to the server. For example, synchronization conflicts will occur if the following conditions are true:
 * The .ost file is offline at the time that the Time Zone Data Update Tool is run against the server store.
 * The tool is also run against the offline client store.
 * The .ost file is synchronized against the server store.

In this scenario, the Time Zone Data Update Tool would have tried to update all the appointments that required updates both in the server store and in the client store. In this case, conflicts can occur. Therefore, we recommend that the Time Zone Data Update Tool only be run while connected to the server in Exchange Server environments.

Q: How does the Exchange tool compare to the Time Zone Data Update Tool?

A: The Exchange tool will let you apply the time zone update in &quot;silent mode&quot; to a set of chosen mailboxes on the Exchange server. This means that the user will not have an opportunity to clear appointments that do not have to be updated.

The Exchange tool works only on server-side calendars. This means that any local calendars that a user might have, such as calendars in .pst stores, can be updated only by the client-side Time Zone Data Update Tool.

Q: What will happen to resource calendars?

A: Updates are not sent for meetings based on the time at which the Time Zone Data Update Tool is run. Administrators must run the tool on the resource mailboxes to correct the meetings.

Q: What happens if I use multiple computers and not all the computers are updated?

A: Particular attention should be paid when you use a combination of updated and non-updated computers. Appointments that are created by using non-updated time zone information and then are viewed on an updated computer will be incorrect during extended daylight saving periods. You must rerun the Time Zone Data Update Tool in order to update these appointments.

Q: What happens if I run the Time Zone Data Update Tool on one of the Microsoft SharePoint Portal Server calendars to which I am connected?

A: Connected SharePoint calendars are read-only in Outlook 2003. The Time Zone Data Update Tool or the Exchange tool will incorrectly modify these calendar items. Additionally, these modifications will not be pushed to the SharePoint server. Therefore, the two calendars will be unsynchronized. However, this issue will not occur as a default condition. This is because it is a custom action to run the Time Zone Data Update Tool on a connected SharePoint calendar in Outlook 2003.

If you are running Outlook 2007, and if you synchronize with Microsoft Office SharePoint Server 2007, recurring appointments that you created that start in calendar year 2006 are updated correctly in Outlook 2007. However, when you view the recurring appointments in SharePoint Server 2007, they are displayed as one hour earlier. Recurring appointments that start in calendar year 2007 are displayed the same in Outlook 2007 and in SharePoint Server 2007.

Note SharePoint Portal Server does not rely on the time zone rules of the client computer. SharePoint Portal Server relies on its own hard-coded list of time zone rules. These rules are based on the year that the recurrence pattern starts.

Q: Where can I learn more about the data structures being updated by the Time Zone Data Update Tool?

A: The Outlook 2007 time zone structures are documented on the Microsoft Developer Network (MSDN) blog. To view this blog, visit the following Microsoft Web site:

http://blogs.msdn.com/stephen_griffin/archive/2006/12/06/outlook-2007-timezone-structures.aspx

Q: Does the Time Zone Data Update Tool require administrator rights to install?

A: Yes. The tool is exactly like any other program. It requires local administrator rights on the local computer.

Q: Can a delegate run the Time Zone Data Update Tool against their manager’s calendar?

A: No. You must be an Exchange Administrator or the owner of the mailbox to run the Time Zone Data Update Tool.

'''Q: I have Outlook installed on Terminal Server. Do I have to do anything special to update the terminal server or the users on the terminal server?'''

A: No special considerations apply to Terminal Server users who connect to Outlook by using a Terminal Server session. You can regard the Terminal Server session as any other client computer.

Q: As an attendee, when I click the Calendar''' button of a meeting in my inbox that was updated by Tzmove.exe, the calendar moves to August 31, 4500. Why doesn't the calendar move to the correct date?'''

A: In some scenarios in Exchange 5.5, the meeting update might be missing some legacy properties which causes this behavior in Outlook. The attendee should click Accept in the updated meeting, and the meeting will be correctly added in the calendar.

Complete table of possible error codes
The following table is a complete list of possible error messages and the corresponding error codes. These are presented in their raw form. The Time Zone Data Update Tool may also generate MAPI errors. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

238119 List of Extended MAPI numeric result codes

<div class="references_section">

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

195900 How Outlook handles time zones for meeting requests

<div class="moreinformation_section">

Additional resources
For more information about the effects of the DST rule changes on products from Microsoft and about other time zone-related information, view the following Knowledge Base articles and Web sites.

General information
For general information about daylight saving time help and support, visit the following Microsoft Web site:

http://support.microsoft.com/gp/cp_dst

Microsoft Windows
For more information about Microsoft Windows and daylight saving time, click the following article numbers to view the articles in the Microsoft Knowledge Base:

921095 FIX: U.S. daylight saving time changes in 2007 do not occur on the correct day on Windows CE 5.0-based devices

922347 FIX: The Windows CE .NET 4.0-based device does not correctly adjust the clock for daylight saving time

923027 How to update daylight saving time for the United States, Canada, and Mexico in 2007 on Windows CE-based devices

923953 How to configure daylight saving time for the United States and Canada in 2007 and in subsequent years on Windows Mobile-based devices

Microsoft Exchange Server
For information about the Exchange Calendar Update Tool, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=A9336886-4B28-4010-9416-36D38429438D

For more information about Microsoft Exchange Server and daylight saving time, click the following article numbers to view the articles in the Microsoft Knowledge Base:

888606 Meetings are unexpectedly moved one hour ahead in Exchange 2000 Server

891629 The time of an appointment that is contained in an e-mail message is changed when the message is sent or received by an Exchange 2000 computer that uses the Microsoft Exchange Connector for Novell GroupWise

910268 Meetings are unexpectedly moved one hour ahead in the last week of October in Exchange Server 2003

912918 Users cannot send e-mail messages from a mobile device or from a shared mailbox in Exchange 2000 Server and in Exchange Server 2003

915577 How to incorporate Indiana's time zone change in Outlook e-mail clients in Exchange Server

916989 After you configure the Jerusalem time zone settings to match the transition dates for daylight saving time, meetings are moved ahead by one hour when a user accepts a meeting request by using a CDO program in Exchange Server 2003

926666 Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 2

928462 The time settings in Outlook Web Access on Exchange Server 2003 SP2 may not reflect the change to Western Australia daylight saving time during the transition period

928468 The time settings in Outlook Web Access on Exchange Server 2003 may not reflect the change to Western Australia daylight saving time during the transition period

941018 How to address daylight saving time by using the Exchange Calendar Update Tool

Microsoft Office and Outlook
For information about the Time Zone Data Update Tool for Microsoft Office Outlook, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=e343a233-b9c8-4652-9dd8-ae0f1af62568

For information about how to prepare Outlook calendar items for DST changes, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/outlook/HA102086071033.aspx

Other Microsoft programs
For more information about daylight saving time changes for Microsoft Dynamics CRM, click the following article numbers to view the articles in the Microsoft Knowledge Base:

913541 Microsoft Dynamics CRM does not reflect Australian daylight saving time changes for the year 2006

925874 An update for the 2007 daylight saving time changes is available for Microsoft Dynamics CRM 3.0 and for the Microsoft Dynamics CRM 3.0 client for Outlook

For more information about Windows Server Update Services and daylight saving time, click the following article number to view the article in the Microsoft Knowledge Base:

894199 Description of Software Update Services and Windows Server Update Services changes in content for 2007

For more information about Microsoft Windows SharePoint Services and daylight saving time, click the following article numbers to view the articles in the Microsoft Knowledge Base:

888253 How to configure time zone information in Windows SharePoint Services by modifying the Timezone.xml file

924881 Description of the update for Windows SharePoint Services: January 9, 2007

Non-U.S. time zones
For more information about daylight saving time in non-U.S. time zones, click the following article numbers to view the articles in the Microsoft Knowledge Base:

289502 Mexico City Time Zone Update for daylight saving time

317211 How to configure daylight saving time dates for Brazil

320034 2002 Mexico City time zone update for daylight saving time

886775 How to change the daylight saving time program for the new 2004 to 2005 schedule in the Uruguay time zone

909915 Microsoft products do not reflect Australian daylight saving time changes for the year 2006

929120 Windows Server 2003-based computers and Windows XP-based computers that are set to the West Australia time zone do not change to daylight saving time on December 3, 2006

Third-party products
For information about daylight saving and third-party products that are frequently used together with Exchange Server, visit the following third-party Web sites: <ul> <li>For information about BlackBerry Enterprise Server for Microsoft Exchange, visit the following Web site:

http://www.blackberry.com/select/dst2007/resolutions/enterpriseserver/exchange/index.shtml

</li> <li>For information about BlackBerry devices, visit the following Web site:

http://www.blackberry.com/DST2007/patch/index2.shtml

</li></ul>

More general information
<ul> <li>For general information about daylight saving time, visit the following Web site:

http://en.wikipedia.org/wiki/Daylight_savings_time

</li> <li>For general information about daylight saving time around the world, visit the following Web site:

http://en.wikipedia.org/wiki/Daylight_saving_time_around_the_world

</li> <li>For general information about the effect that the 2007 time zone changes may have on computers in Canada, in the United States, and in Bermuda, visit the following Web site:

http://www.reganfamily.ca/dst

</li> <li>For general information about the history of daylight saving time, visit the following Web sites:

http://www.seizethedaylight.com/dst

http://www.npr.org:80/templates/story/story.php?storyId=4572036

</li></ul>

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

<div class="moreinformation_section">

Technical revisions
The revision numbers and review dates for this article may reflect minor editorial or structural revisions to this content. The major technical revisions to this content are listed in this table.

Additional query words: fall back spring ahead OLK OLK2000 OLK2002 OLK2003 OL2007

Keywords: kbhowto kbexpertisebeginner KB931667

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.