In many countries, the start dates and the end dates for daylight saving time (DST) change from year to year. Additionally, countries may change their policies for recognizing daylight saving time, or they may change the local offset from Coordinated Universal Time (UTC). This update includes updated time zone definitions for the following countries:

• Iraq
• Argentina
• Chile
• Iran
• Morocco
• Pakistan
• Venezuela

This update provides the following major DST changes for the following cities in the countries that are listed in the "Introduction" section. Additionally, if the Timezone.xml file was previously edited, this update overrides those changes.

Note The * character signifies a new time zone.

Baghdad
• DST was removed.

Buenos Aires*
• DST starts on December 30, 2007. This is the fifth Sunday of December.
• DST ends on March 16, 2008. This is the third Sunday of March.

Santiago
• DST ends on March 29, 2008. This is the last Saturday of March.

Tehran
• DST starts on March 21, 2008. This is the third Friday of March.
• DST ends on September 23, 2008. This is the fourth Tuesday of September.

Casablanca*
• DST starts on June 1, 2008. This is the first Sunday of June.
• DST ends on September 27, 2008. This is the last Saturday of September.

Islamabad, Karachi*
• DST starts on June 1, 2008. This is the first Sunday of June.
• DST ends on August 31, 2008. This is the last Sunday of August.

Caracas*
• UTC offset was changed from UTC minus 4 hours to UTC minus 4.5 hours.

This update also provides changes to the following stsadm.exe -o tzmove command:Examples of how this command is used:

• stsadm -o tzmove -from 1 -to 2 -update all
  
  For all sites in the farm that have a time zone ID equal to 1, this command changes the time zone ID to 2. Additionally, this command updates all date and time values in these sites accordingly.
• stsadm -o tzmove -from 1 -to 2 -update before -date YYYYMMDD
  
  For all sites in the farm that have a time zone ID equal to 1, this command changes the time zone ID to 2. Additionally, this command updates all date and time values in these sites that were modified before a particular date that you specify.

Sample scenarios

• Assume that you installed an update that created a new time zone definition. Now you want all sites in the farm that have a specific time zone definition to be updated to the new time zone definition. However, you want to maintain the correct date and time values. In this scenario, run the following command:
  stsadm -o tzmove -from 32 -to 85 -update before -date YYYYMMDD
  Note In this command, 32 is the ID of the old time zone definition that is found in the Timezone.xml file. (ID 32 represents Buenos Aires and Georgetown.). And 85 is the ID of the new time zone definition that is found in Timezone.xml file. (ID 85 represents Buenos Aires.) YYYYMMDD is the date on which you installed the update that created the new time zone definition. Only those date and time values that are created after this date will be updated.

Important If you decide to use the stsadm.exe -o tzmove command, make sure that you carefully follow the instructions that are described in the following Microsoft Knowledge Base article: To successfully use the stsadm.exe -o tzmove command to fix date and time values that are affected by this update, be aware that the following -name attribute values are required by thestsadm.exe -o tzmove command for each time zone change in this update:

• Baghdad:
  -name baghdad2008
• Santiago:
  -name santiago2008
• Tehran:
  -name tehran2008

Additionally, to successfully use the stsadm.exe -o tzmove command to move all sites that have a specific time zone definition in the farm to a new time zone definition that is provided by this update, note the following Timezone.xml IDs for each new time zone:

• Buenos Aires:
  85
• Casablanca:
  86
• Islamabad, Karachi:
  87
• Caracas:
  88

Update installation details

How to obtain and install the update

To obtain the 32-bit version of the Windows SharePoint Services update together with installation instructions and deployment strategies, visit the following Microsoft Web site:To obtain the 64-bit version of the Windows SharePoint Services update together with installation instructions and deployment strategies, visit the following Microsoft Web site:Note The installation of the update to Windows SharePoint Services involves a series of steps that must be completed in the correct sequence. For more information about how to deploy software updates for Windows SharePoint Services 3.0, visit the following Microsoft Web site:

Downloadable files in the update

How to determine whether the update is installed

The update contains the files that have the versions that are listed in the following table.

32-bit version of the Windows SharePoint Services update

64-bit version of the Windows SharePoint Services update

Information for administrators about .msp files

This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp file is packaged in a self-extracting executable file. The .msp files in the following table are distributed in this update.

.msp files in the 32-bit version of the Windows SharePoint Services update

.msp files in the 64-bit version of the Windows SharePoint Services update

Update replacement information

This update replaces the following updates:

• 951695  (http://kbalertz.com/Feedback.aspx?kbNumber=951695/ ) Description of the Infrastructure Update for Windows SharePoint Services 3.0: July 15, 2008
• 955594  (http://kbalertz.com/Feedback.aspx?kbNumber=955594/ ) Description of the Windows SharePoint Services 3.0 hotfix package: July 22, 2008
• 956057  (http://kbalertz.com/Feedback.aspx?kbNumber=956057/ ) Description of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): August 26, 2008
• 957109  (http://kbalertz.com/Feedback.aspx?kbNumber=957109/ ) Description of the Windows SharePoint Services 3.0 hotfix package (Wssmui.msp): August 26, 2008