New Zealand 2007 Daylight Saving Changes : TZMove

New Zealand time zone differs between Windows Vista and down-level Windows OSes - 1st of January is approaching!

nzdst — Tue, 18 Dec 2007 00:24:00 GMT

Hi All,

We sent this information out in September during the mad rush of customers preparing for the Daylight Savings change, however this may have fallen off the radar for customers running Vista and Outlook. Customers running Windows Vista and Outlook will need to rebase their calendars again after the 1st of January (and as close to the 1st of January as possible).

Please refer to this post for more information
- http://blogs.msdn.com/nzdst/archive/2007/09/20/new-zealand-time-zone-differs-between-windows-vista-and-down-level-windows-oses.aspx

Nick.

December 2007 cumulative time zone update for Microsoft Windows Operating Systems

nzdst — Tue, 27 Nov 2007 23:53:00 GMT

Hi All,

This update supersedes and replaces update 933360, which was released in August 2007. This update also includes additional time zone changes that were signed in to law after update 933360 was created. If you have already deployed update 933360, read the descriptions of the specific time zone changes that are addressed in this Microsoft Knowledge Base (KB) article to determine whether you must deploy this update immediately. If systems are not directly affected, you can schedule deployment at the next available opportunity. We recommend that you deploy the most current Windows cumulative time zone update to guarantee the consistency of the time zone database on all systems.

Important Before you apply the update that is described in 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 How to address the daylight saving time changes in 2007 by using the Time Zone Data Update Tool for Microsoft Office Outlook

Important

•

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 information about the Exchange daylight saving time (DST) update, 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

•

Cumulative time zone updates contain only data that has changed for a specific region or that has been added to maintain parity with other operating system versions. Therefore, if a time zone key has been deleted, some original values may not be restored after you apply the cumulative zone update. We do not recommend that you delete any registry keys that are related to time zones. On a computer that has incomplete time zone keys, first restore the time zone keys from a known good backup. Then, apply the update.

http://support.microsoft.com/default.aspx/kb/942763

The above packages will be pushed out via Windows Update 11 of December (US Pacific Time) and when Custom Support Agreement packages will be available via connect.

Nick.

Tzmove and /forcerebasesuppressallupdates

nzdst — Thu, 13 Sep 2007 08:11:00 GMT

Hi All,

We have had a few questions about Tzmove and using the /forcerebasesuppressallupdates switch.

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.

Generally speaking we don't recommend that /FORCEREBASESUPPRESSALLUPDATES be used with user calendars, noting the risks in the "Issues" sections of http://support.microsoft.com/kb/933146.

See also http://blogs.technet.com/dst2007/pages/quick-reference.aspx

Nick.

What version of TZMove are you using?

nzdst — Tue, 11 Sep 2007 06:09:00 GMT

Hi All,

There was new version of tzmove.exe published to the web on the 30th of August. We highly recommend customers use this version and remove earlier versions. The knowledge base article that references this new version was update on the 5th of September 2007.

To check what version you are using please check the version of TZmove.exe file. This is located here:

“C:\program files\microsoft office\office 12\office outlook time zone data update tool\tzmove.exe”

The version should be 12.0.4518.1062, otherwise please click on the link above to download the latest version.

Changes

We rolled up all of the “hotfixes” that were made to the original tzmove shortly after it was released and included them in the ‘core’ version of the new release (e.g. additional functionality that is useful for rebasing resources, updated logic about prerequisites for install, etc.)

A streamlined UI, that by default, doesn’t confuse the end-user with options related to ‘physical’ moves between time zones (e.g. a user permanently moving from New York to LA and wanting to update their Calendar appropriately). Specifically, the time zone move UI is now hidden unless you provide a command-line parameter to explicitly unhide it.

Update - Steps to reporting the changes that will be made by the Outlook Time Zone Data Update tool.

You can see what modifications will be made by the Outlook Time Zone Data Update tool by using the /REPORTINGMODE option. This option creates a log that can be used for planning purposes. /REPORTINGMODE does not perform any modifications, and instead it logs the items that would be modified if the tool were not run in Reporting Mode to the Application event log.

Update (20th September) - Re-occurring appointments created by deleted users

For the deleted mailbox, users need to update those meetings manually, as there is no mapi profile to therefore connect to and update the appointments.

Nick.