New Zealand DST updates for Sharepoint, Dynamics, SQL Notifications, Visual Studio, CE and JVM

After applying updates to Sharepoint Server, recurring events which start prior to a daylight saving period may appear off by one hour after the start of the daylight saving period. To correct this problem open the event, reset the times and save the event.

Both WSS 2.0 and 3.0 can be updated manually if required: see KB888253 for details.

After applying the updates, appointments which fall within the new daylight saving period may be shifted by one hour. To fix this problem, update the appointments manually and re-save them.

Microsoft SQL Server Notification Service instances created prior to applying a time zone update may need to be modified to reflect the new settings. Refer to KB931815 for background on this issue. Customers who are affected by this should call Microsoft Technical Support, log a Professional Support incident and request that it be brought to the attention of the CPE Lead. There is no charge for cases logged in this fashion.

Developers who use the .NET Framework may find their applications affected if the application uses the time zone information for historical purposes or if they have derived custom classes from System.TimeZone to provide custom time zone information. The standard System.TimeZone class provides a managed wrapper for the underlying Windows Operating System time zone functions. Refer to Visual Studio and Daylight Saving Time Change for more information.

Device owners should contact the device manufacturer to determine whether or not an update is available.

The Microsoft Java Virtual Machine (MS JVM) will sometimes apply an incorrect time zone rule after the daylight saving update is applied the daylight saving transition has occurred. Microsoft is restricted to providing only security fixes to the MS JVM. Further information the MS JVM is available at http://www.microsoft.com/mscorp/java/default.asp.