New Zealand 2007 Daylight Saving Changes : NZ

New Zealand Daylight Savings ending on the 6th of April.

nzdst — Tue, 18 Mar 2008 02:09:00 GMT

Hi All,

A reminder that this year, daylight savings ends two weeks later than previous years due the law changes introduced in April last year. This year, daylight savings ends at 3am on 6^th of April 2008. For more information on products affected, patches that needed to be applied prior to daylight savings starting, guidance and other resources, please refer to the New Zealand Daylight Savings Website.

Nick

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.

NZDST - Microsoft JVM version 3815 release

nzdst — Mon, 22 Oct 2007 23:46:00 GMT

Hi All,

Daylight saving time (DST) affects all builds of the Microsoft JVM up to and including VM version 3812. Microsoft has worked cooperatively with Sun Microsystems to provide a hotfix update to the MSJVM that will make it compatible with the latest changes to the observance of DST in the time zones for New Zealand, Eastern Europe (Minsk), GTB (applicable to Athens, Istanbul) and Eastern South America (Brasilia). MSJVM was shipped as part of a number of products that are currently in Extended Support. The update to the MSJVM for these DST changes is available to customers through the Extended Support program. Premier Support customers should work with their local Microsoft account team to discuss options to obtain the hotfix.

Non-Premier Support customers should contact Professional Support on 0800 800 004.

Nick.

Mac OS X: Adjusting Date & Time for New Zealand Daylight Saving Time in late 2007

nzdst — Tue, 16 Oct 2007 05:14:00 GMT

Hi All,

We've had a number of support calls from customers who are running Mac OS X and Entourage who are concerned with the guidance supplied by Apple which was to manually move the time after the 30th of September 2007.

Here is the Apple KB article - http://docs.info.apple.com/article.html?artnum=306486

A third party workaround has been posted to the web which should address this issue - http://www.mactcp.org.nz/nzdt.html. As always, we stress that testing should always be done before rolling this out to production systems.

DISCLAIMER - This is completely unsupported by Microsoft and therefore we offer no warranty or support if you choose to utilise information in this posting.

Also see NZDST - Updates for Entourage

Nick.

NZ DST Changes this weekend!

nzdst — Thu, 27 Sep 2007 23:54:00 GMT

Hi All,

In April 2007 the New Zealand Government announced an update to the Time Act of 1974. This update changes the dates of both the start and end of daylight saving time (DST). When this law goes into effect in 2007, daylight savings time will start one week earlier (2:00 A.M. on the 30th September 2007) and will end two weeks later (3:00 A.M. on 6th April 2008) than past years. Click here for more information from the New Zealand Government.

The New Zealand Daylight Savings changes Guidance Document can be found here (XPS and PDF versions are available).

The New Zealand daylight savings blog is constantly being updated with information as it comes to hand. Please ensure you are keeping your eyes on it.

If things don’t go as expected over the weekend, Please visit here to understand your support options with Microsoft. Customers who have managed support agreements with Premier Support, Please follow your normal processes to log support calls directly with Microsoft.

Many thanks,

Nick.

New Zealand time zone differs between Windows Vista and down-level Windows OSes

nzdst — Thu, 20 Sep 2007 00:35:00 GMT

Introduction

Windows encodes the time zone transition dates on a yearly basis yielding the following rules for years 2006, 2007, and 2008:

	DST End	DST Start
2006	Third Sunday in March	First Sunday in October
2007	Third Sunday in March	Last Sunday in September
2008	First Sunday in April	Last Sunday in September

The definition of the New Zealand time zone differs between Windows Vista and down-level Windows OSes. Specifically, the difference between OSes relates to which time zone rule each OS returns as the currently active rule; Vista returns the 2007 rule shown in the table above while other Windows OSes return the 2008 rule.

This difference exists because Vista is designed to keep the 2007 rule as the active rule until December 31st, at 11:59:59PM. At midnight, January 1st , Vista will automatically activate the 2008 rule. Previous OSes such as Windows XP and Windows Server 2003 do not have the capability to automatically switch rules, so after the time zone patch under KB 933360 is applied; they make the 2008 rule active.

This inconsistency causes user-visible differences in the functioning of the Outlook Calendar on Vista versus non-Vista OSes. The below is intended to explain the end-user visible affects as well as provide some guidance on how to best plan for rebasing calendars in this region.

Example

In the following example, two weekday recurring appointments were created on fully patched OSes. Both computers had the current time zone set to New Zealand and both created the appointments such that they occurred from 12:00pm to 12:30pm local time. In the screen shots below, the green series was created on a down-level OS (and, therefore, encoded using the 2008 time zone rules for New Zealand) while the red series was created on Vista (and, therefore, encoded using the 2007 time zone rules for New Zealand).

As can be seen in the table above, this means that the two recurrences differ by how they were encoded between the third Sunday in March and the first Sunday in April. To illustrate the issue, let us now display the items on the two different machines:

Down-level OS

On the down-level OS, the 2008 New Zealand rule is in force and, therefore, daylight savings time ends on April 6th. This means that the item encoded in 2008 rules continues to occur at noon but the item encoded with 2007 rules now appears an hour too late since it was encoded under the expectation that daylight savings time is no longer in force.

The discrepancy continues until we get to the first Sunday in April, at which point both appointments return to their intended local time.

Windows Vista

When viewed on Vista, exactly the same appointments in the same store look different. Again, everything agrees except for the “delta” between the third Sunday in March and the first Sunday in April only, on Vista, it is the item encoded with 2007 rules that continues to look correct while the item encoded in 2008 rules now looks an hour early because it was encoded under the expectation that daylight savings time would continue and the Calendar is being displayed as if it does not.

As above, the discrepancy continues until we get to the first Sunday in April, at which point both appointments return to their intended local time.

Outlook Calendar Rebasing

The Time Zone Data Update Tool for Microsoft Office Outlook is aware of the above discrepancy and attempts to handle it as correctly as possible. Specifically, the client-side tool will detect the OS on which it is running and behave as expected on the assumption that all appointments were created on that OS. Some examples (assuming a fully patched machine in all cases):

• When run on Vista during 2007 with the time zone set to New Zealand, the tool will assume that any appointments that lack time zone information were created using the 2006 rules and will transition all appointments to the 2007 rules.
• When run on Vista during 2008 with the time zone set to New Zealand, the tool will assume that any appointments that lack time zone information were created using the 2007 rules and will transition all appointments to the 2008 rules.
• When run on a down-level OS in either 2007 or 2008, the tool will assume that any appointments that lack time zone information were created using 2006 rules and will transition them directly to the 2008 rules.
It is worth noting that, in all versions of Outlook, all recurrences are stamped with time zone information and, therefore, there is no ambiguity in behaviour. Single instance items, on the other hand, are not stamped with time zone information on Outlook 2003 SP2 and earlier so, in such cases, care will have to be taken to review the times of all single-instance appointments to ensure that the updated calendar items are correct.

All of the behaviour described above is specific to the latest version of the Time Zone Data Update Tool for Microsoft Office Outlook and the Exchange Calendar Update Configuration Tool. Previous versions of both tools do not behave properly in time zones such as New Zealand so users/administrators should be sure to have the latest versions of the appropriate rebasing tool before starting. The latest versions of the Time Zone Data Update Tool for Microsoft Office Outlook and the Exchange Calendar Update Configuration Tool along with supporting documentation can be found at http://support.microsoft.com/kb/931667 and http://support.microsoft.com/kb/941018 respectively.

Mitigations

Here are some things to think about as you consider your plans for rebasing Calendars in the New Zealand time zone:
• It is beneficial to rebase a calendar on the OS from which the majority of single instance items were created (although care still needs to be taken to ensure that the correct updates were applied).
• In the case of Vista, users will have to rebase their Calendar a second time in January of 2008. It is recommended that this rebasing be done as early in 2008 as possible so as to avoid user confusion as late March and early April approach.
• If using the Exchange Calendar Update Configuration Tool, the above logic applies to the machine from which the Exchange Calendar Update Configuration Tool was run (i.e. that machine should be chosen such that it matches the most common OS deployed across the company and a second rebasing will have to be scheduled if users create appointments using Vista).

Conclusion

There are three end-user visible side-effects to the interaction of the Outlook Calendar and the definition of the New Zealand time zone on various Windows OSes:
1. When looking at appointments in late March or early April, there will be a discrepancy between the local time at which the appointments appear to start and end.
2. Users that only use down-level OSes to create/edit items on their Calendar need to rebase only once, during the fall of 2007.
3. Users that use Vista to create/edit items on their Calendar will need to rebase twice: once in the fall of 2007 and again in January of 2008 in order to transition any items encoded using the 2007 time zone rules into the 2008 time zone rules. Once this step is successfully completed, anomalies such as the above should simply disappear.

We greatly appreciate the assistance and feedback that Graham Codd provided on this issue.

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.

DST and NT 4.0

nzdst — Thu, 06 Sep 2007 09:17:00 GMT

DISCLAIMER - This is completely unsupported by Microsoft and therefore we offer no warranty or support if you choose to utilise information in this posting. This has not been tested by Microsoft as it is outside of extended support and therefore out of our test matrix. Please backup your registry before making any changes to ensure you have a known good restore point. As always please ensure you test this in a lab environment before deploying to production systems.

NT 4.0 and earlier.

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\New Zealand Standard Time]

"Display"="(GMT+12:00) Auckland, Wellington"

"Dlt"="New Zealand Daylight Time"

"Std"="New Zealand Standard Time

"MapID"="78,79"

"Index"=dword:00000122

"TZI"=hex:30,fd,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,04,00,00,00,01,00,03,00,00,\

00,00,00,00,00,00,00,09,00,00,00,05,00,02,00,00,00,00,00,00,00

Testing the update:

1.	Change the date/clock to September 30, 2007, 1:59am and verify that the clock advances one hour (instead of moving to 2am it moves to 3am). This is the new (2007) DST start date.
2.	Change the date/clock to October 7, 2007 at 1:59am and verify that the clock does not adjust for DST (Simply moves to 2am). This is the 2007 DST start date.
3.	Change the date/clock to March 16, 2008 at 1:59am and verify that the clock does not adjust for DST (Simply moves to 2am). This is the 2008 DST end date.
4.	Change the date/clock to April 6, 2008 at 2:59am and verify that the clock goes back one hour to 2:00am (instead of 3am). This is the new (2008) DST end date.

Guidelines for when an overseas company needs to install the NZ DST updates

nzdst — Thu, 06 Sep 2007 09:13:00 GMT

Please see the guidelines below for when to update systems that are based outside NZ.

Required:

· Domain Controllers :- you will need to update all AD domain controller servers if that server has a dual role or is likely to run an application that use the OS to get time zone information.

· Exchange servers:- You will need to update all Exchange Servers with the OS update and the Exchange CDO update at the same time if they use OWA or any 3rdparty application that does CDO calls

· Member Servers:- You will need to update any member server with the OS patch if an application that uses the OS to obtain its timezone information is installed

· Terminal Servers:- You will need to update any terminal server that has outlook installed with the OS patch that. These machines will need to be updated at the same time as the client OS updates are done.

· Client Desktops:- You will need to update a users client workstation (OS patch) and then rebase the users calendar in the remote site if the user in question schedule re-occurring meetings or resources in NZ

· Applications:- Any application that is hosted outside NZ that implements scheduling or calendaring and holds its own timezone information will need to be updated.

Recommendation:

· Microsoft recommends that the Daylight savings update is installed on all machines in the environment (Clients and Servers) to reduce any potential issues.

SAP and NZ Daylight Saving Time Changes

nzdst — Thu, 06 Sep 2007 08:48:00 GMT

SAP Note No. 1080797 07.08.2007 Page 1
________________________________________________________________________

     Number              1080797
     Version             2 from 07.08.2007
     Status              Released for Customer
     Set on              07.08.2007

     Language            EN
     Master language     DE
     Short text          Begin date & end date of DST in New Zealand as of
     Sept 2007

     Responsible         Ulrich Weber
     Component           BC-SRV-TIM-TZ
                         Time zones
     ________________________________________________________________________

Long text

     Symptom
     As of the summer 2007/2008, the start date and the end date of the DST
     are changed in New Zealand. DST starts on September 30, 2007 at 2
     o'clock a.m. and ends on April 6, 2008 at 3 o'clock a.m.
     The DST starts in New Zealand now on the last Sunday in September and
     ends on the first Sunday in April.

Other terms
DST, daylight saving time

Reason and Prerequisites
None.

Solution

1. In the IMG, call the maintenance dialog for the daylight saving time
rules:

         Call transaction STZBC - "Variable Summer time rules" view (or call
         the IMG activity "General Settings" -> "Time zones" -> "Maintain
         Time Zones")

2. Create a new entry with the following data:

- DST rule: NEWZEA

- Valid from: 2007

- Start Mon.: 9 (September)

- Start Day: 1 (Sunday)

- Strt DayMo.: 5 (last occurrence of that particular weekday in
the month)

- Start Time: 02:00:00

- End Month: 4 (April)

- End Day: 1 (Sunday)
Page 2

- End Day/Mo.: 1 (1. (first occurrence of that particular
weekday in the month)

- End Time: 03:00:00

These changes are available in the attachment to Note 198411 as of
Version TZ_2007_V04.

     Note that you should not delete old entries in the daylight saving time
     rules (for example, entries valid as of 1990), because these entries
     will still be required for the correct conversion of data prior to 2007.

________________________________________________________________________

     Valid releases
     Software Component                        Release
                                               from            to
     SAP_BASIS
          SAP Basis component
                                               710          - 710
                                               700          - 700
                                               620          - 640
                                               46C          - 46C

________________________________________________________________________

Reference to related Notes

     Number    Short text
     ____________________________________________________________
     198411    Current data and information about time zones

________________________________________________________________________