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

Glossary of terms

• 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.

Back to the top

What you should do

Back to the top

Microsoft Outlook

• Microsoft Office Outlook 2007
• Microsoft Office Outlook 2003
• Microsoft Outlook 2002
• Microsoft Outlook 2000

Back to the top

Tools that you can use to update DST in calendaring applications

Collapse this imageExpand this image

• 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

Back to the top

Summary of the key changes in the Time Zone Data Update Tool 3.0 for Outlook

• Ability for the user to access and run the tool from the Windows Start menu.
• All the hotfixes that were made to the Time Zone Data Update Tool 2.0.
• Key fixes, most notably those that allow for more accurate updates in Israel, Iraq, Brazil, and Latin America.
  
  Important Note The behavior of the previously released versions of the tool (1.0.2 and 2.0) is incorrect in various ways when the tool is used for New Zealand, Western Australia, Brazil, and Latin America. Any use of these versions 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.

Back to the top

General sequence of update actions

1. 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:
   955839  (http://support.microsoft.com/kb/955839/ ) December 2008 cumulative time zone update for Microsoft Windows operating systems
2. 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:
   955839  (http://support.microsoft.com/kb/955839/ ) December 2008 cumulative time zone update for Microsoft Windows operating systems
   950885  (http://support.microsoft.com/kb/950885/ ) A March 2008 cumulative daylight saving time (DST) update is available for Windows Mobile-based devices
3. 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.
   • 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.
   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  (http://support.microsoft.com/kb/941018/ ) How to address daylight saving time by using the Exchange Calendar Update Tool
4. 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 Server 2007
   
   941421  (http://support.microsoft.com/kb/941421/ ) Description of Update Rollup 5 for Exchange Server 2007
   Update Rollup 4 for Exchange Server 2007 includes the following DST fixes:
   • 937656  (http://support.microsoft.com/kb/937656/ ) You experience problems in Outlook Web Access for Exchange 2007 after daylight saving time (DST) starts in New Zealand in 2007
   • 932561  (http://support.microsoft.com/kb/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
   Exchange Server 2003 SP2
   
   926666  (http://support.microsoft.com/kb/926666/ ) Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 2
   931915  (http://support.microsoft.com/kb/931915/ ) Update for daylight saving time changes in Newfoundland in 2007 for Exchange Server 2003 Service Pack 2
   929895  (http://support.microsoft.com/kb/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  (http://support.microsoft.com/kb/937653/ ) You experience one or more issues in Exchange Server 2003 after the daylight saving time period for New Zealand changes in 2007
   Exchange Server 2003 SP1
   
   940123  (http://support.microsoft.com/kb/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.

For small business, home, or consumer computer users who run Windows and Outlook but not Exchange Server

1. 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:
   955839  (http://support.microsoft.com/kb/955839/ ) December 2008 cumulative time zone update for Microsoft Windows operating systems
2. 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 (http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568)

Back to the top

Differences between the Outlook tool and the Exchange tool

For individual users

Back to the top

How to minimize the effect of the extended DST period

1. 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
2. Consider any calendar items in the extended DST period to be suspect. If you are not sure, verify the correct time with the organizer.
3. 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:
   1. Apply the Windows update that contains the updated time zone definitions.
   2. Run the Time Zone Data Update Tool.

Back to the top

Why the Time Zone Data Update Tool is required

• 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.

Back to the top

The effects that occur when the Time Zone Data Update Tool is not run

How to manually update calendar items

• 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.

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.

Recurring item exceptions may be lost after calendars are updated

Back to the top

Different scenarios in Outlook

Calendar items that are created in a Mexican time zone are not detected by the tool

• GMT -08:00 Pacific Time (US & Canada)
• GMT -08:00 Tijuana, Baja California

• 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.

• 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.

Back to the top

Considerations for users in time zones that are not affected by time zone changes

• 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 has updated time zone 2007 rules during extended periods.

Back to the top

How to install and to use the Time Zone Data Update Tool

1. 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:
   955839  (http://support.microsoft.com/kb/955839/ ) December 2008 cumulative time zone update for Microsoft Windows operating systems
2. 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:
   • When a user who has standard user permissions double-clicks OutlookTimeZoneMove.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.
   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:
   • When a user who has standard user permissions double-clicks OutlookTimeZoneMove.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.
   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.
3. The Time Zone Data Update Tool can be launched from the Windows Start menu. The tool can be found under All Programs\ Microsoft Office Outlook Tools\ Time Zone Data Update Tool\ Time Zone Daylight Saving Update Mode.
   
   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.
4. Click OK.

Back to the top

The Time Zone Data Update Tool will not run on a computer that does not have Outlook installed

Back to the top

How to determine whether the Time Zone Data Update Tool completed successfully

Event Type: Information
Event Source: TZMOVE
Event Category: None
Event ID: 32
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The Time Zone Data Update tool for Microsoft Office Outlook completed. 1 items updated in 'Mailbox - UserName'. Additional information in %Temp%\Outlook Time Zone Update.log.

Back to the top

Detailed behavior of the Time Zone Data Update Tool in specific situations

Update mode

• Outlook 2003
• Outlook 2002
• Outlook 2000
• Outlook Web Access
• Exchange Server 2003
• Mobile devices

Command-line parameter options

1. 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.
2. 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:
   • For a 32-bit OS, type the following command:
     “%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe” /quiet
   • For a 64-bit OS, type the following command:
     “%PROGRAMFILES (x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe” /quiet

1. Click Start, click Run, type %temp%, and then click OK.
2. Locate the "Time Zone Data Update Tool for Microsoft Office Outlook(#).log" file and the "Outlook Time Zone Update.log" file.

Back to the top

Move mode

When to change the Outlook home calendar time zone

• 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.

Differences between a time zone move operation and a time zone update operation

• 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.
• Some 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 /ONLYRECURRING option is not supported. The following table indicates which command-line options are supported for the time zone move operation:
  
  Collapse this tableExpand this table

  Command-line option	Supported in time zone move operation?
  /FORCEREBASESUPPRESSALLUPDATES	Yes
  /FORCEREBASESUPPRESSEXCHANGEUPDATES	Yes
  /FORCEREBASESUPPRESSEXCHANGEUPDATES[:MaxDepth]	Yes
  /ONLYCREATEDPREPATCH:yyyy-mm-ddThh:mm:ssZ	No
  /REPORTINGMODE	Yes
  /ONLYRECURRING	No
  /MAXAPPTS	No
  /SENDRESOURCEUPDATES	Yes
  /IGNOREPATCHDATE	No

• 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 Outlook Time Zone Data Update tool for Microsoft Office Outlook tool by using "Permanent Time Zone Move Mode" in the Start menu.
• Alternatively, you can run the Time Zone Data Update Tool for Microsoft Office Outlook tool together with the /PHYSICALMOVE command-line option.

To perform a move operation

1. 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  (http://support.microsoft.com/kb/914387/ ) How to configure daylight saving time for Microsoft Windows operating systems
2. Change the time zone on the computer to the destination time zone.
3. 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 (http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568)
4. Select the Permanent Time Zone Move Mode in the Start menu under All Programs\ Microsoft Office Outlook Tools\ Time Zone Data Update Tool\. Alternatively you can 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:
   • For a 32-bit operating system, run the following command:
     "%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe" / PHYSICALMOVE
   • For a 64-bit operating system, run the following command:
     "%PROGRAMFILES(x86)%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe" / PHYSICALMOVE
5. 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.
6. 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.

Using the /Quiet option in a time zone move operation

Specifying the Original and New Time zone for a time zone move operation

Additional information for administrators

• Instead of downloading and installing the OutlookTimeZoneMove.exe program every time that you perform a move operation, create a local copy of the OutlookTimeZoneMove.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.

@echo off <path of OutlookTimeZoneMove.exe>\OutlookTimeZoneMove.exe /quiet "%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\OutlookTimeZoneMove.exe" /physicalMove @echo on 

• Replace <path of OutlookTimeZoneMove.exe> with the path of the OutlookTimeZoneMove.exe file that you obtained from the following Microsoft Web site:
  http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568 (http://www.microsoft.com/downloads/details.aspx?familyid=%20E343A233-B9C8-4652-9DD8-AE0F1AF62568)
• 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.

Reporting Mode

Additional command-lines

Scenarios

• /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.
• /ONLYCREATEDPREPATCH: UTC date and time
  
  This option configures the Outlook Time Zone Data Update tool to rebase the following:
  • All recurring items
  • The single-instance items that were created before the specified date
  • The single-instance items that were created before the dates of the knowledge base article IDs that are specified in a KB Input File.
  The UTC date and time must be specified in the following format:
  /ONLYCREATEDPREPATCH[: yyyy-mm-ddThh:mm:ss Z]
  The following is an example command-line:
  /ONLYCREATEDPREPATCH:2007-02-16T12:00:00Z

• 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

• 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.
• 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  (http://support.microsoft.com/kb/914387/ ) How to configure daylight saving time for Microsoft Windows operating systems
• 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.
• 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.
• Consider the following scenario:
  1. 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.
  2. You install the DST updates on the operating system. The system now has the new time zone rules.
  3. You manually update the calendar items by using the new DST rules.
  4. You run the Outlook Time Zone Data Update tool.
  5. The single-instance calendar item is rebased to the wrong time.
  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.
• 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:
  • 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.
  • 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.
  • 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.
• Consider the following scenario:
  1. An end-user installs the new Windows time zone update.
  2. The user creates some single-instance items under the new DST rules.
  3. The user uninstalls the Windows time zone update.
  4. The user creates more items under the previous DST rules.
  5. The user reinstalls the Windows time zone update.
  6. The user runs the Outlook Time Zone Data Update tool.
  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.

Scenario 2: Force rebase calendar items and suppress the calendar updates that result from the time zone rebasing

• /FORCEREBASESUPPRESSALLUPDATES
  
  This option is known as "SuppressAll" 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.
• /FORCEREBASESUPPRESSEXCHANGEUPDATES
  
  This option is known as "SuppressExchange" 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

• 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.
• 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:
  • 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.
  • 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.
• 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.
• 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:
  • 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.
• 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:
  • 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.
  Additionally, the following are examples of how you can have an SMTP address for an internal recipient:
  • You use the Add to Contacts feature to add a mobile phone number for a coworker.
  • 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.
  • 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.
• 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:
  1. The organizer and the attendee have a single-instance meeting in the delta time period.
  2. The Outlook Time Zone Data Update tool is run on the organizer’s mailbox first.
  3. The organizer sends an update for the meeting because of a change of location. This update uses the new DST rules.
  4. The attendee accepts the meeting update.
  5. The attendee rebases his or her calendar and causes the meeting to be one hour off.
  Or, consider the following scenario in which the attendee rebases first:
  1. The organizer and the attendee have a single-instance meeting in the delta time period.
  2. The Outlook Time Zone Data Update tool is run on the attendee’s mailbox first.
  3. The organizer sends an update for the meeting because of a change of location.
  4. Because the organizer controls the meeting, the meeting shifts back to the previous DST rules.
  5. The organizer rebases their calendar and causes the meeting to be one hour off.
  6. 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.
• 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.
• If outgoing requests are sent to Optional or Resource attendees, the requests may appear malformed when they are viewed.
• 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.

• 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

1. 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 (http://technet.microsoft.com/en-us/library/aa997184.aspx)
2. Install the Windows time zone DST 2007 update.
   
   For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   955839  (http://support.microsoft.com/kb/955839/ ) December 2008 cumulative time zone update for Microsoft Windows operating systems
3. 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.
4. 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.

• 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

• 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

• 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

• 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

• /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[: yyyy-mm-ddThh:mm:ss 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.
• /ONLYSTAMPEDITEMS
  
  This option is new to V3. It is used to rebase only items that have a time zone property stamped on them, and ignores unstamped items. This is an useful option in cases where a timezone definition has changed more than once in the same year, making it impossible for the tool to determine which rules were in place when the unstamped items were created or modified.
• /ONLYCREATEDBEFORE: yyyy-mm-ddThh:mm:ss Z
  
  This option is new to V3.This option can only be used with move mode.It configures the Outlook Time Zone Data Update tool to move to the new time zone all recurring items and only the single-instance items that are created before the specified date.
• /STAMPHOMETIMEZONE
  
  This option is new to V3. It stamps the local machine OS Time zone on the Outlook calendar as the home time zone if no home time zone is already stamped on the calendar. No item is adjusted when using this option.
• /FORCESTAMPHOMETIMEZONE
  
  This option is new to V3. It stamps the local machine OS Time zone on the Outlook calendar as the home time zone regardless whether a home time zone is already stamped on the calendar. No item is adjusted when using this option.

Suppress the Change Calendar Time Zone Tool in Microsoft Office Outlook 2007

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

Back to the top

Known issues and limitations

• 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.
• 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 "Applies to" section.
• 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.
• You cannot run the tool by opening the OutlookTimeZoneMove.exe package on a computer where the Time Zone Data Update Tool for Microsoft Office Outlook tool is already installed. To run the tool again after it has been installed, use the appropriate entry in the Start menu.
• Version 2.0 of the Outlook Time Zone Data Update Tool and earlier versions cannot correctly rebase any calendar item that was created in the Brasilia time zone. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  957498  (http://support.microsoft.com/kb/957498/ ) Outlook Time Zone Data Update Tool 2.0 and earlier versions of this tool do not correctly rebase any calendar item that was created in the Brasilia time zone

Back to the top

• 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 "Outlook Time Zone Update.log" file:

  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:
  1. Click Start, click Run, type Outlook.exe /cleanfreebusy, and then click OK.
  2. Examine the published Free/Busy information from another computer.
• 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  (http://support.microsoft.com/kb/909109/ ) In Outlook 2003, a user does not receive meeting updates if the user clicked the "Don't send a response" option in response to a forwarded meeting request
• 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.

Back to the top

Frequently Asked Questions (FAQs)

• 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 "pre-image" of the updated time zone. If the definition matches, the tool can rewrite the appointment by using the "new version" 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.

• 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

• 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.

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

• 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.

1. Right-click My Computer, and then click Properties.
2. Click the Advanced tab.
3. Click Environment Variables.
4. Under both user variables, for username and system variables, examine the list and find a variable called TZ. Remove this TZ variable, and then restart the computer.

Back to the top

Complete table of possible error codes

Back to the top

Additional resources

General information

Microsoft Windows

Microsoft Exchange Server

Microsoft Office and Outlook

Other Microsoft programs

Non-U.S. time zones

Third-party products

• 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 (http://www.blackberry.com/select/dst2007/resolutions/enterpriseserver/exchange/index.shtml)
• For information about BlackBerry devices, visit the following Web site:
  http://www.blackberry.com/DST2007/patch/index2.shtml (http://www.blackberry.com/DST2007/patch/index2.shtml)

More general information

• For general information about daylight saving time, visit the following Web site:
  http://en.wikipedia.org/wiki/Daylight_savings_time (http://en.wikipedia.org/wiki/Daylight_savings_time)
• 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 (http://en.wikipedia.org/wiki/Daylight_saving_time_around_the_world)
• 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 (http://www.reganfamily.ca/dst)
• For general information about the history of daylight saving time, visit the following Web sites:
  http://www.seizethedaylight.com/dst (http://www.seizethedaylight.com/dst)
  http://www.npr.org:80/templates/story/story.php?storyId=4572036 (http://www.npr.org:80/templates/story/story.php?storyId=4572036)

Back to the top