How to make the 2007 daylight saving time changes by using the Update Time Zones Wizard for Microsoft Dynamics CRM 3.0

After you apply update 925874 to update Microsoft Dynamics CRM 3.0 for the 2007 daylight saving time (DST) changes, you may have to change some of the records that are stored in the Microsoft Dynamics CRM database to reflect the new time zone changes. The following scenario is an example of why this data correction is necessary:

1. A user who is assigned the Microsoft Dynamics CRM "(GMT -8:00) Pacific Time (US & Canada)" time zone schedules a task for 8:00 A.M. on March 30, 2007. The user creates the task before update 925874 is applied.
2. This task is stored in the Microsoft Dynamics CRM database as 4:00 P.M. on March 30, 2007. This problem occurs because until update 925874 is applied, this date occurs in standard time.
3. You apply update 925874.
4. The user opens the task that is created in step 1.
5. The task is displayed in Microsoft Dynamics CRM, and it has a due date that is 9:00 A.M. on March 30, 2007. This problem occurs because after you apply update 925874, this date occurs in the new daylight saving time.

This result is incorrect. The user scheduled the appointment for 8:00 A.M., and now the appointment appears at 9:00 A.M. In this example, the Update Time Zones Wizard for Microsoft Dynamics CRM 3.0 finds all the entities for this user that occur between 2:00 A.M. on March 11, 2007 and 2:00 A.M. on April 1, 2007. March 11, 2007 2:00 A.M. is the new DST start date and start time, and 2:00 A.M. on April 1, 2007 is the old DST start date and start time. The wizard adjusts the time by one hour. For this example, the date and the time in the database are changed to 3:00 P.M. on March 30, 2007. Therefore, when the user opens the task, the date and the time appear as 8:00 A.M. on March 30, 2007. This date and this time are the correct date and the correct time.

This problem is fixed in Microsoft Dynamics CRM 3.0 Update Rollup 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about how to prepare for the 2007 daylight saving time (DST 2007) changes for all the affected Microsoft products, visit the following Microsoft Web site: For more information about the Microsoft Dynamics CRM 3.0 server update and about the Microsoft Dynamics CRM 3.0 client update, click the following article number to view the article in the Microsoft Knowledge Base: For more information about Microsoft Dynamics CRM and DST, click the following article number to view the article in the Microsoft Knowledge Base:

Information about how to run the Update Time Zones Wizard multiple times

The Update Time Zones Wizard can be run multiple times. When you apply update 925874, the update creates a candidate table in the OrganizationName_MSCRM database. The candidate table lists the users, the Microsoft Dynamics CRM entities, and the Microsoft Dynamics CRM records that have to be changed to comply with the DST changes. The Update Time Zones Wizard reads the information in the candidate table to obtain a list of the records that may have to be updated. The wizard updates the candidate table by using information about the records that have been updated. Therefore, if you run the wizard after you update the records, the wizard will not update these records again.

Time that is required to run the Update Time Zones Wizard

The time that is required to complete the wizard depends on several factors. These factors include the following factors:

• The number of users who are affected by the DST changes
• The number of records that each user owns

An SQL script that is provided when the wizard is released helps you determine the current time zone settings for users, for sites, and for resources. You can use the results of the script to make decisions when you run the Update Time Zones Wizard.

Microsoft entities that are not updated by the Update Time Zones Wizard

The wizard updates only the entities that are owned. The following list is a list of entities that are not owned, and their date and time fields. These fields are not updated by the wizard. These entities and attributes are listed in the CrmDSTTool_data.csv file and have a DoneUpdate value of 3.

For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base: