On 9 February 2007 we released a Windows Time Zone Update Rollup, KB 931836 to the Download Center. This update rollup replaces KB 928388 (global time zone update) and KB 929120 (W. Australia Time Zone Update). It includes all the time zone changes in the previously released time zone updates and additional time zone changes that were adopted and announced after we created KB 928388.
KB931836 will be available on MU and through WSUS on February 13, 2007 as well.
We would like to alert our customers as this is a slight change from what I bloged on Dec. 13th, 2005 when we indicated the Windows Time Zone Update (KB 928388) was going to be assigned a high priority or critical classification for the February 13th release.
While the Windows time zone update will be categorized as an Update Rollup and hence offered automatically to customers who signed-up for Automatic Updates, it will be under KB 931836. At the same time as the update roll-up goes out, KB 928388 and KB 929120 will become superseded. A few additional noteworthy considerations:
- KB 931836 installs over any previously installed time zone update (KB 928388 or KB 929120 or both of them). Customers do not need to uninstall any of the previous KBs to install the update rollup.
- KB 931836 is cumulative, so it includes all changes that KB 928388 and 929120 included. Customers who have not installed the previous time zone update only need to install KB 931836 to have the latest time zone data
- Customers who already deployed KB 928388 should evaluate if any of the 6 specific time zone changes addressed in KB 931836 merit deploying this update immediately. If systems are not directly affected, deployment can be scheduled at the next available opportunity. Microsoft recommends that all customers standardize on the most current Windows cumulative time zone update to ensure consistency of the time zone database on all systems.
- Customers who use SMS ITMU will be able to use ITMU to deploy the update as it is classified as an Update Rollup.
- Outlook and Exchange tools and patches are available and will be released on Office Update and Microsoft Update and available to WSUS on Feb 13th as well.
For more information please go to our Microsoft DST 2007 portal: http://www.microsoft.com/dst2007.
I figured you haven't been annoyed enough with my DST posts and it's time I did another one.... since
So I guess there are absolutely no plans to release a Windows 2000 hotfix for the DST?
Have not seen the KB931836 show up in WSUS and it is now the 15th. Where can I find it? Was it delayed to WSUS. I can use scripts to post to my XP systems but would prefer WSUS.
Have not seen KB931836 show up in WSUS yet and it is now the 15th. Was it delayed?
You need to change Update Classification to include "Update Rollups"
Are there any hot fixes for Windows 2000 Servers?
If not what is the procedure to align the date/time to DST?
I still don't have this update KB931386 in WSUS and I have "Update Rollups" selected in WSUS.
No KB933836 in WSUS for me either. "Update Rollups" is selected. Any ideas?
Correction.. I wasn't SYNCING update rollups, only trying to view them!
Same problem for me: Selected "Update Rollups" for synchronization, and hit sychornize now.
Then searched updates for "All updates; Any approval; Any time" Still don't see KB931836.
Am I missing something here? Was the KB # changed?
Help! I can synchronize and find KB981836 just fine but when I check to see if it will update my XP systems (set the action to "Detect only" to verify) it shows that NONE of my XP systems need the update even though they ALL have XP SP2 installed. Please help!!!!
just looked over hte post. i typed "KB981836" in it but i meant "KB931836"
Why is our WSUS deployed 931836 contain TZCHANGE.EXE with a 5.2.3790.2872 (srv03_sp1_gdr.070130-2240) file version and if we manually download from the KB article, TZCHANGE.EXE is 5.2.3790.2876 (srv03_sp1_gdr.070205-2234)
Apparrently diff updates for diff systems as well as even changes to the inital updates for given systems, my guess is that ms could be failing to offer the users the latest changes for various updating means. Could that be possible?
Ref. ms site search lists many versions of the update, ref...
some examples listed...
Tzchange.exe: 5.2.3790.616: 58,368: 27-Nov-2006: 08:59: x86: None: RTMGDR:
Tzchange.exe: 5.2.3790.616: 58,368: 27-Nov-2006: 09:17: x86: None: RTMQFE:
Tzchange.exe: 5.2.3790.2840: 60,928: 27-Nov-2006: 09:30: x86: SP1: SP1GDR
Tzchange.exe: 5.2.3790.615: 58,368: 18-Nov-2006: 12:03: x86: None: RTMGDR:
Tzchange.exe: 5.2.3790.615: 58,368: 18-Nov-2006: 12:10: x86: None: RTMQFE:
Tzchange.exe: 5.2.3790.2836: 60,928: 18-Nov-2006: 12:29: x86: SP1: SP1GDR
Tzchange.exe: 5.2.3790.642: 58,368: 02-Feb-2007: 09:02: x86: None: RTMGDR:
Tzchange.exe: 5.2.3790.642: 58,368: 02-Feb-2007: 09:51: x86: None: RTMQFE:
Tzchange.exe: 5.2.3790.2876: 60,928: 06-Feb-2007: 09:17: x86: SP1: SP1GDR