XP SP3 Clients Not Getting DST Updates

Re WSUS 3.0 SP1, our XP SP3 clients are not getting Daylight Savings Time
updates and hence display the wrong time even after getting other updates
after installation of SP3. What is the latest DST update and why isn't it
being pushed out via WSUS? We have update rollups enabled. We do not however
use WSUS for SP3 itself.

"mcintoshs" <> wrote in message
news:F540E8B2-3CB8-45FA-A731-...
> Re WSUS 3.0 SP1, our XP SP3 clients are not getting Daylight Savings Time
> updates and hence display the wrong time even after getting other updates
> after installation of SP3. What is the latest DST update and why isn't it
> being pushed out via WSUS?

The latest update is "Update for Windows XP (KB955839)", released in
December, 2008,
which superceded "Update for Windows XP (KB951072)", released in August,
2008,
which superceded "Update for Windows XP (KB942763)", released in August,
2008,
which superceded "Update for Windows XP (KB933360)", released in August,
2007,
which superceded "Update for Windows XP (KB931836)", released in August,
2007,
which was the original update.

Windows XP SP3 superceded KB942763, but you'll still need KB955839 as it
updates anything previously updated by XP SP3.

All of those updates are available in the WSUS catalog; if you're
experiencing issues with DST updates on your systems, perhaps you've not
approved KB955839 for installation? or it has not been installed by the XP
SP3 systems.





--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Thanks for the response. I approved that 955839 update long ago and it shows
as approved in the mgmt interface under update rollups but it doesn't seem to
be installing. Also, there is a large red x to the left of that rollup entry
in WSUS mgmt interface and indicates 82% install rate. My own system is SP3
and it doesn't show as installed. What could be causing this failure to
install?
I have not approved SP3 itself for auto download and install because there
have been issues. We apply it selectively.


"Lawrence Garvin [MVP]" wrote:

> "mcintoshs" <> wrote in message
> news:F540E8B2-3CB8-45FA-A731-...
> > Re WSUS 3.0 SP1, our XP SP3 clients are not getting Daylight Savings Time
> > updates and hence display the wrong time even after getting other updates
> > after installation of SP3. What is the latest DST update and why isn't it
> > being pushed out via WSUS?
>
> The latest update is "Update for Windows XP (KB955839)", released in
> December, 2008,
> which superceded "Update for Windows XP (KB951072)", released in August,
> 2008,
> which superceded "Update for Windows XP (KB942763)", released in August,
> 2008,
> which superceded "Update for Windows XP (KB933360)", released in August,
> 2007,
> which superceded "Update for Windows XP (KB931836)", released in August,
> 2007,
> which was the original update.
>
> Windows XP SP3 superceded KB942763, but you'll still need KB955839 as it
> updates anything previously updated by XP SP3.
>
> All of those updates are available in the WSUS catalog; if you're
> experiencing issues with DST updates on your systems, perhaps you've not
> approved KB955839 for installation? or it has not been installed by the XP
> SP3 systems.
>
>
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"mcintoshs" <> wrote in message
news:3B89536D-9C94-450D-A81A-...
> Thanks for the response. I approved that 955839 update long ago and it
> shows
> as approved in the mgmt interface under update rollups but it doesn't seem
> to
> be installing.

Then you have an issue to resolve -- which, btw, might have absolutely
nothing to do with this particular update.

> Also, there is a large red x to the left of that rollup entry
> in WSUS mgmt interface and indicates 82% install rate. My own system is
> SP3
> and it doesn't show as installed. What could be causing this failure to
> install?

That's why there are logfiles. Find the entry in your WindowsUpdate.log
where the installation of KB955839 was attempted on your system and review
the results.

> I have not approved SP3 itself for auto download and install because there
> have been issues. We apply it selectively.

Okay.

Irrelevant to this issue, though, you do understand?


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Searched the windowsupdate.log file on my computer. There is not a single
instance of it in the log.

"Lawrence Garvin [MVP]" wrote:

> "mcintoshs" <> wrote in message
> news:3B89536D-9C94-450D-A81A-...
> > Thanks for the response. I approved that 955839 update long ago and it
> > shows
> > as approved in the mgmt interface under update rollups but it doesn't seem
> > to
> > be installing.
>
> Then you have an issue to resolve -- which, btw, might have absolutely
> nothing to do with this particular update.
>
> > Also, there is a large red x to the left of that rollup entry
> > in WSUS mgmt interface and indicates 82% install rate. My own system is
> > SP3
> > and it doesn't show as installed. What could be causing this failure to
> > install?
>
> That's why there are logfiles. Find the entry in your WindowsUpdate.log
> where the installation of KB955839 was attempted on your system and review
> the results.
>
> > I have not approved SP3 itself for auto download and install because there
> > have been issues. We apply it selectively.
>
> Okay.
>
> Irrelevant to this issue, though, you do understand?
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

>> Thanks for the response. I approved that 955839 update long ago and it
>> shows
>> as approved in the mgmt interface under update rollups but it doesn't
>> seem to
>> be installing.
[...]
>> Also, there is a large red x to the left of that rollup entry
>> in WSUS mgmt interface and indicates 82% install rate. My own system
>> is SP3
>> and it doesn't show as installed. What could be causing this failure to
>> install?

Check Add/Remove Programs (with "show updates" enabled) to check whether or not
KB955839 is actually installed.

What does WSUS show as the status of KB955839 on your computer?

Type this at a command line:

wuauclt /detectnow

Wait twenty minutes then post the contents of WindowsUpdate.log starting from
five minutes before you issued the command.

Harry.

2009-07-21 08:22:45:961 1292 4b4 AU Triggering AU detection through DetectNow
API
2009-07-21 08:22:45:961 1292 4b4 AU Triggering Online detection
(non-interactive)
2009-07-21 08:22:45:961 1292 8a4 AU #############
2009-07-21 08:22:45:961 1292 8a4 AU ## START ## AU: Search for updates
2009-07-21 08:22:45:961 1292 8a4 AU #########
2009-07-21 08:22:45:961 1292 8a4 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {21186851-DA20-4BBE-A36D-A83CFF52724E}]
2009-07-21 08:22:45:961 1292 b1c Agent *************
2009-07-21 08:22:45:961 1292 b1c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-07-21 08:22:45:961 1292 b1c Agent *********
2009-07-21 08:22:45:961 1292 b1c Agent * Online = Yes; Ignore download
priority = No
2009-07-21 08:22:45:961 1292 b1c Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2009-07-21 08:22:45:961 1292 b1c Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-07-21 08:22:45:961 1292 b1c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-07-21 08:22:45:977 1292 b1c Misc Microsoft signed: Yes
2009-07-21 08:22:45:992 1292 b1c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-07-21 08:22:45:992 1292 b1c Misc Microsoft signed: Yes
2009-07-21 08:22:45:992 1292 b1c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-07-21 08:22:46:008 1292 b1c Misc Microsoft signed: Yes
2009-07-21 08:22:46:008 1292 b1c Setup *********** Setup: Checking whether
self-update is required ***********
2009-07-21 08:22:46:008 1292 b1c Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-07-21 08:22:46:024 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2009-07-21 08:22:46:039 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-07-21 08:22:46:039 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:039 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:086 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:102 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:102 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:102 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:149 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:149 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 08:22:46:149 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-07-21 08:22:46:149 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-07-21 08:22:46:164 1292 b1c Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-07-21 08:22:46:164 1292 b1c Setup * IsUpdateRequired = No
2009-07-21 08:22:52:367 1292 b1c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-07-21 08:22:52:367 1292 b1c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://gpssec/ClientWebService/client.asmx
2009-07-21 08:22:52:571 1292 b1c PT WARNING: Cached cookie has expired or
new PID is available
2009-07-21 08:22:52:571 1292 b1c PT Initializing simple targeting cookie,
clientId = e5eba84e-4825-4a29-a89b-a88633d78b0c, target group = Servers, DNS
name = netco-11712.glastonburyus.org
2009-07-21 08:22:52:571 1292 b1c PT Server URL =
http://gpssec/SimpleAuthWebService/SimpleAuth.asmx
2009-07-21 08:24:17:916 1292 b1c PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2009-07-21 08:24:17:916 1292 b1c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://gpssec/ClientWebService/client.asmx
2009-07-21 08:24:23:400 1292 b1c Agent * Added update
{4E41018C-72E6-4F63-9F05-AC088F1352F8}.101 to search result
2009-07-21 08:24:23:400 1292 b1c Agent * Added update
{19986D1F-0652-4816-8D54-0ADD7D1D444C}.102 to search result
2009-07-21 08:24:23:400 1292 b1c Agent * Added update
{C85C0842-5CD9-47D5-BFDB-08E5504E5DC9}.102 to search result
2009-07-21 08:24:23:400 1292 b1c Agent * Added update
{6FF1BD9D-C442-4C06-93F3-A768877A5254}.101 to search result
2009-07-21 08:24:23:400 1292 b1c Agent * Found 4 updates and 52 categories
in search; evaluated appl. rules of 630 out of 942 deployed entities
2009-07-21 08:24:23:416 1292 b1c Agent *********
2009-07-21 08:24:23:416 1292 b1c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-07-21 08:24:23:416 1292 b1c Agent *************
2009-07-21 08:24:23:416 1292 1610 AU >>## RESUMED ## AU: Search for
updates [CallId = {21186851-DA20-4BBE-A36D-A83CFF52724E}]
2009-07-21 08:24:23:416 1292 1610 AU # 4 updates detected
2009-07-21 08:24:23:416 1292 1610 AU #########
2009-07-21 08:24:23:416 1292 1610 AU ## END ## AU: Search for updates
[CallId = {21186851-DA20-4BBE-A36D-A83CFF52724E}]
2009-07-21 08:24:23:416 1292 1610 AU #############
2009-07-21 08:24:23:432 1292 1610 AU AU setting next detection timeout to
2009-07-22 07:28:19
2009-07-21 08:24:28:416 1292 b1c Report REPORT EVENT:
{BCBFDC5D-834A-4EEB-90EE-3EB8838FDB83} 2009-07-21
08:24:23:416-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 4 updates.
2009-07-21 08:24:28:416 1292 b1c Report REPORT EVENT:
{1B0DB4F7-4008-4A06-805D-4E0862AD6CB2} 2009-07-21
08:24:23:416-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2009-07-21 08:25:28:542 1292 b1c Report Uploading 2 events using cached
cookie, reporting URL =
http://gpssec/ReportingWebService/Re...ebService.asmx
2009-07-21 08:25:28:542 1292 b1c Report Reporter successfully uploaded 2
events.
2009-07-21 08:25:48:308 1292 8a4 AU AU received policy change subscription
event


