Hot Topics for Daylight Saving Time changesLatest NewsDaylight Saving Time changes in Morocco and Pakistan (revised May 19, 2008)
Microsoft has learned of a change to the observance of Daylight Saving Time (DST, aka regionally as Summer Time) in Morocco and Pakistan that could impact customers using local time zones. We have news that Morocco will switch from GMT to GMT+1:00 beginning on June 1, 2008, and that the Pakistan Government will change from GMT +5:00 to GMT +6:00 June 1, 2008, at 12 midnight (local time). These changes may impact customers and partners in the regions who use local time zones, including entities engaged in business in or with the region.
Unfortunately, due to the short notice provided for these late breaking changes, we do not expect that product groups will provide updates incorporating these changes. The Windows organization plans to include these updates in the next release of the 2008 Cumulative Time Zone Update for Windows, scheduled to release in July/August 2008.
For manual remediation of Microsoft Windows operating systems in mainstream support, Microsoft will provide an updating to the following DST and time zone manual update article with the changes for Morocco and Pakistan:
How to configure daylight saving time for Microsoft Windows operating systems Advisory: Potential changes to Daylight Saving Time in Iraq
Microsoft has learned of a change to the observance of Daylight Saving Time (DST) in Iraq that could impact customers using the Baghdad time zone which is also called the Arabic time zone (GMT +03:00). The Ministry of Iraq has decided that the country will no longer observe DST as they have in prior years, which has historically taken effect on April 1. This may impact customers and partners in the region who use the Baghdad time zone, including entities engaged in business in or with the region. Microsoft has created product updates and guidance to help customer adjust to this change.
Microsoft is recognizing this change and provides the guidance to customers and partners should they have systems that may be impacted by this change in Iraq, as noted on the Microsoft Daylight Saving Time & Time Zone FAQs Blog at http://blogs.technet.com/dst2007/archive/2008/03/25/advisory-potential-dst-change-in-iraq-technical-guidance.aspx.US and Canadian Daylight Saving Time
US and Canadian Daylight Saving Time occurs March 9: DST now begins on the second Sunday of March (in 2008, March 9), several weeks earlier than in years prior to 2007. DST will end later than usual, on the first Sunday of November (in 2008, November 2); more details on the new DST start and end times can be found here). This results in a new DST period that is approximately three to four weeks longer than in previous years. Generally, customers should have applied and updated their client and server systems previously with the 2007 DST and TZ updates, and continued to install cumulative updates as released (such as the 2008 Cumulative Time Zone Update for Windows has as noted in KB article 942763). Please review the list of impacted Microsoft products at http://support.microsoft.com/gp/dst_prodlist for a list of updates.Some customers may be impacted, such as those in South America that requested and installed a DST/TZ hotfix (as provided recently for Argentina); multinational companies with activities in these areas should consider applying the hotfix updates or following published guidance for utilizing an appropriate time zone.Argentina: Changes to daylight saving time: December 30
The government of Argentina approved a new change to their observance of daylight saving time in the country effective this Sunday, December 30, 2007 at 12:00am to March 16th, 12:00 for Argentina. Information is also available via our Argentinean web site at http://www.microsoft.com/argentina/dst, "Instrumentación del próximo horario de verano para Argentina en 2007-2008." Customers and partners will find additional information on this change and manual remediation at http://blogs.technet.com/dst2007/archive/2007/12/29/argentina-122907.aspx.Australia Eastern and Central 2008 Daylight Saving Changes
Australia Eastern (New South Wales, Victoria, Australian Capital Territory and Tasmania) and Central (South Australia) time zones will extend daylight saving and also harmonise start and end times commencing April 2008. From April 2008, daylight saving will end on the first Sunday in April and recommence on the first Sunday in October in all states. See the Australian Government Time web site for more information. For a summary of the status of product updates, we recommend that customers review the information at http://technet.microsoft.com/en-au/bb887637.aspx. In most cases, customer will find that these changes have been addressed when the latest cumulative time zone update for Microsoft Windows operating systems was applied (released December, 2007, as noted at http://support.microsoft.com/kb/942763). Some of the updates are not specific to the Australia Eastern and Central changes and can be applied immediately; other products (for example Office Groove) require manual adjustment after application of the time zone update to the host Windows operating system.2008 Cumulative Time Zone Update for Windows
The 2008 Cumulative Time Zone Update for Windows has been released to the Microsoft Download Center (DLC) for currently supported Windows OS versions (including Windows XP, Windows Server 2003 and Windows Vista.)
This update can be found in KB article 942763
As noted previously, the annual 2008 Cumulative Time Zone Update for Windows sets the known, correct dates for 2008 (including 2008 changes for Australia, Brazil and other countries we know that have changed their observance of DST entry/exit dates or time zones in 2008). This early drop of the update allows IT professionals and sysadmins to test the installation and deployment of the cumulative update roll-ups prior to broad distribution. The update packages will be distributed to computers via Windows Update in early December (the second Tuesday, Dec 11.)
Guidance for consumers and unmanaged customers: Generally, consumers should allow for the updates to be installed on their computers via Windows Update rather than download and install these updates from the DLC. Outlook 2007 Free/Busy information moved ahead by one hour in a mixed Exchange environment
Free/Busy information for Exchange 2003 users when viewed through the Exchange 2007 Availability Service and Microsoft Office Outlook 2007 is displayed as being moved ahead by one hour when viewed on a client that has a system time of November 4, 2007 at 2:00 A.M. or earlier. After November 4, 2007 all Free/Busy information displays correctly for Exchange 2003 users when viewed through the Exchange 2007 Availability Service and Outlook 2007. This is not true for appointments that occur after March 9, 2008. A hotfix is planned for Outlook to resolve this problem for future time changes. Microsoft Knowledge Base article 944374 will be used to document this issue.Windows Mobile
Many changes in daylight saving time (DST) and time zones have occurred. Microsoft has been working closely with customers, partners, and other people in the industry to help ensure a smooth and seamless transition. Although updates have been made available for mobile devices running Windows Mobile software, some users may not have the information that they need or did not follow the steps that are required to apply those updates. The correct end date for DST for 2007 in North America is November 4, 2007. Mobile devices for users who did not update, may have experienced the "fall back" in North America on October 28. Some user's mobile devices and calendars may be one hour early for the following week, if the appropriate updates are not applied. We recommend that customers who have to update, follow the instructions on http://www.microsoft.com/windowsmobile/daylightsaving/default.mspx to update their devices.Windows
Microsoft Windows operating systems KB 942763 is the latest Windows Cumulative Time Zone Update available. KB 942763 will be issued as an "Update Rollup" and available via WSUS. To note, this Knowledge Base article replaces KB 933360. Customers who have updated with the previous Rollup (KB 933360) should carefully review KB 942763 in the section on “Updates from the previous cumulative Windows time zone update” and determine if this update is necessary for their environment. To see such updates in WSUS, go to "Update Classifications" and select "Change," then check "Update Rollups" and sync. The KB will be released to WSUS on November 27th, 2007. More details on the changes for DST start and end times around the world can be found on the Microsoft website at http://www.microsoft.com/dst2007.Windows KB 942763 was issued as an "Update Rollup" and is available via WSUS, replacing KB 933360. For customers using SMS 2003 and ITMU, the DST Update Rollup KB 933360 was superseded by KB 942763 in the wsusscn2.cab file – the catalog consumed by ITMU. As a result, KB 933360 update is no longer available for deployment via ITMU. We encourage customers to run the latest cumulative DST update on their systems as a general rule. All clients that haven't had KB 933360 installed, will now only report that KB 942763 is applicable (due to the way WUA handles and reports superseded KBs) but the clients that have installed the previous update will still report it as installed. In the event KB 933360 was only partially deployed for an environment and not all machines can be readily updated to KB 942763, several options are available, among them:
- Build further collections of machines that do not yet have either update rollup applied, and target those machines with a new patch package which includes KB 942763.
- Continue to roll out KB 933360 to the remainder of the environment using standard software distribution.
- For more information see the SMS 2003 and ITMU section of this update.
After patching the suspect client machines, you may need to address Outlook calendar items that may be displayed incorrectly now that the Windows time zone definitions have been updated. Venezuela announces 2007 Time Zone changesVenezuelan time zone changes: The government of the Bolivarian Republic of Venezuela has announced a change to the time zone for the country, which to date has typically observed South America Western Standard Time. According to current official reports, the start date for new time zone is yet to be determined, but projected to occur on December 9th, 2007. When customers move their Windows clients to the new time zone, clocks will move backwards 30 minutes, from UTC -4:00 to UTC -4:30. This change begins at 2:59:59 PM local time on the start date. Clocks should be moved back to 2:30:00 PM rather than advancing to 3:00:00 AM. For more information, please see Microsoft Knowledge Base article 942763.
Generally, end users do not have to install these updates manually. Updates will be installed via Windows Update beginning on December 11, 2007 rather than downloading and installing these from the Microsoft Download Center. For end users who have their computers managed by a central administrator, please contact your IT administrator for infomration on how computers on your network will be updated.
For a Web log of the most common questions and answers about moving appointments from one time zone to another for Venezuela, visit the following Web site:
Correcting the Outlook/Exchange Calendars of affected usersDetermine which machines/users were affected. This list will be used to create the input file for the Exchange Calendar Update Tool. To determine which users are affected you should identify new machines that were introduced into your environment after August and are not patched with KB 933360. You will need to associate a user with each machine. For each potentially affected user you should check their Calendar to ensure accuracy during the extended DST period. Any Calendars that have appointments which are displayed incorrectly (example: appointments appear to be moved by one hour) during the extended DST period will need to either manually update their appointments so that they appear correctly. Alternatively you can use the Exchange Calendar Update Tool or the Outlook Calendar Update Tool to correct the appointments. The decision for which Calendar Update Tool to use is typically determined by the number of users affected, the number of Calendar items affected and the amount of end user interaction that is acceptable. For instance, if there are a small number of users affected and a small number of Calendar items in each Calendar then having end users run the Outlook Calendar Update Tool or requesting that they manually drag and drop appointments to the correct time could be an acceptable solution. Exchange Calendar Update ToolIf you chose to update the user Calendars with the Exchange Calendar Update Tool then after you have compiled the list of users you will then need to obtain their Legacy Exchange DN. You will then enter the user’s Legacy Exchange DN into a text file along with their mailbox servers Legacy Exchange DN and the users time zone. KB 941018 contains additional information about creating this file and running the Exchange Calendar Update Tool. "Update affected users with the Exchange Calendar Update Tool using the "Only Update Recurring Meetings" Advanced Option in Exchange Calendar Update Configuration Tool which is documented in KB 941018. Please do not update all items in these calendars as you may inadvertently change the time of a single-instance item that is correct. Complete information on how to use the tool can be found here: KB 941018 - How to address daylight saving time by using the Exchange Calendar Update Tool Information about obtaining user LegacyExchangeDN information can be found at:KB 324606 - How to use Legacydn.exe to correct Exchange organization names or Administrative Group names in Exchange Server 2003 or in Exchange 2000 Server Once all recurring items are updated, instruct users to manually correct any remaining items in Outlook that are 1-hour off.
- Print a copy of your calendar during the extended DST period for reference.
- Manually move meetings that you organized to the correct time.
- Send an update for the meeting that you moved to all attendees so that the attendees' calendar reflects the correct time.
- Manually move all single-instance appointments.
- Manually move all recurring appointments within the extended DST period.
Outlook Calendar Update ToolIf you choose to update the user Calendars with the Outlook Calendar Update Tool, then you should use the instructions in KB 931667 and have the users carefully select which appointments that they want to have rebased. They should pay attention to the appointments that occur from October 28, 2007 – November 4, 2007 to ensure the accuracy of those appointments. More information on the Outlook Calendar Update Tool is available at: KB 931667 - How to address the daylight saving time changes in 2007 by using the Time Zone Data Update Tool for Microsoft Office Outlook You may also experience discrepancies in Resource Accounts (Conference Rooms) with double bookings or incorrect times. If this occurs then meeting organizers can update the meetings for an available time and send an update to all attendees. Users should synchronize mobile devices and any additional Outlook clients (i.e. laptops, home machines) after all changes are completed. Sharepoint ServicesWindows SharePoint Services 3.0 and Microsoft Office SharePoint Server customers should be aware of important fixes recently updated that should be installed, particularly those related to daylight saving time. You should install the updates listed in KB 934525. Please visit the Microsoft Web page at http://support.microsoft.com/gp/dst_prodlist#WSS3 for more details. SMS 2003 and ITMU (Inventory Tool for Microsoft Updates)For customers using SMS 2003 and ITMU (Inventory Tool for Microsoft Updates):
KB 931836 DST Update Rollup was superseded by KB 933360 in the wsusscn2.cab file – the catalog consumed by ITMU and the Distribute Software Updates Wizard. As a result, KB 931836 update is no longer available for deployment via ITMU. We encourage customers to run the latest cumulative DST update on their systems as a general rule.However in the event KB 931836 was only partially deployed for an environment and not all machines can be readily updated to KB 933360, several options are available, among them:
- Build further collections of machines that do not yet have either update rollup applied, and target those machines with a new patch package which includes KB 933360.
- Continue to roll out KB 931836 to the remainder of the environment using standard software distribution.
Collections can be based on queries of Add/Remove programs Hardware Inventory data, which is enabled by default in SMS 2003. The relevant Display Names of the updates in question are below: Windows Server 2003 931836 – Update for Windows Server 2003 (KB 931836) 933360 – Update for Windows Server 2003 (KB 933360) Windows XP 931836 – Update for Windows XP (KB 931836) 933360 – Update for Windows XP (KB 933360) DST instructional videos availableThe Microsoft DST Team has put together a few videos to assist you in your DST remediation planning and execution. Click the links below to learn more about the Windows Cumulative Update and the Outlook and Exchange Time Zone Data Update Tools.On-Demand (hosted by Channel9.MSDN.com)
Indiana announces 2007 Time Zone changesIndiana time zone changes: Effective November 4th, the Indiana counties of Knox, Daviess, Martin, Pike, and Dubois will be moving from the Central time zone to Eastern time. These are five 5 counties in Indiana that did not move to Eastern last year when the rest of Indiana moved. We did not release an update for Indiana since directions are to change the time zone to Eastern from Central. For more information please see the following: http://www.microsoft.com/windows/timezone/indiana.mspx.
For a Web log of the most common questions and answers about moving appointments from one time zone to another for Indiana, visit the following Web site:
BlogsFor a Web log of the most common questions and answers about daylight saving time changes affecting Microsoft products, please visit the Technet DST Blog site.  | |