Microsoft KB Archive/914837

= Description of issues that are related to time zone changes in Indiana =

Article ID: 914837

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, 64-Bit Enterprise Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows XP Home Edition
 * Microsoft Windows XP Media Center Edition 2002
 * Microsoft Windows XP Professional
 * Microsoft Windows XP Professional x64 Edition
 * Microsoft Windows CE 5.0
 * Microsoft Windows Mobile 2003 software for Pocket PC Standard Edition
 * Microsoft Windows Mobile 2003 software for Smartphone
 * Microsoft Windows Mobile 2003 software for Pocket PC Standard Edition
 * Microsoft Windows Mobile 2003 Second Edition software for Smartphone
 * Microsoft Windows Mobile 2003 software for Pocket PC Standard Edition
 * Microsoft Windows Mobile 2003 software for Smartphone
 * Windows Mobile 5.0 for Pocket PC
 * Windows Mobile 5.0 for Pocket PC Phone Edition
 * Windows Mobile 5.0 for Smartphones
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Server

-





SUMMARY
''On April 2, 2006, Indiana will start using daylight saving time. Most counties in Indiana will use the Eastern Time zone. However, some counties will use the Central Time zone.

Microsoft Windows users in Indiana will have to change their Windows time zone settings from Indiana (East) to either Eastern Time (US & Canada) or Central Time (US & Canada). The Indiana (East) time zone setting will become obsolete and should not be used in the future. Indiana residents should use local sources of information to determine the correct time zone.

This article describes issues that are related to the time zone changes in Indiana. This article also describes how and when to change the time zone setting. How you make this change depends on whether you must change one computer or many computers.''



INTRODUCTION
On April 2, 2006, all counties in Indiana will start using daylight saving time. Residents who are in the Eastern Time zone will set clocks forward one hour on that day to start using Eastern Time. Residents who are in the Central Time zone will not change their clocks on April 2, 2006, but will start using Central Time.

Currently, Microsoft Windows products contain the (GMT -5:00) Indiana (East) time zone setting. This setting does not use daylight saving time. You must update Windows-based computers in the affected time zones as follows:
 * Eastern Time zone

If you are in a county that will use the Eastern Time zone, set your time zone to Eastern Time (US & Canada) as soon as possible. If you do this, new meetings or appointments that repeat and that you set up between now and April 2, 2006, will be accurate.
 * Central Time zone (before April 2)

If you are in a county that will use the Central Time zone, we recommend that you do not change your time zone until April 2, 2006. This step helps prevent the wrong offset for meeting requests between now and April 2.
 * Central Time zone (on April 2)

On April 2, your actual time will not change, but you will officially move to the Central Time zone. Your actual time will change in October 2006. However, you must change your time zone on April 2 to Central Time (US & Canada), and then reset your clock to the correct time. After this change, you may have to update or resend requests for meetings that repeat and then verify other meeting requests in your calendar programs. This step will enable the computer clock to automatically adjust in October. Therefore, any new recurring meetings that are created between April 2 and October 28, 2006, and that are scheduled for a date on or after October 28, 2006, will be correct in your calendar.

Important You should not wait until October to adjust your clock.

Note You should use local information to determine which counties will use Central Time and which counties will use Eastern Time.



MORE INFORMATION
Depending on whether you have to change the time zone setting on a single computer or on multiple network computers in an organization, use one of the following methods.

Note We recommend that you print your Outlook calendar before you change time zones or apply an Indiana Time Zone Change hotfix. Compare meeting schedules before and after the time zone change to make sure that the information is correct.

Method 1: Manually change the time zone setting on a single computer
You can change the time zone setting at any time. If you change the time zone setting before April 2, 2006, the computer clock will adjust automatically to the correct time. If you discover that you must change a computer clock after April 2, 2006, you should first change the time zone to the correct time zone setting, and then adjust the clock setting for the correct local time. We recommend that you determine the new time zone setting and then change to it based on the timing information in the &quot;Introduction&quot; section.

To change the time zone setting on a single computer, follow these steps.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
 * 1) Determine the new time zone for your county.
 * 2) Click Start, click Control Panel, and then click Date, Time, Language, and Regional Options.
 * 3) Under or click a Control Panel icon, click Date and Time.
 * 4) On the Time Zone tab, click (GMT-5:00) Eastern Time (US & Canada) or (GMT-6:00) Central Time (US & Canada) in the list, and then click OK.

Method 2: Change the time zone setting on multiple network computers
Use Group Policy to change the time zone setting on network computers. To change the time zone on network computers, follow these steps on the Windows-based domain controller.

Notes
 * You must be able to determine the county in which all affected computers are located before you implement a broad Group Policy setting.
 * The Indiana Time Zone Change hotfix automates the time zone change for networked computers that are in a locked down deployment. Because users who do not have administrative credentials cannot change the time and date settings on their computers, the hotfix enables administrators to make the changes by using automated methods. The automated methods use startup scripts.

This hotfix automatically shifts the computer to the specified Eastern Time or Central Time zone and enables daylight saving time. (This hotfix was created for Indiana and assumes that the computer is using the Indiana (East) time zone. Computers that use other time zones require that an administrator use the manual method to change the time zone and daylight saving time settings.) Users who have administrator credentials and who apply this hotfix will also have the time zone on their computers changed to Eastern Time or Central Time and the daylight saving time setting turned on. However, when these users open Date and Time in Control Panel to verify that the time zone has changed, they may see that the daylight saving time check box is cleared (turned off). The daylight saving time setting is turned on after the hotfix is applied even though the check box is cleared. Users can click to select the daylight saving time check box and then click Apply to make sure that daylight saving time is turned on. Another way to test the time zone and daylight saving time settings is to open a command prompt and to set the time and date to the start of daylight saving time. To do this, you use the time and date commands. Notice that when you set the time and date to 2 A.M. and April 2, 2006, the time moves ahead to 3 A.M.

How to deploy the Indiana Time Zone Change hotfixes
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN;CNTACTMS]

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.'''

Note If a computer is configured for Eastern Time or Central Time, but the Automatically adjust clock for daylight savings changes''' option is disabled, these hotfixes will not change this setting. To enable this option, you must manually change the setting.

How to create a startup script to change the time zone on Windows XP-based and Windows 2003-based computers
 Contact Microsoft Product Support Services, and then request the Indiana Time Zone Change hotfix for the appropriate time zone. Hotfix 916452 is to change to the Eastern Time zone. Hotfix 916453 is to change to the Central Time zone. You may need both hotfixes. Therefore, make sure that you are specific about whether you need one time zone hotfix or whether you need both time zone hotfixes.

To obtain the correct hotfix files, you must also provide the following information:  The operating system version (Windows XP or Windows Server 2003) The platform (x86, x64, or IA-64)

Note Customers who are running Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, or Microsoft Windows 2000 Server must have an Extended Hotfix Agreement to receive non-security hotfix support for these operating systems. Per the life cycle policy of Windows 2000, non-security hotfixes are no longer made or distributed for Windows 2000 unless a system is covered by an Extended Hotfix Agreement. Use Notepad to create a new file. (If you are already running a startup script, you can just add information to the existing startup script.)  Copy the following lines into the Notepad file: <pre class="fixed_text">REM Eastern Time Zone updates REM WindowsXP-KB916452-x86-ENU.exe /quiet REM WindowsServer2003-KB916452-x86-ENU.exe /quiet

REM Central Time Zone updates REM WindowsXP-KB916453-x86-ENU.exe /quiet REM WindowsServer2003-KB916453-x86-ENU.exe /quiet Remove the “REM” part of the line for your specific time zone and for each operating system version that you want to update. For example, if you only want the hotfix to apply to Windows XP computers in the Central Time zone, remove &quot;REM&quot; from the “WindowsXP-KB916453-x86-ENU.exe /quiet” line. Multiple operating systems can receive the hotfix from one script, but only for a single time zone. If you remove &quot;REM&quot; for the same operating system for both time zones, the script will update to the last time zone that is listed. </li> Save the logon script as “UpdateTZ.cmd”. Or, if you have multiple sites that need different time zone changes, save the logon scripts by using specific names, such as “UpdateTZEastern.cmd” and “UpdateTZCentral.cmd”.</li> Copy the appropriate hotfix file(s) and the UpdateTZ.cmd file to the logon script share (NETLOGON) on a domain controller. On a Microsoft Windows 2000-based or Microsoft Server 2003-based domain controller, copy the hotfix file to the following location:

C:\Windows\Sysvol\Sysvol\ \Scripts

This information assumes that you have installed Windows on the C drive in the default locations on all domain controllers.

Note You can also verify the PATH location of the scripts directory by typing the following command at a command prompt:

net share netlogon

If you have more than one domain controller, wait for the script to replicate to all domain controllers. Depending on your configuration and site connectivity, replication may take several hours to finish. Verify that the appropriate files are on all domain controllers before you assume that replication has completed successfully.</li></ol>

How to create a startup script to modify the time zone for Windows 2000-based computers
<ol> Use Notepad to create a new file. (If you are already running a startup script, you can just add information to the existing startup script.)</li>  Copy the following lines into the Notepad file: <pre class="fixed_text">REM Eastern Time Zone Update REM CONTROL.EXE TIMEDATE.CPL,,/Z Eastern Standard Time

REM Central Time Zone Update REM CONTROL.EXE TIMEDATE.CPL,,/Z Central Standard Time Remove the “REM” part of the line for your specific time zone. If you remove &quot;REM&quot; for both time zones, the script will update to the last time zone that is listed. </li> Save the script as a .cmd file.</li> Create a Group Policy object specifically for the time zone change. Depending on how a customer's environment is divided up, you can deploy the startup script either by using an organizational unit (OU) policy or by using a site policy.</li> After all computers have received the changes, remove the Group Policy object from the OU or from the site.</li></ol>

How to use Group Policy to run the startup script
Note We recommend that you use a site policy instead of a domain policy because most sites are located in a single time zone. Domains can exist across wide geographical locations and time zones. <ol> Click Start, click Administrative Tools, and then click Active Directory Sites and Services.</li> Expand the Sites folder, right-click a site to which you want to deploy this hotfix, and then click Properties.</li> Click the Group Policy tab, and then click New.</li> Name the Group Policy object &quot;Time Zone Update-Eastern&quot; or &quot;Time Zone Update-Central&quot;, depending on the hotfix that you are deploying.</li> Click Edit.</li> Expand Computer Configuration, expand Windows Settings, click Scripts (Startup/Shutdown), and then double-click Startup in the right pane.</li> Click Add, and then click Browse.</li> In the File name field, type \\ \NetLogon. is the name of the domain to which you are deploying the hotfixes.</li> Click Open, and then click the UpdateTZ.cmd file.</li> <li>Click OK two times, and then exit the Group Policy Object Editor.</li> <li>Assign the Group Policy settings to other sites, if appropriate. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Right-click the site, click Properties, click the Group Policy tab, and then click Add.</li> <li>Click the All tab, and then click the policy that you created.</li></ol> </li></ol>

Notes
 * These steps will increase the startup times of the computers that are deploying the new policy. After the appropriate time zone changes have been deployed in your environment, remove the policy. Configure any new computers to use the correct time zone.
 * Depending on the number of domain controllers in the environment, we recommend that you manually update them.
 * If you use this script for Windows XP-based clients, we recommend that you disable &quot;Fast Logon Optimization&quot; to make sure that the script runs the first time that you use it.

How to use System Management Server (SMS) to deploy the hotfixes
If you use Microsoft Systems Management Server (SMS), you can take advantage of the scheduling and targeting capabilities of SMS. For organizations that have clients in different counties, this method may be especially useful. For example, by using SMS, you can target script deployment based on user groups, on subnet locations, or on other unique identifiers that indicate a computer's location. SMS also lets you to distribute software packages, scripts, and hotfixes by using elevated privileges. For more information about how to use SMS for distribution, see the Scenarios and Procedures for Microsoft Systems Management Server 2003: Software Distribution and Patch Management guide. To obtain this guide, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=32f2bb4c-42f8-4b8d-844f-2553fd78049f&DisplayLang=en

How to change the time zone setting on Microsoft Windows Mobile Devices Pocket PC

 * 1) Tap Start, tap Settings, and then tap the System tab.
 * 2) Tap Clock & Alarms.
 * 3) Tap the Time tab if it is not already selected, and then tap GMT-5 Eastern US or GMT-6 Cent. America in the Home list.
 * 4) Tap ok.

How to change the time zone setting on Microsoft Windows CE-based devices
Note Procedures may vary with the device or with the OEM. We recommend that you examine the device manual for the latest instructions.
 * 1) Click Start, point to Settings, click Control Panel, and then double-click Date/Time.
 * 2) In Time Zone list, select (GMT-5:00) Eastern Time (US & Canada) or (GMT-6:00) Central Time (US & Canada), and then click OK.

How to change the time zone setting on a smartphone

 * 1) Select Start, select Settings, select Clock & Alarm, and then select Date and Time.
 * 2) In Time Zone list, select GMT-5 Eastern US or GMT-6 Cent. America, and then click OK.

Restart requirements
We recommend that you restart a computer after you change the time zone setting. You may have to restart the computer if any services or programs are running that use the time zone information. However, you may only have to restart services and programs that use the time zone information.

Testing
In a large organization, we recommend that you test these changes on a small group of computers before you make a change that will affect the whole organization. Before April 2, 2006, you can adjust the time zone setting of servers, workstations, and devices that are located in Indiana. Devices may include mobile devices and Personal Digital Assistants (PDAs). Do not wait until April 2, 2006, to change the time zone setting. By changing the time zone setting in advance, you make sure that the time adjusts automatically for daylight saving time.

Order of changes
The following list is the suggested order for changing time settings and for adjusting calendars:
 * 1) Change time zone settings on servers.
 * 2) Change time zone settings on client and workstation computers.
 * 3) Adjust calendars if it is required.

Calendar scheduling
Time zones in Windows are based on Greenwich Mean Time (GMT). Many calendar and schedule programs, such as Microsoft Outlook, use GMT time to store appointment information. For these programs, appointments typically adjust automatically to the correct local time based on the computer’s time zone setting. Ask the individual calendar software vendor to make sure that this is true for your calendar software.

In calendar programs that store appointments by using GMT, appointments change to the correct time when the time zone is changed.

Sample scenario

 * Jason is in the Indiana (East) time zone.
 * Ben is in the Central Time (US & Canada) zone.
 * Lynn is in the Eastern Time (US & Canada) zone.

On January 24, 2006, Jason scheduled a 9:00 A.M. Indiana (East) time zone appointment with Ben and with Lynn to occur April 4, 2006. The scheduled appointment automatically appears in Ben’s calendar as 8:00 A.M. and in Lynn’s calendar as 10:00 A.M. This behavior occurs because Ben's calendar program displays appointments based on the local time zone.

When the time changes on April 2, 2006, in Indiana, Jason’s network administrator uses Group Policy to change the local computer time to Eastern Time. Jason’s appointments that are scheduled after April 2, 2006, are automatically updated to reflect the new time zone. Therefore, the appointment on April 4, 2006, is automatically changed to 10:00 A.M. Although this behavior may appear confusing to Indiana residents, it is correct and shows the time that Lynn already had on her calendar.

If Jason wants the appointment to occur at 9:00 A.M. after the time zone change, he must manually move the appointment back in his calendar. After he does this, he can notify users that the appointment time has changed. However, Jason should consider that others who are invited to the appointment may have already been in the Eastern Time zone. These attendees may plan on attending the 10:00 A.M. appointment and may not be available at 9:00 A.M. Jason should examine the calendars of the other meeting attendees before he moves the appointment.

For more information about how to adjust repeating appointments in Microsoft Outlook, click the following article number to view the article in the Microsoft Knowledge Base:

915577 How to incorporate Indiana's time zone change into Outlook

How to control local calendars in Indiana
Typically, users have scheduled appointments with other users in Indiana. These appointments have to be moved manually. We recommend that you do not change local time zone appointments until after network administrators have changed the time setting on servers in Indiana.

You can make this change before April 2, 2006. As soon as the server times are changed, you can change the local time of the workstations. Users will now see that appointments that are scheduled after April 2, 2006, have moved up one hour. Users can now manually move the appointments as needed. Updates to the appointments will be sent to users and will appropriately reflect the correct time.

Meetings or events that repeat
Meetings or events that repeat in calendar programs may store the local time zone adjustment in each meeting or event. You may have to manually resend or re-create meetings or events that repeat after you change the server or workstation time zone settings.

For more information about how to adjust repeating appointments in Microsoft Outlook, click the following article number to view the article in the Microsoft Knowledge Base:

915577 How to incorporate Indiana's time zone change into Outlook

Outlook Web Access
Outlook Web Access (OWA) also has a time zone setting. Each user must set this manually. Users must log on to OWA, click Options, locate the time zone setting, and then change the OWA time zone to either Central Time or Eastern Time. When OWA users log on, they may see an information bar that indicates that the local time differs from the OWA time zone setting if they do not update OWA.

Keywords: kbinfo KB914837

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.