MOSS Daylight savings time Update for Australia 2008

Seems like the daylight savings issues are continually biting. On the bright side the fix this year for MOSS is a very simple xml change. Simply navigate to “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG” and edit “timezone.xml”. I’d recommend making another copy of timezone.xml at this point just in case. The example here fits for East Coast Australia 2008. Simply go through file until you find your particular timezone, then modify the values or Month Day Hour, just remember that Day is actually the week that it changes ie in this example DST starts in the first week of October this year in Melbourne. It’s all pretty straight forward.

<TimeZone ID="76" Name="(GMT+10:00) Canberra, Melbourne, Sydney" Hidden="FALSE">

Posted in MOSS. 3 Comments »

3 Responses to “MOSS Daylight savings time Update for Australia 2008”

  1. Haley Says:

    You’re a legend mate. I’ve been googling here and there over the past week to solve this for our internal moss with no luck.

    On client site today with the same issue, and now all sorted!

    I only just realised the date of this post too….today! Woo!

    Good timing, thanks again.

  2. Chan Says:

    I’m having issues with the Sharepoint timer service kicking off an hour early. I also read the following article:

    But when I checked the TIMEZONE.XML the start date for Daylight savings appears to be correct:



    That is the correct date and time for Melbourne (this year) as per this page:

    FYI I’m on the MOSS and upto version (Infrastructure update)

  3. Chris Armstrong Says:

    Hi Chan,

    That one sounds odd, according to the DST doco from Microsoft MOSS shouldn’t need anything other than the change in the timezone.xml. I haven’t really investigated whether timer jobs are running against the DST time myself, but I’d double check the Operating System as it also requires it’s own set of DST patches, which are described in the Australia2008DaylightSavingPlanningGuide.doc. In terms of the Infrastructure update, I’m not convinced that this has actually been useful so far, it seems to have caused some major issues on our servers which we haven’t been able to isolate.

    Please let me know if you find a solution to this.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: