Where Are You Coming From Today?
Follow us on:
by LATAM DST Taskforce
Disclaimer: The information in this document is written in response to an announcement by the government of Chile about changes in the daylight saving time in Chile for the year of 2010.
The steps provided in this bulletin were created to mitigate the impacts that the daylight saving time changes will cause for customers in Chile. These are the impacts primarily anticipated at the time this document was written, and the effects that customers may face are not restricted to them.
The suggested actions on this document might receive additional testing. The information described in this document may change without notice.
In addition, customers should be aware that further guidance will be provided at any time by Microsoft.
Special notes: The official decree changing the DST dates in Chile is published by the government on the following site: http://www.horaoficial.cl/cambio.htm
In response to the recent natural disaster that impacted the country the Chilean government has announced a new end date for the DST period of 2009-2010. The new fallback information is the following:
Since the new date published by the government is different from what was defined in the previous years, Windows-based computers could not correctly interpret the time that IS related to the transition to daylight saving time.
In addition to Microsoft products, other software, OS releases and hardware (phones, routers, switches and managed devices) may require updates and/or changes.
Microsoft released a hotfix to address the changes. The hotfix 981128 updates the DST end date for the “(UTC-04:00) Santiago”.
For Windows 2000 machines, the hotfix KB 981128 will only be available for customers with Extended Hotfix Agreement (EHA). Customers with no EHA can update their Windows 2000 systems via ‘Updating ‘(GMT -04:00) Santiago’ time zone in Windows 2000 Operating Systems’ section in this document.
Our teams at Microsoft have taken several steps to alert customers and partners to the change in Chile.
This is a guide for those that followed our first recommendation (published before the release of the hotfix KB981128) and changed the machine’s time zone to “GMT-03:00 Cayenne, Fortaleza”. It describes the steps that need to be done to prepare their machines for the end of the extended DST period.
Users that applied the hotfix KB981128 or modified the time zone “GMT-04:00 Santiago by following the KB914387 (or our blog post at Guidance for Chile DST Changes effective Saturday, March 13, 2010) are prepared for the upcoming changes and don’t need to follow this guide.
We will continue to publish advice and recommendations on the LATAM Team Blog at http://blogs.technet.com/latam and at http://www.microsoft.com/chile/cambiodehora/default.aspx.
Customer needs to follow the steps bellow to update the Operating Systems and Outlook calendar.
This section describes the anticipated impacts of the changes. We recommend customers to evaluate steps before apply on their environment.
Applies to:
Note:
Below is a brief description of these activities:
Item
When
Activity
1
As soon as possible
Apply KB981128 or follow KB914387
2
Any time before April 03th, 2010
Change computer time zone back to ‘(GMT -4:00) Santiago’ and readjust Outlook calendar appointments to the new time zone definition.
In order to change the computer time zone to ‘(GMT -04:00) Santiago’, please follow the steps below:
For Windows Vista, Windows Server 2008, Windows 7 and Windows 2008 R2 machines:
Note: If your machine does not have the KB979306 applied the display name can be one of the following:
o (UTC-03:00) Buenos Aires, Georgetown
o (UTC-03:00) Georgetown
o (UTC-03:00) Cayenne
The solution can be applied with any of the above display names.
For Windows 2000, Windows XP and Windows Server 2003 machines:
The solution can be applied with any of the above display names
Warning: If your domain have multiples site in different countries make sure that you only deploy this solution to machines that are located in Chile. We recommend customers to evaluate the alternative and test before apply on their production environment.
Note: this procedure is only supported in Windows 2000, Windows XP and Windows Server 2003, Windows 7 and Windows 2008 R2 Operating Systems. Users running Windows Vista and Windows Server 2008 will have to use the procedures specified in ‘Changing Windows OS time zone to ‘(GMT -04:00) Santiago’’ section.
On Active Directory environments, administrators may want to automate the change of time zones to ‘(GMT -04:00) Santiago’. This section explains how to deploy this time zone change via startup script. These procedures need to be executed in a Domain Controller or another machine with Admin Tools installed.
After performing all the steps below, all machines need to be restarted to automatically change the computer time zone. To avoid restarting a specific machine, please execute the procedures ‘Changing Windows PC Operating Systems time zone’ above to move this machine to ‘(GMT -04:00) Santiago’ time zone.
The script below can be used to change the current time zone to (GMT -04:00) Santiago on the client computer. Then, the script writes an event to the Application log of the client computer where the script was run.
On Error Resume Next strNewTimeZone = "Pacific SA Standard Time" Set objSh = CreateObject("WScript.Shell")
'Get the StandardName key of the current time zone szStandardName = objSh.RegRead("HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\StandardName")
'Enumerate the subkeys in the time zone database Const HKEY_LOCAL_MACHINE = &H80000002 Set objReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv") szTzsKeyPath = "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones" objReg.EnumKey HKEY_LOCAL_MACHINE, szTzsKeyPath, arrTzSubKeys
'Step through the time zones to find the matching Standard Name szCurrentTzKey = "<Unknown>" For Each subkey In arrTzSubKeys strTimeZoneStandarName = "" strTimeZoneStandarName = objSh.RegRead("HKLM\" & szTzsKeyPath & "\" & subkey & "\Std") If (strTimeZoneStandarName = szStandardName) Then 'Found matching StandardName, now store this time zone key name szCurrentTzKey = subkey End If Next
Dim process, processid, result, strUpdateCommand Set process = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2:Win32_process")
'Add time change privilege to the process object process.Security_.Privileges.AddAsString "SeSystemTimePrivilege", True strUpdateCommand = "control.exe timedate.cpl,,/Z" & strNewTimeZone
'Launch control.exe to change time zone using the TZ key name stored in strNewTimeZone result = process.Create(strUpdateCommand, Null, Null, processid) If result <> 0 Then objSh.LogEvent 1, "Process to change machine time zone failed to execute on this computer. Unable to change machine time zone." wScript.Quit 0 End If
'Get the display name from previous time zone and compare with the new time zone szPrevDispName = objSh.RegRead("HKLM\" & szTzsKeyPath & "\" & szCurrentTzKey & "\Display") szNewDispName = objSh.RegRead("HKLM\" & szTzsKeyPath & "\" & strNewTimeZone & "\Display")
'Write entry to the Application event log stating that the update has executed If szPrevDispName = szNewDispName Then objSh.LogEvent 4, "Machine time zone was refreshed. The current time zone is: " & Chr(13) & Chr(10) & Chr(13) & Chr(10) & szNewDispName & "." Else objSh.LogEvent 4, "Machine time zone was changed from: " & Chr(13) & Chr(10) & Chr(13) & Chr(10) & szPrevDispName & Chr(13) & Chr(10) & Chr(13) & Chr(10) & "To: " & Chr(13) & Chr(10) & Chr(13) & Chr(10) & szNewDispName & "." End If
@echo off ver |find /i "6.">nul IF %errorlevel% EQU 0 GOTO SIX cscript \\contoso.com\NETLOGON\ChangeTZ.vbs GOTO End :SIX ver |find /i "6.0">nul IF %errorlevel% EQU 0 GOTO End ver |find /i "6.1">nul IF %errorlevel% EQU 0 GOTO Win7 GOTO End :Win7 TZUTIL /G |Find /i "SA Eastern Standard Time" >nul IF %errorlevel% EQU 0 GOTO Santiago GOTO End :Santiago TZUTIL /s "Pacific SA Standard Time" :End
Any calendar item created during the extended DST period (03/14/2010 and 04/03/2010) and scheduled to any date during the next DST period will show with one hour off. We are going to call this difference “Delta Period”.
The inconvenience experienced by Outlook client users happens for all appointments during the delta period that were created before the administrators update the DST dates on the operating system.
Those appointments will be off 1 hour. This may happen for both recurring and single-instance appointments.
The appointments created after the DST dates have been updated on the operating system will have the correct time.
To answer this question, we need to understand how Outlook schedule meetings and appointments:
Three factors affect the scheduling of a meeting and appointment in Outlook:
Outlook time stamps the message request with the Greenwich Mean Time for the meeting. Outlook calculates Greenwich Mean Time by using the computer's clock time, plus or minus the local time zone adjustment, minus (depending upon the time of year) the daylight-saving time adjustment.
As soon as Outlook receives the meeting request it will calculate the meeting time for the recipient and schedule it on the calendar. If any of the three factors listed earlier are incorrect at that time, the meeting time will be incorrect. You cannot correct the time after the fact by correcting the factor in error; you must open the meeting request and manually correct the scheduled time.
After you move to the time zone '(GMT -04:00) Santiago", only Outlook calendar items created during the extended DST period (between 03/14/2010 and 04/03/2010) and scheduled for the next DST period (between the second Saturday of October of 2010 and the second Saturday of March of 2011) will be displayed with 1 hour off.
Options to correct your Outlook calendar in this scenario:
Special note: We recommend you to print your calendar before any changes are made, and then review the calendar items to make sure these items appear at the correct times. You can use this printed copy of the calendar items to verify that Outlook has been updated successfully.
The following describes the steps to be followed by end-users performing a time zone move:
After you move from another time zone to '(GMT -04:00) Santiago", your calendar items will be one hour off between the second Saturday of October of 2010 and the second Saturday of March of 2011 (next DST period).
A simpler alternative to correct the Outlook Calendar items is by adjusting the appointments manually. To do so, please proceed as follows:
941018 How to address daylight saving time by using the Exchange Calendar Update Tool
931667 How to address time zone changes by using the Time Zone Data Update Tool for Microsoft Office Outlook
943390 Some Outlook calendar items are rebased incorrectly when you use the Outlook Time Zone Data Update Tool to adjust for daylight saving time changes in certain time zones
934001 A troubleshooting guide to the Exchange Calendar Update Tool (Msextmz.exe)