Novell Home

My Favorites

Close

Please to see your favorites.

DST end date extended by one week to 2 April 2006 to coincide with the Melbourne Commonwealth Games

(Last modified: 05Feb2006)

This document (10100402) is provided subject to the disclaimer at the end of this document.

goal

DST end date extended by one week to 2 April 2006 to coincide with the Melbourne Commonwealth Games

fact

Standard AET definition: AET = UTC + 10 hours, with +1 hour DST offset from last Sunday in October till last Sunday in March.
Standard ACT definition: ACT = UTC + 9.5 hours, with +1 hour DST offset from last Sunday in October till last Sunday in March.
Standard TST definition: TST = UTC + 10 hours, with +1 hour DST offset from first Sunday in October till last Sunday in March.

GroupWise 6.5

GroupWise 7.x

All Platforms

change

Victoria, New South Wales, South Australia, Tasmania and the Australian Capital Territory are the only areas operating in the AET, ACT and TST time zones.

The Governments of these states have legislated to extend the DST end date by one week to 2 April 2006 (first Sunday in April) to coincide with the Commonwealth Games 

This change is for 2006 only, and will revert to normal from 2007

symptom

GroupWise version 6 and later post offices are multi-time zone enabled. This means that the individual mailboxes within a post office may be in varying time zones.

All timestamps and appointment times are stored in GroupWise in UTC time. The GroupWise Client converts between UTC and local (workstation) time when creating or reading message items. Routing and delivery actions done by agents are timestamped in UTC by the agent, using the time zone assigned to the domain or post office the agent is serving.

So, the time zone definitions that affect GroupWise are those of the workstation OS (Windows, Linux or Mac OS X) for full client users, and GroupWise system itself

fix

First, a decision needs to be made on whether to make any change at all:

If you don't change the time zone definition on workstations then workstation time will be out by 1 hour for the week March 26th to April 1st, 2006.

If you decide to change the time zone definition:

For full client users on all platforms:

The local workstation time zone definition needs to be changed for each workstation operating in the AET, ACT or TST time zones. Once this is done on a workstation GroupWise will display existing appointments for the week March 26th to April 1st one hour later on that workstation. Appointments remain synchronized throughout the GroupWise system, they just display one hour later when viewed from workstations in the modified AET, ACT or TST time zones. 

For Windows users, Microsoft provides a utility that modifies the local time zone definition for the AET, ACT and TST time zones. http://www.microsoft.com/australia/timezone/2005.aspx

If the actual time of appointments needs to remain unchanged, then you will need to do one of the following:

1. Advise users that they need to either manually confirm or delete and reschedule all existing appointments for the week of March 26th to April 1st, 2006.

2. Use the Appointment Time Adjuster utility to adjust the relevant appointments in all post offices in which there are users who are recipients of those appointments. This utility is downloadable from:  http://support.novell.com/cgi-bin/search/searchtid.cgi?/2956924.htm

For WebAccess users:

 By default WebAccess uses the time zone assigned to the users post office, however users can override this by setting their timezone in WebAccess. For users who have not selected their time zone in WebAccess, merely altering the AET, ACT and TST time zone definitions in ConsoleOne will be sufficient.

 For WebAccess users who have selected their time zone in WebAccess, the details of that time zone are written to their user database. The change described above, made by the Administrator to the GroupWise timezone definition for AET, ACT and TST time zones through ConsoleOne will not reset WebAccess time zone details in user databases.

To make this happen you must use the ClearTZ option with GWCheck as described at  http://support.novell.com/cgi-bin/search/searchtid.cgi?/10076257.htm .

 Individual users will then have to re-select their WebAccess time zone if it is different from their post office's assigned time zone.  This will cause existing appointments for the week March 26th to April 1st to display one hour later than they were originally set for. Appointments remain synchronized throughout the GroupWise system, they just display one hour later when viewed by users who's post office is in the modified AET, ACT or TST time zones

 If the actual time of appointments needs to remain unchanged, then you will need to do one of the following:

1. Advise users that they need to either manually confirm or delete and reschedule all existing appointments for the week of March 26th to April 1st, 2006.

2. Use the Appointment Time Adjuster utility to adjust the relevant appointments in all post offices in which there are users who are recipients of those appointments. This utility is downloadable from:  http://support.novell.com/cgi-bin/search/searchtid.cgi?/2956924.htm

3. To ensure that routing and delivery timestamps remain consistent with timestamps applied by GroupWise Clients, the GroupWise timezone definitions for AET, ACT or TST time zones will have to be altered through ConsoleOne. To ensure that server time reverts from DST to Standard time on the correct date the server OS time zone must be altered.

.

note

After April 1st, 2006 you will need to revert all the changed timezone definitions back to their normal DST end date of Last Sunday in March, in preparation for 2007. The sooner this change is made the less chance that users will create new appointments for the corresponding week in 2007 and future years that need to be adjusted or rescheduled.

Users should be advised not to create new appointments for the corresponding week in future years until after the timezone definitions have been returned to normal.

A word about external appointments:

The Administrators of external systems may well handle this time zone change differently to the way you do. Regardless of how you choose to handle this change, you should advise users to confirm appointment times with external recipients for the week March 26th to April 1st manually.

Mobile devices (PDA's, etc):

Please refer to the mobile device OS vendor for details of how to handle the time zone change for these devices. The synchronization solution and PDA applications that use the GroupWise data may also need adjustment.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10100402
  • Solution ID: NOVL105085
  • Creation Date: 05Feb2006
  • Modified Date: 05Feb2006
    • NovellGroupWise Client/Admin

Did this document solve your problem? Provide Feedback