Daylight savings starts early this year - are your sites up to date?

As you probably know, daylight saving now commences on the first Sunday in October and ends on the first Sunday in April in New South Wales, Victoria, the ACT, Tasmania & South Australia. This change affects Microsoft Windows, Microsoft Office Outlook and other Microsoft, third party and custom applications. 

Below is a quick snapshot of things you need to know & where to go to get more information.

Cheers,

Robbie

 

What is the impact of Daylight Savings changes?

Effects can range from the incorrect time display on the clock, to calendaring problems, to financial and reputation loss if business critical services fail.  

The 5th of October commences the second window of time zone harmonisation for this year, however, we expect a greater impact in October as the change is 21 days difference, whereas the adjustment earlier in the year was only 7 days.

What is affected?

- All Microsoft Windows PC, server and mobile devices in the affected time zones must be updated to ensure accuracy of internal time zone tables and correct operation of the system clock.

- Microsoft Office Outlook calendars may need to be adjusted. Client and Server-based tools are available to automate this service.

- Microsoft, third party and custom applications which schedule events at future dates should be reviewed to ensure they will operate correctly during the extended daylight saving period. Previously scheduled events may also need to be adjusted.

- Microsoft recommends that all PC and server systems are updated regardless of location to ensure consistency of operation.

What do I need to do?

Thorough planning and testing for these changes is critical to ensure the change results in minimal user impact, so to help customers prepare Microsoft has developed the Australia 2008 Daylight Saving Planningdocument which details the nature and impact of the DST changes, along with planning guidance to avoid user impact.

What if the systems have been previously patched?

Where servers, workstations and mobile devices have been added to the infrastructure, organisations will need to audit their environment to ensure all systems are patched according to the organisation’s Daylight Savings Plan.

Where the environment does not have a consistent Daylight Savings Time (DST) patch level, appointments may have been created with a mix of correct and incorrect DST transition dates.  Furthermore, Microsoft recommends customers update all systems to ensure consistency of operation, even if none of your systems are in the affected time zones.

Planning for Daylight Savings changes

Microsoft has revised the Australia 2008 Daylight Saving Planning Guide with learnings from the April transition and additional considerations for the October transition. Download the guide and update your daylight savings plan.

Support Options: