Microsoft Daylight Saving Time & Time Zone Blog : General Questions

Questions Regarding /PHYSICALMOVE

atsim — Wed, 19 Sep 2007 19:57:11 GMT

In preparation for a potential time zone move, customers may use the Outlook Time Zone Data Update Tool with the /PHYSICALMOVE switch, which has promoted some questions as noted here:

Q: Are there negative effects from running the tool multiple times on the same mailbox? (i.e., on the first pass, original time zone = Central & new time zone = Eastern; on the second pass, original time zone = Easter & new time zone = Central)

A: There should be no negative side-effects. In the example here, this would make sense if someone moved from the Central to Eastern time zone and then, some time later, moved back.

Q: Will the tool behave differently if there are appointments created using Blackberry, Live Meeting, OWA, etc…?

A: The intention is that all items are updated correctly.

Q: Can this switch be used when running the Exchange version of the tool?

A: Unfortunately, no. This is functionality that we did not include in the most recent release. Customers may run into issues related to new time zones, as may be the case in Venezuela (which is moving to a newly created time zone, -4:30 GMT - see DST Hot Topics and Latest News for more information). The recommended and supported way to move between time zones is using the client-side tool.

Q: I’ve tried researching internally and haven’t found much documentation on the /PHYSICALMOVE switch. Is there a brief overview of how it works?

A: At a basic level, the /PHYSICALMOVE switch is not that much different than rebasing with the Outlook Time Zone Data Update Tool: identify future items targeted at the source time zone and, if we detect that being in the destination time zone would affect their start or end time, update them such that they correctly reflect local time in the destination time zone.

DST VIDEOS NOW AVAILABLE!

atsim — Fri, 14 Sep 2007 22:08:45 GMT

Steve Justice (Senior Escalation Engineer) and Joel Schaeffer (Escalation Engineer) from Microsoft Product Support have put together some instructional videos to assist your DST planning efforts.

On-Demand (hosted by Channel9.MSDN.com)
These videos can be streamed on-demand for viewing.

DST: Cumulative Time Zone Update for Microsoft Windows
http://channel9.msdn.com/ShowPost.aspx?PostID=341535

DST: Using the Outlook v2.0 Time Zone Data Update Tool
http://channel9.msdn.com/ShowPost.aspx?PostID=341649

DST: How to Address Daylight Saving Time in Exchange Server by Using the Exchange Calendar Update Tool v2.0
http://channel9.msdn.com/ShowPost.aspx?PostID=341747

Microsoft Download Center (table of contents included – use as a reference)
These videos include a web-based table of contents that allow them to be used as an offline reference.

VIDEO: Cumulative Time Zone Update for Microsoft Windows and Windows Mobile
http://www.microsoft.com/downloads/details.aspx?FamilyId=1E55473C-80FF-4E87-A48F-3BC872EF39AA&displaylang=en

VIDEO: Using the Time Zone Data Update Tool for Microsoft Office Outlook v2.0
http://www.microsoft.com/downloads/details.aspx?FamilyId=1A511C92-A45B-46ED-9848-64349EEBD040&displaylang=en

VIDEO: Using the Time Zone Data Update Tool for Microsoft Exchange Server v2.0
http://www.microsoft.com/downloads/details.aspx?FamilyId=A05519EF-B698-4A60-8292-D22D35393E43&displaylang=en

Enjoy!

The Microsoft DST Team

[JS]

Q: Updates to Microsoft Office 2004 for Mac 11.3.7 update and Entourage?

atsim — Thu, 13 Sep 2007 07:35:03 GMT

Q: I checked http://support.microsoft.com/gp/dst_prodlist#Ent and under Entourage it states to download Microsoft Office 2004 for Mac 11.3.7 update.

I checked the KB for the update and it mentioned nothing about DST. I checked the readme for the download and it updates the following 3 files:

Microsoft Component Plugin
Microsoft Excel
Microsoft Ole Automation

Can someone explain how updating to Mac 11.3.7 updates Entourage for DST this Fall?

A: The Entourage product group has noted that the download for the Microsoft Office 2004 for Mac 11.3.7 Update includes most recent updates including the most recent changes to DST update as of August 31, 2007.

Product updates are cumulative, and customers should visit the Office 2004 download page for the latest product information and updates.

See the MacBU's team blog post on the subject at http://blogs.msdn.com/macmojo/archive/2007/01/10/the-times-they-are-a-changin.aspx (as noted earlier here).

[M3]

Q: Updates to Exchange 2003 SP1 AND BES Blackberry server advice?

atsim — Thu, 13 Sep 2007 07:20:25 GMT

Q: We currently run Exchange 2003 SP1, and also have Blackberry server. Up to now our understanding was that we need to apply the standard DST O/S fix to the Exchange server, but would only need to install the CDO patch if we had applications that use CDO – and Microsoft was only releasing the CDO patch for Exchange 2003 SP2 (KB937653).

We have the Blackberry notice http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB14176&sliceId=SAL_Public&dialogID=47758087&stateId=0%200%2023172424 about updating CDO.

We have now seen http://support.microsoft.com/kb/940123 which seems to show a CDO DST fix for Exchange 2003 SP1.

Instead of migrating now to Exchange SP2 now, could we use KB940123?

A: This is the correct fix for an Exchange 2003 SP1 installation.

In this case the customer is installing it on on Blackberry Exchange Server (aka BES). We suggest that customers contact RIM to find out what RIM recommends and supports for their products in this scenario.

Otherwise, the customer may update the Exchange 2003 components on the BES computer to SP2 and then apply 937653 (as RIM states in the link).

[JM]

Q: Is there any reason not to use the /forcerebasesuppressallupdates switch with tzmove?

atsim — Thu, 13 Sep 2007 07:02:20 GMT

Q: Is there any reason not to recommend the use of the /forcerebasesuppressallupdates switch with tzmove? And what is the likely scenario why someone would get the error below?

Get the following error with the /FORCEREBASESUPPRESSALLUPDATES switch.

A: We do not recommend that customers use the /forcerebasesuppressallupdates switch with tzmove because ALL appointments in a users Calendar are updated regardless of who the organizer of the meeting is. In addition, no updates to meetings are sent out to any attendees.

The difficulty that is introduced due to these two factors is that every Calendar that has meetings in the organization has to have the /forcerebasesuppressallupdates command-line switch ran on their Calendar within a very short period of time. It’s difficult to coordinate this and it goes against how Outlook is designed to update meetings through meeting updates.

One example of the type of problem you could encounter would be if one user sent out a meeting series to 10 people and 5 of them already had the /forcerebasesuppressallupdates switch ran. When the remaining 5 have /forcerebasesuppressallupdates ran then those appointments will be at a different time than the other attendees and possibly even different than the organizer. In addition, meeting attendees that are outside of the Exchange organization would not get meeting updates so they would likely have to manually move those appointments or the appointments would be incorrect. There are other scenarios but you probably get the point.

As far as running the tool from the command-line. The syntax you are looking for is as follows with “User” being the mailbox owner:

tzmove /Q /FORCEREBASESUPPRESSALLUPDATES \\Mailbox - User\Calendar

Since you are using the /Q switch then you should look at the TZMOVE events in the Application Event log for information regarding how the tool executed.

Additional information:

/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 DST 2006 rules. The rebase occurs regardless of who the organizer is. This mode will not send any updates for any reason.

(SJ)

Q: What is the correct syntax when a rebasing a second calendar in a user's mailbox?

atsim — Thu, 13 Sep 2007 06:23:00 GMT

Q: I have had this question come in from a customer around rebasing of calendars:

In the Knowledgebase article KB931667: DST using Outlook TZmove, the following is stated:

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.

My question is about syntax of the command.

Which bit of the command do I change for the second user?

Example, if user Mary holds a second calendar for Joe then:

When Mary is logged in, is the command

tzmove.exe -Q \\Mailbox - User\Joe

tzmove.exe -Q \\Mailbox - Mary\Joe

or some other command string.

Seeing that we have a large number of PAs that have an even larger number of second calendars for bosses, meeting rooms and other resources, getting this command right is imperative.

What is the correct syntax please?

A: If the Calendar “Joe” is in Mary’s Mailbox and as a result is truly a “second calendar” in her Mailbox then the command is:

tzmove –q \\Mailbox – Mary\Joe

You can view the Application Event Log to verify that the command ran successfully by looking at the events that are logged for TZMOVE. You can also view the log file named “Outlook Time Zone Update.log” that is in the users %TEMP% folder to see detailed information about actions that tzmove performed.

[JS]

Q: What steps are needed to install the Exchange Calendar Update tool version 2

atsim — Thu, 13 Sep 2007 06:18:00 GMT

Q: I’m attempting to install the new Exchange Calendar Update tool on a system that had the previous version installed – I removed the previous version via Add/Remove Programs, but when I execute the installation for the new version, I get an option to repair or remove and choosing either option results in an error indicating ‘This action is only valid for products that are currently installed’. Can someone advise as to what kind of clean up may be needed to get the new version to install successfully?

A: If you have uninstalled the old Exchange tool, then look for and remove the following key if it exists:

HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{9F73F6F4-F3A0-4B0A-A52B-D3B622DE6024}

Try the install of the updated Exchange tool again. The installation should now work after removal of this key.

Q: if we applied Microsoft daylight saving time updates this past Spring, are we covered for the Fall?

atsim — Thu, 06 Sep 2007 19:55:00 GMT

Q: "If we updated for this [US and Canadian daylight saving time] change this spring, we should be covered for the fall time change, correct?"

A: Generally, the answer is yes. As noted here, it depends: we recommend that companies review their specific situation. Companies that do not have a presence in an affected time zone may find that no DST updates are required. However, Microsoft strongly recommends that customers apply the time zone updates for all affected products. There are a couple of reasons for this:

First, customers may have users who travel to an affected time zone, and as such, their applications could be affected by not having the current time zone updates installed on their client machines.
Second, applying the current DST updates to all machines and applications keeps their environment up-to-date and consistent with worldwide changes. This could be important when communicating with another end user or company in an affected time zone, or where different IT environments come together and coexist.

Overall, Microsoft strongly recommends DST patch installation on all affected systems, devices and applications to ensure consistency with the world’s current time zone information. Customers should review the updates available and posted at http://support.microsoft.com/gp/dst_prodlist for the latest and updated information of Microsoft products affected by daylight saving time, as well as the main DST and TZ page at http://www.microsoft.com/dst2007.

Customers who need the latest updates for the recently-added and revised countries (new time zone rules for Jordan and New Zealand, for example), should get the latest update. Consumers may update their PCs by visiting Microsoft Update at http://www.update.microsoft.com/. Network managers and sysadmins can get the latest Windows OS update (KB 933360) as an "Update Rollup" via WSUS as noted in this post.

Again, there are scenarios where updates and patches are not required, but Microsoft strongly recommends DST patch installation on all affected systems, devices and applications to ensure consistency with the world’s current time zone information.

Q: Is there a list of the time zones and daylight saving time changes in Windows?

atsim — Wed, 22 Aug 2007 07:41:00 GMT

Q: Is there a list of the time zones [and daylight saving time/ summer time] changes in Windows?"

A: yes, there is a list of all changes included in KB article 933360, "August 2007 cumulative time zone update for Microsoft Windows operating systems," that notes that the following changes have been made since the previous Windows cumulative time zone update in February (KB article 931836) :

Caucasus Standard Time: Changes display name to Caucasus Standard Time as cities in the previous display name have separate time zones, and removes DST settings.
Armenian Standard Time: Creates a new time zone for Armenia to better align with different DST changes in the Caucasus region.
New Zealand Standard Time: Adjusts DST start dates and end dates according to changes signed in to law after the prior cumulative time zone update was created (February 2007).
GTB Standard Time: Corrects the display name for GTB Standard Time on Windows Server 2003 SP2 to include Bucharest.
Jordan Standard Time: Adjusts DST start times, end times, and dates according to changes signed in to law after the prior cumulative time zone update was created (February 2007).

A list of the display names and GMT offsets are noted here for your review...

Registry subkey name	Display name	Daylight name	Standard name	DST start	DST end
Alaska Standard Time	(GMT-09:00) Alaska	Alaskan Daylight Time	Alaskan Standard Time	Second Sunday in March at 02:00:00	First Sunday in November at 02:00:00



Armenian Standard Time	(GMT +04:00) Yerevan	Armenian Daylight Time	Armenian Standard Time	Last Sunday in March at 2:00:00 AM	Last Sunday in October 3:00:00 AM



Atlantic Standard Time	(GMT-04:00) Atlantic Time (Canada)	Atlantic Daylight Time	Atlantic Standard Time	Second Sunday in March at 02:00:00	First Sunday in November at 02:00:00



AUS Eastern Standard Time	(GMT+10:00) Canberra, Melbourne, Sydney	AUS Eastern Daylight Time	AUS Eastern Standard Time	Unchanged	Last Sunday in March at 03:00:00



Azerbaijan Standard Time	(GMT+04:00) Baku	Azerbaijan Daylight Time	Azerbaijan Standard Time	Last Sunday in March at 04:00:00	Last Sunday in October at 05:00:00



Caucasus Standard Time	(GMT +04:00) Caucasus Standard Time	Caucasus Daylight Time	Caucasus Standard Time	removed	removed



Cen. Australia Standard Time	(GMT+09:30) Adelaide	Cen. Australia Daylight Time	Cen. Australia Standard Time	Unchanged	Last Sunday in March at 03:00:00



Central Brazilian Standard Time	(GMT-04:00) Manaus	Central Brazilian Daylight Time	Central Brazilian Standard Time	First Sunday in November at 00:00:00	Last Sunday in February at 00:00:00



Central Standard Time	(GMT-06:00) Central Time (US & Canada)	Central Daylight Time	Central Standard Time	Second Sunday in March at 02:00:00	First Sunday in November at 02:00:00



Central Standard Time (Mexico)	(GMT-06:00) Guadalajara, Mexico City, Monterrey	Central Daylight Time (Mexico)	Central Standard Time (Mexico)	First Sunday in April at 02:00:00	Last Sunday in October at 02:00:00



E. Europe Standard Time	(GMT+02:00) Minsk	E. Europe Daylight Time	E. Europe Standard Time	Last Sunday in March at 02:00:00	Last Sunday in October at 03:00:00



E. South America Standard Time	(GMT-03:00) Brasilia	E. South America Daylight Time	E. South America Standard Time	First Sunday in November at 00:00:00	Last Sunday in February at 00:00:00



Eastern Standard Time	(GMT-05:00) Eastern Time (US and Canada)	Eastern Daylight Time	Eastern Standard Time	Second Sunday in March at 02:00:00	First Sunday in November at 02:00:00



Egypt Standard Time	(GMT+02:00) Cairo	Egypt Daylight Time	Egypt Standard Time	Last Thursday in April at 23:59:59.999	Last Thursday in September at 23:59:59.999



Georgian Standard Time	(GMT+03:00) Tbilisi	Georgian Daylight Time	Georgian Standard Time	Removed	Removed



Greenwich Standard Time	(GMT) Casablanca, Monrovia, Reykjavik	Greenwich Daylight Time	Greenwich Standard Time	Not applicable	Not applicable



GTB Standard Time	(GMT+02:00) Athens, Bucharest, Istanbul	GTB Daylight Time	GTB Standard Time	Last Sunday of March at 3:00:00	Last Sunday in October at 04:00:00



Iran Standard Time	(GMT+03:30) Tehran	Iran Daylight Time	Iran Standard Time	Removed	Removed



Israel Standard Time	(GMT+02:00) Jerusalem	Jerusalem Daylight Time	Jerusalem Standard Time	March 30, 2007 at 02:00:00	September 16, 2007 at 02:00:00



Jordan Standard Time	(GMT+2:00) Amman	Jordan Daylight Time	Jordan Standard Time	Last Thursday in March at 11:59:59	Last Friday in October at 01:00:00



Middle East Standard Time	(GMT+02:00) Beirut	Middle East Daylight Time	Middle East Standard Time	Last Sunday in March at 00:00	Last Saturday in October at 23:59:59.999



Montevideo Standard Time	(GMT-03:00) Montevideo	Montevideo Daylight Time	Montevideo Standard Time	First Sunday in October at 02:00:00	Second Sunday in March at 02:00:00



Mountain Standard Time	(GMT-07:00) Mountain Time (US and Canada)	Mountain Daylight Time	Mountain Standard Time	Second Sunday in March at 02:00:00	First Sunday in November at 02:00:00



Mountain Standard Time (Mexico)	(GMT-07:00) Chihuahua, La Paz, Mazatlan	Mountain Daylight Time (Mexico)	Mountain Standard Time (Mexico)	First Sunday in April at 02:00:00	Last Sunday in October at 02:00:00



Myanmar Standard Time	(GMT+06:30) Yangon (Rangoon)	Myanmar Daylight Time	Myanmar Standard Time	Not applicable	Not applicable



Namibia Standard Time	(GMT+02:00) Windhoek	Namibia Daylight Time	Namibia Standard Time	First Sunday in April at 02:00:00	First Sunday in September at 02:00:00



New Zealand Standard Time	(GMT+12:00) Auckland, Wellington	New Zealand Daylight Time	New Zealand Standard Time	Last Sunday in September at 02:00:00	First Sunday in April at 03:00:00



Newfoundland Standard Time	(GMT-3:30) Newfoundland	Newfoundland Daylight Time	Newfoundland Standard Time	Second Sunday of March at 00:01:00	First Sunday of November at 00:01:00



Pacific SA Standard Time	(GMT-04:00) Santiago	Pacific SA Daylight Time	Pacific SA Standard Time	Second Saturday in October at 23:59:59.999	Second Saturday in March at 23:59:59.999



Pacific Standard Time	(GMT-08:00) Pacific Time (US & Canada)	Pacific Daylight Time	Pacific Standard Time	Second Sunday in March at 02:00:00	First Sunday in November at 02:00:00



Pacific Standard Time (Mexico)	(GMT-08:00) Tijuana, Baja California	Pacific Daylight Time (Mexico)	Pacific Standard Time (Mexico)	First Sunday in April at 02:00:00	Last Sunday in October at 02:00:00



SA Pacific Standard Time	(GMT-05:00) Bogota, Lima, Quito, Rio Branco	SA Pacific Daylight Time	SA Pacific Standard Time	Not applicable	Not applicable



Sri Lanka Standard Time	(GMT+05:30) Sri Jayawardenepura	Sri Lanka Daylight Time	Sri Lanka Standard Time	Not applicable	Not applicable



Tasmania Standard Time	(GMT+10:00) Hobart	Tasmania Daylight Time	Tasmania Standard Time	Unchanged	Last Sunday in March at 03:00:00



W. Australia Standard Time	(GMT+08:00) Perth	W. Australia Daylight Time	W. Australia Standard Time	Last Sunday in October at 02:00:00	Last Sunday in March at 03:00:00

Important notes from this KB...

This update supersedes and replaces update KB931836, released in January 2007. This update also includes additional time zone changes that were signed in to law after update KB931836 was created. Customers who have already deployed update KB931836 should evaluate whether any of the five specific time zone changes that are addressed in the update described by this Microsoft Knowledge Base (KB) article merit deploying this update immediately. If systems are not directly affected, you can schedule deployment at the next available opportunity. We recommend that all customers standardize on the most current Windows cumulative time zone update to guarantee the consistency of the time zone database on all systems.
Before you apply the update that is described by this article, be aware of potential issues that may affect Microsoft Office Outlook. For more information about these issues, click the following article number to view the article in the Microsoft Knowledge Base: 931667 (http://support.microsoft.com/kb/931667/) How to address the daylight saving time changes in 2007 by using the Time Zone Data Update Tool for Microsoft Office Outlook
If you are running Microsoft Exchange Server in an Information Technology (IT) environment, you must take additional measures to guarantee the correct operation of Exchange Server. For more informationabout the Exchange daylight saving time (DST) update, click the following article number to view the article in the Microsoft Knowledge Base: 926666 (http://support.microsoft.com/kb/926666/) Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 2

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, DST. 629,244; 954,983; 1,750,000

Will update KB 933360 be released for WSUS deployment and will it be classified as an Update Rollup?

atsim — Sat, 18 Aug 2007 08:33:00 GMT

Q: Will update KB 933360 be released for WSUS deployment and will it be classified as an Update Rollup?

A: Yes, Microsoft Windows operating systems KB 933360 is now available (http://support.microsoft.com/kb/933360/), "August 2007 cumulative time zone update for Microsoft Windows operating systems." KB 933360 will be issued as an "Update Rollup" and available via WSUS. (This Knowledge Base article replaces KB article 931836.)

To see such updates in WSUS, go to "Update Classifications" and select "change," then check "Update Rollups" and sync.

The only correction is that the KB that will be released to WSUS on August 28th, 2007.

As we have done in the past, we will ask the WSUS team to post a blog a few days before release to remind WSUS admins that Update Roll-ups are not displayed by default and they must take the steps outline below if they are not downloading Update Roll-ups.

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, DST. 641,827; 965,091; 1,472,886

August 2007 cumulative time zone update for Microsoft Windows operating systems now available

atsim — Mon, 13 Aug 2007 21:26:00 GMT

Please note: If you referenced the February 2007 cumulative time zone update for Microsoft Windows operating systems KB article 931836, please note that there is a new update now available. This Knowledge Base article has been replaced by the update that is described in Microsoft Knowledge Base article, KB 933360 (http://support.microsoft.com/kb/933360/), "August 2007 cumulative time zone update for Microsoft Windows operating systems."

To make sure that Microsoft Windows has the latest time zone data, install the update that is described in Microsoft Knowledge Base article 933360.

Note: You do not have to uninstall the update that is described in this Microsoft Knowledge Base article before you install the update that is described in Microsoft Knowledge Base article 933360.

For more information, click the following article number to view the article in the Microsoft Knowledge Base, KB 933360 (http://support.microsoft.com/kb/933360/), "August 2007 cumulative time zone update for Microsoft Windows operating systems."

Additional information on past DST and TZ updates: To be clear on the time zones added to this update, and whether or not time zones added in past KBs (931836) were included in the update: Yes, this includes the TZ releases for areas and provinces impacted (such as NF): it's a cumulative update that also includes the updates from prior OS updates, including 931836, I believe.

From the KB 933360 ...

Updates from the previous cumulative Windows time zone update

The following changes have been made since the previous Windows cumulative time zone update, described in KB931836:

•	Caucasus Standard Time Changes display name to Caucasus Standard Time as cities in the previous display name have separate time zones, and removes DST settings.
•	Armenian Standard Time Creates a new time zone for Armenia to better align with different DST changes in the Caucasus Region.
•	New Zealand Standard Time Adjusts DST start and end dates according to changes signed in to law after the prior cumulative time zone update was created (February 2007).
•	GTB Standard Time Correct the display name for GTB Standard Time on Windows Server 2003 SP2 to include Bucharest.
•	Jordan Standard Time Adjusts DST start and end times and dates according to changes signed in to law after the prior cumulative time zone update was created (February 2007).

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, DST. 627,827; 936,312; 1,472,886

Help desk guidelines on Daylight Saving Time for Microsoft Office Outlook Calendars

atsim — Wed, 07 Mar 2007 22:15:00 GMT

The Exchange team has posted a helpdesk-oriented document that provides recommendations and prescriptive guidance for updating Outlook calendars to comply with the Daylight Saving Time (DST) 2007 rule changes. The goal is to provide an Outlook user with a "personal touch" experience to help them understand what is happening with their calendar. Enterprise and business customers may find this helpful when dealing with end user questions or answering their helpdesk calls on the subject.

General References

Main Microsoft DST site - www.microsoft.com/dst2007
DST Technical chats FAQ - blogs.technet.com/dst2007
Webcasts and Technical Chats - http://support.microsoft.com/gp/dst_webcasts
Step by Step Videos - http://msexchangeteam.com/archive/2007/02/21/435543.aspx#435553

Tools Availability

Outlook Time Zone Data Update Tool - http://support.microsoft.com/kb/931667/en-us
Outlook Time Zone Data Update Tool patch – http://support.microsoft.com/kb/933146/en-us
Exchange Time Zone Data Update Tool - http://support.microsoft.com/kb/930879/en-us

More information

For more info on updating Outlook calendars, see the full help desk guidance at http://msexchangeteam.com/archive/2007/03/06/436731.aspx

Can you call Support for help even though you do not have a support contract?

atsim — Wed, 07 Mar 2007 21:28:00 GMT

Q: If there any issues with the DST changes, can you call Support for help even though you do not have a support contract? I've read somewhere that Microsoft is offering support for DST changes only.
A: You can call support for assistance with problems related to the DST changes. Phone numbers to call are located here: http://support.microsoft.com/

How do you determine if the appointments are off before the rebase and how do you determine if they are right after the rebase?

atsim — Wed, 07 Mar 2007 21:28:00 GMT

Q: If your workstation has been patched and you have appointments past March 10th. How do you determine if the appointments are off before the rebase and how do you determine if they are right after the rebase?
A: Appointments created before patching the client are created using DST2006 rules. Appointments created after patching the client are created with DST2007 rules. When you run the Outlook or Exchange tools to rebase your calendar, it will move all recurring meetings made with DST2006 rules and all single-instance meetings (since DST rules are not recorded for them until after rebasing). Concerning it being correct, we advise that the meeting information be placed in the subject or body; if they didn't do that, you have not option but to consult the organizer.

Do the DST updates apply to North America only?

atsim — Wed, 07 Mar 2007 21:27:00 GMT

Q: The DST updates applied to North America only or worldwide, for example if I have a server in Singapore
A: The DST updates contain updated time zone information for several time zones around the world (not just US time zones). Because of that we recommend applying it to all servers worldwide. This is particularly important for Exchange servers as even though they may be outside of an affected time zone, they may process creation requests for appointments within affected time zones.