"Harry Johnston [MVP]" wrote:

> >> Thanks for the response. I approved that 955839 update long ago and it
> >> shows
> >> as approved in the mgmt interface under update rollups but it doesn't
> >> seem to
> >> be installing.
> [...]
> >> Also, there is a large red x to the left of that rollup entry
> >> in WSUS mgmt interface and indicates 82% install rate. My own system
> >> is SP3
> >> and it doesn't show as installed. What could be causing this failure to
> >> install?
>
> Check Add/Remove Programs (with "show updates" enabled) to check whether or not
> KB955839 is actually installed.
>
> What does WSUS show as the status of KB955839 on your computer?
>
> Type this at a command line:
>
> wuauclt /detectnow
>
> Wait twenty minutes then post the contents of WindowsUpdate.log starting from
> five minutes before you issued the command.
>
> Harry.
>

"mcintoshs" <> wrote in message
news:4FB19A33-28E4-4729-BE10-...

> 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> {4E41018C-72E6-4F63-9F05-AC088F1352F8}.101 to search result

Security Update for Windows XP (KB971633)


> 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> {19986D1F-0652-4816-8D54-0ADD7D1D444C}.102 to search result

Security Update for Windows XP (KB961371)


> 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> {C85C0842-5CD9-47D5-BFDB-08E5504E5DC9}.102 to search result

Update for Microsoft Office Outlook 2003 Junk Mail Filter (KB971931)


> 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> {6FF1BD9D-C442-4C06-93F3-A768877A5254}.101 to search result

Cumulative Security Update for Active X Killbits for Windows XP (KB973346)


> 2009-07-21 08:24:23:400 1292 b1c Agent * Found 4 updates and 52
> categories
> in search; evaluated appl. rules of 630 out of 942 deployed entities

Looks like the update is not being detected for installation.

Either it's already installed, or it's not approved for the group this
machine scanned against.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Is there a registry key which would have a definitive listing of all updates
installed? I've looked at "Add/Remove Programs" with "show updates" enabled
and it doesn't show up there nor in the C:\Windows location.

"Lawrence Garvin [MVP]" wrote:

> "mcintoshs" <> wrote in message
> news:4FB19A33-28E4-4729-BE10-...
>
> > 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> > {4E41018C-72E6-4F63-9F05-AC088F1352F8}.101 to search result
>
> Security Update for Windows XP (KB971633)
>
>
> > 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> > {19986D1F-0652-4816-8D54-0ADD7D1D444C}.102 to search result
>
> Security Update for Windows XP (KB961371)
>
>
> > 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> > {C85C0842-5CD9-47D5-BFDB-08E5504E5DC9}.102 to search result
>
> Update for Microsoft Office Outlook 2003 Junk Mail Filter (KB971931)
>
>
> > 2009-07-21 08:24:23:400 1292 b1c Agent * Added update
> > {6FF1BD9D-C442-4C06-93F3-A768877A5254}.101 to search result
>
> Cumulative Security Update for Active X Killbits for Windows XP (KB973346)
>
>
> > 2009-07-21 08:24:23:400 1292 b1c Agent * Found 4 updates and 52
> > categories
> > in search; evaluated appl. rules of 630 out of 942 deployed entities
>
> Looks like the update is not being detected for installation.
>
> Either it's already installed, or it's not approved for the group this
> machine scanned against.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"mcintoshs" <> wrote in message
news:11BC8A7B-EA68-45B1-8F7B-...
> Is there a registry key which would have a definitive listing of all
> updates
> installed? I've looked at "Add/Remove Programs" with "show updates"
> enabled
> and it doesn't show up there nor in the C:\Windows location.

There are a number of places that might have evidence of such, but you've
pretty much hit the authoritative ones.

If the update does not show in A/R Prog,
and there's no uninstall folder in %systemroot%
and there's no key in
HKLM\Software\Microsoft\Windows\CurrentVersion\Uni nstall
and the PC is behaving like it doesn't know the correct DST applicability
rules...

Then I'd say it's safe to say the update is not installed,
and it's obvious it's not being detected,
which leaves us with only one possibility:

It's not Approved for the group containing this machine,
or the *content* for the update (KB955839) has not yet been downloaded to
the WSUS Server.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin