Discussion:
WSUS client not updating
(too old to reply)
Trond Mahle
2005-08-22 10:52:05 UTC
Permalink
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install" almost 2
weeks ago. I consider to run WindowsUpdate manually, but are afraid I only
postpone the problem. Any suggestions? Here are today's entries in the local
log file:

2005-08-22 07:11:16 1048 c0 Misc =========== Logging initialized (build:
5.8.0.2469, tz: +0200) ===========
2005-08-22 07:11:16 1048 c0 Misc = Process: C:\Windows\System32\svchost.exe
2005-08-22 07:11:16 1048 c0 Misc = Module: C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
2005-08-22 07:11:16 1048 c0 Agent * Base directory:
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * WSUS status server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access disabled: No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0 downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes (Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
2005-08-22 07:12:17 1048 778 Setup * Inf file:
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5 categories in
search
2005-08-22 07:12:24 1048 778 Report *********** Report: Initializing static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c

2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:24 1048 778 Agent *************
2005-08-22 07:12:24 1048 e0 AU >>## RESUMED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU # 0 updates detected
2005-08-22 07:12:24 1048 e0 AU #########
2005-08-22 07:12:24 1048 e0 AU ## END ## AU: Search for updates [CallId
= {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU #############
2005-08-22 07:12:24 1048 e0 AU AU setting next detection timeout to
2005-08-22 09:26:23
2005-08-22 07:12:29 1048 e0 Report REPORT EVENT:
{A54E443A-FBD5-45A5-B98D-41EA1817BC92} 2005-08-22
07:12:24+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
2005-08-22 07:12:29 1048 e0 Report REPORT EVENT:
{6E9C9BAF-04E1-4132-9D18-5D674ED33E42} 2005-08-22
07:12:24+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 07:21:04 1048 42c Report Uploading 2 events using cached cookie,
reporting URL = http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 07:21:04 1048 42c Report Reporter successfully uploaded 2 events.
2005-08-22 11:00:10 1048 c0 AU Forced install timer expired for scheduled
install
2005-08-22 11:26:23 1048 c0 AU #############
2005-08-22 11:26:23 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 11:26:23 1048 c0 AU #########
2005-08-22 11:26:23 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:23 1048 42c Agent *************
2005-08-22 11:26:23 1048 42c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:23 1048 42c Agent *********
2005-08-22 11:26:25 1048 42c Setup *********** Setup: Checking whether
self-update is required ***********
2005-08-22 11:26:25 1048 42c Setup * Inf file:
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup * IsUpdateRequired = No
2005-08-22 11:26:27 1048 42c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 11:26:27 1048 42c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 11:26:27 1048 42c PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 11:26:27 1048 42c PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 11:26:29 1048 42c Agent * Found 0 updates and 5 categories in
search
2005-08-22 11:26:29 1048 42c Agent *********
2005-08-22 11:26:29 1048 42c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:29 1048 42c Agent *************
2005-08-22 11:26:29 1048 42c AU >>## RESUMED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU # 0 updates detected
2005-08-22 11:26:29 1048 42c AU #########
2005-08-22 11:26:29 1048 42c AU ## END ## AU: Search for updates [CallId
= {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU #############
2005-08-22 11:26:29 1048 42c AU AU setting next detection timeout to
2005-08-22 14:08:53
2005-08-22 11:26:34 1048 42c Report REPORT EVENT:
{D6746135-D6E6-4B02-A49E-FA179F4C252D} 2005-08-22
11:26:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
2005-08-22 11:26:34 1048 42c Report REPORT EVENT:
{CC7DEDDF-30F5-475D-9F1B-69AEA47B63AF} 2005-08-22
11:26:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 11:35:05 1048 42c Report Uploading 2 events using cached cookie,
reporting URL = http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 11:35:05 1048 42c Report Reporter successfully uploaded 2 events.
Patrick
2005-08-22 15:36:48 UTC
Permalink
Try using Bitsadmin. This is part of the support tools for XP and 2003. You
can determine the jobs set and then clear them if they are stacked up. This
may "unclog" the pipe allowing your client to perform the updates.
Post by Trond Mahle
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install" almost 2
weeks ago. I consider to run WindowsUpdate manually, but are afraid I only
postpone the problem. Any suggestions? Here are today's entries in the local
5.8.0.2469, tz: +0200) ===========
2005-08-22 07:11:16 1048 c0 Misc = Process: C:\Windows\System32\svchost.exe
2005-08-22 07:11:16 1048 c0 Misc = Module: C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * WSUS status server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access disabled: No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0 downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes (Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5 categories in
search
2005-08-22 07:12:24 1048 778 Report *********** Report: Initializing static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c
2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:24 1048 778 Agent *************
2005-08-22 07:12:24 1048 e0 AU >>## RESUMED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU # 0 updates detected
2005-08-22 07:12:24 1048 e0 AU #########
2005-08-22 07:12:24 1048 e0 AU ## END ## AU: Search for updates [CallId
= {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU #############
2005-08-22 07:12:24 1048 e0 AU AU setting next detection timeout to
2005-08-22 09:26:23
{A54E443A-FBD5-45A5-B98D-41EA1817BC92} 2005-08-22
07:12:24+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{6E9C9BAF-04E1-4132-9D18-5D674ED33E42} 2005-08-22
07:12:24+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 07:21:04 1048 42c Report Uploading 2 events using cached cookie,
reporting URL = http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 07:21:04 1048 42c Report Reporter successfully uploaded 2 events.
2005-08-22 11:00:10 1048 c0 AU Forced install timer expired for scheduled
install
2005-08-22 11:26:23 1048 c0 AU #############
2005-08-22 11:26:23 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 11:26:23 1048 c0 AU #########
2005-08-22 11:26:23 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:23 1048 42c Agent *************
2005-08-22 11:26:23 1048 42c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:23 1048 42c Agent *********
2005-08-22 11:26:25 1048 42c Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup * IsUpdateRequired = No
2005-08-22 11:26:27 1048 42c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 11:26:27 1048 42c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 11:26:27 1048 42c PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 11:26:27 1048 42c PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 11:26:29 1048 42c Agent * Found 0 updates and 5 categories in
search
2005-08-22 11:26:29 1048 42c Agent *********
2005-08-22 11:26:29 1048 42c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:29 1048 42c Agent *************
2005-08-22 11:26:29 1048 42c AU >>## RESUMED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU # 0 updates detected
2005-08-22 11:26:29 1048 42c AU #########
2005-08-22 11:26:29 1048 42c AU ## END ## AU: Search for updates [CallId
= {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU #############
2005-08-22 11:26:29 1048 42c AU AU setting next detection timeout to
2005-08-22 14:08:53
{D6746135-D6E6-4B02-A49E-FA179F4C252D} 2005-08-22
11:26:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{CC7DEDDF-30F5-475D-9F1B-69AEA47B63AF} 2005-08-22
11:26:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 11:35:05 1048 42c Report Uploading 2 events using cached cookie,
reporting URL = http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 11:35:05 1048 42c Report Reporter successfully uploaded 2 events.
Lawrence Garvin
2005-08-22 17:47:38 UTC
Permalink
There are not likely any jobs hung in the BITS queue because the WUA is not
detecting any updates eligible for installation. If the WUA had previously
detected updates for installation, initiated the download, but the download
failed -- the WUA would continue to report those updates as "detected" until
they are successfully /installed/.

This is not happening, so it's highly unlikely there is anything caught in
the BITS queue.
Post by Patrick
Try using Bitsadmin. This is part of the support tools for XP and 2003.
You
can determine the jobs set and then clear them if they are stacked up.
This
may "unclog" the pipe allowing your client to perform the updates.
Post by Trond Mahle
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install" almost 2
weeks ago. I consider to run WindowsUpdate manually, but are afraid I only
postpone the problem. Any suggestions? Here are today's entries in the local
5.8.0.2469, tz: +0200) ===========
C:\Windows\System32\svchost.exe
C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing
Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * WSUS status server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access disabled: No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0
downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day
at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes
(Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5 categories
in
search
2005-08-22 07:12:24 1048 778 Report *********** Report: Initializing
static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c
2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:24 1048 778 Agent *************
2005-08-22 07:12:24 1048 e0 AU >>## RESUMED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU # 0 updates detected
2005-08-22 07:12:24 1048 e0 AU #########
2005-08-22 07:12:24 1048 e0 AU ## END ## AU: Search for updates
[CallId
= {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU #############
2005-08-22 07:12:24 1048 e0 AU AU setting next detection timeout to
2005-08-22 09:26:23
{A54E443A-FBD5-45A5-B98D-41EA1817BC92} 2005-08-22
07:12:24+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{6E9C9BAF-04E1-4132-9D18-5D674ED33E42} 2005-08-22
07:12:24+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 07:21:04 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 07:21:04 1048 42c Report Reporter successfully uploaded 2
events.
2005-08-22 11:00:10 1048 c0 AU Forced install timer expired for scheduled
install
2005-08-22 11:26:23 1048 c0 AU #############
2005-08-22 11:26:23 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 11:26:23 1048 c0 AU #########
2005-08-22 11:26:23 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:23 1048 42c Agent *************
2005-08-22 11:26:23 1048 42c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:23 1048 42c Agent *********
2005-08-22 11:26:25 1048 42c Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup * IsUpdateRequired = No
2005-08-22 11:26:27 1048 42c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 11:26:27 1048 42c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 11:26:27 1048 42c PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 11:26:27 1048 42c PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 11:26:29 1048 42c Agent * Found 0 updates and 5 categories
in
search
2005-08-22 11:26:29 1048 42c Agent *********
2005-08-22 11:26:29 1048 42c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:29 1048 42c Agent *************
2005-08-22 11:26:29 1048 42c AU >>## RESUMED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU # 0 updates detected
2005-08-22 11:26:29 1048 42c AU #########
2005-08-22 11:26:29 1048 42c AU ## END ## AU: Search for updates
[CallId
= {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU #############
2005-08-22 11:26:29 1048 42c AU AU setting next detection timeout to
2005-08-22 14:08:53
{D6746135-D6E6-4B02-A49E-FA179F4C252D} 2005-08-22
11:26:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{CC7DEDDF-30F5-475D-9F1B-69AEA47B63AF} 2005-08-22
11:26:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 11:35:05 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 11:35:05 1048 42c Report Reporter successfully uploaded 2
events.
Lawrence Garvin
2005-08-22 17:46:10 UTC
Permalink
Trond.. the client is /not/ detecting the updates.

This can happen for a number of reasons:

(1) The client is configured in a different client-side group than the
approvals are set for.
In this case, the client is looking for approvals for
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
(Uhh.... question about the name "ME Laptops"... does this mean /your/
laptops as in me, mine, ours, and yours -- or does this mean "ME" as in
Millenium Edition?????. If the latter, then you should know that WSUS does
not support "Millenium Edition", Windows NT, or Windows 9x.)

The good news, though, is that I can see that this particular client is
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
(2) There is a /required/ (pre-requisite) update that is not approved for
installation. This occurs in some instances where SP2 is approved for
installation to an XP SP1 system, but not all post-SP1 updates are approved
for installation. (Contrary to released statements, it now appears that SP2
does not include /all/ post-SP1 updates.) It's generally not an issue for
SP2, except in the case where the client has not yet installed Windows
Installer v3.1 -- which will prevent the detection of /all/ updates.

Otherwise, there appears to be no abnormal behavior in this client. It's
simply not detecting any updates approved for installation, which pretty
much means that, however it happened, there are no updates eligible for
installation on this client at this time. I would suggest scanning the
Updates webpage of the WSUSAdmin console, to see what updates are reported
as "Needed" for this client, and make sure all "Needed" clients are actually
approved for installation for the "ME Laptops" target group.

To get a quick check on any WSUS-related activity at the client, review the
logfile at %windir%\SoftwareDistribution\ReportingEvents.log, which should
include entries for the successful installation of Windows Installer v3.1,
and any other updates detected, downloaded, scheduled for installation,
installed, and the successful restart of the system following that
installation.
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install" almost 2
weeks ago. I consider to run WindowsUpdate manually, but are afraid I only
postpone the problem. Any suggestions? Here are today's entries in the local
5.8.0.2469, tz: +0200) ===========
C:\Windows\System32\svchost.exe
C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * WSUS status server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access disabled: No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0 downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day
at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes
(Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5 categories in
search
2005-08-22 07:12:24 1048 778 Report *********** Report: Initializing
static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c
2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:24 1048 778 Agent *************
2005-08-22 07:12:24 1048 e0 AU >>## RESUMED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU # 0 updates detected
2005-08-22 07:12:24 1048 e0 AU #########
2005-08-22 07:12:24 1048 e0 AU ## END ## AU: Search for updates [CallId
= {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU #############
2005-08-22 07:12:24 1048 e0 AU AU setting next detection timeout to
2005-08-22 09:26:23
{A54E443A-FBD5-45A5-B98D-41EA1817BC92} 2005-08-22
07:12:24+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{6E9C9BAF-04E1-4132-9D18-5D674ED33E42} 2005-08-22
07:12:24+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 07:21:04 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 07:21:04 1048 42c Report Reporter successfully uploaded 2
events.
2005-08-22 11:00:10 1048 c0 AU Forced install timer expired for scheduled
install
2005-08-22 11:26:23 1048 c0 AU #############
2005-08-22 11:26:23 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 11:26:23 1048 c0 AU #########
2005-08-22 11:26:23 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:23 1048 42c Agent *************
2005-08-22 11:26:23 1048 42c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:23 1048 42c Agent *********
2005-08-22 11:26:25 1048 42c Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup * IsUpdateRequired = No
2005-08-22 11:26:27 1048 42c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 11:26:27 1048 42c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 11:26:27 1048 42c PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 11:26:27 1048 42c PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 11:26:29 1048 42c Agent * Found 0 updates and 5 categories in
search
2005-08-22 11:26:29 1048 42c Agent *********
2005-08-22 11:26:29 1048 42c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:29 1048 42c Agent *************
2005-08-22 11:26:29 1048 42c AU >>## RESUMED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU # 0 updates detected
2005-08-22 11:26:29 1048 42c AU #########
2005-08-22 11:26:29 1048 42c AU ## END ## AU: Search for updates
[CallId
= {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU #############
2005-08-22 11:26:29 1048 42c AU AU setting next detection timeout to
2005-08-22 14:08:53
{D6746135-D6E6-4B02-A49E-FA179F4C252D} 2005-08-22
11:26:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{CC7DEDDF-30F5-475D-9F1B-69AEA47B63AF} 2005-08-22
11:26:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 11:35:05 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 11:35:05 1048 42c Report Reporter successfully uploaded 2
events.
Trond Mahle
2005-08-22 21:06:02 UTC
Permalink
Lawrence, thanks for your detailed answer!

(1) This WXP SP2 client is a member of group "ME laptops". ME is an
abbreviation for our company name - Moxy Engineering - see www.moxy.no :-).

(2) The following patches are approved for Install on clients in group "ME
Laptops", but have not yet been installed on this "problem" laptop:

- Critical Update for Windows XP (KB886185)
- Security Update for Microsoft Windows (KB898458)
- Security Update for Microsoft Messenger (KB887472)
- Security Update for Windows XP (KB885835)
- Security Update for Windows XP (KB890047)
- Security Update for Windows XP (KB890175)
- Security Update for Windows XP (KB896358)
- Update for Windows XP (KB896358)

(3) The problem occured when the laptop had a harddisk crash and we had to
buy/swap physical disk. After installing WXP SP2 on the new disk, the laptop
showed up again in group "Unassigned computers". We then deleted the old
entry in group "ME Laptops" and moved this new entry to group "ME Laptops". A
lot of patches were then installed, except the 8 remaining mentioned above.
Windows Installer 3.1 is not among these, so I think that's OK.

I have tried to log on the laptop as Administrator, but that didn't help.
All other 11 laptops in the group are OK (updated). Please advise what to try
next, I don't know what to try now.

Regards Trond

----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Trond.. the client is /not/ detecting the updates.
(1) The client is configured in a different client-side group than the
approvals are set for.
In this case, the client is looking for approvals for
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
(Uhh.... question about the name "ME Laptops"... does this mean /your/
laptops as in me, mine, ours, and yours -- or does this mean "ME" as in
Millenium Edition?????. If the latter, then you should know that WSUS does
not support "Millenium Edition", Windows NT, or Windows 9x.)
The good news, though, is that I can see that this particular client is
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
(2) There is a /required/ (pre-requisite) update that is not approved for
installation. This occurs in some instances where SP2 is approved for
installation to an XP SP1 system, but not all post-SP1 updates are approved
for installation. (Contrary to released statements, it now appears that SP2
does not include /all/ post-SP1 updates.) It's generally not an issue for
SP2, except in the case where the client has not yet installed Windows
Installer v3.1 -- which will prevent the detection of /all/ updates.
Otherwise, there appears to be no abnormal behavior in this client. It's
simply not detecting any updates approved for installation, which pretty
much means that, however it happened, there are no updates eligible for
installation on this client at this time. I would suggest scanning the
Updates webpage of the WSUSAdmin console, to see what updates are reported
as "Needed" for this client, and make sure all "Needed" clients are actually
approved for installation for the "ME Laptops" target group.
To get a quick check on any WSUS-related activity at the client, review the
logfile at %windir%\SoftwareDistribution\ReportingEvents.log, which should
include entries for the successful installation of Windows Installer v3.1,
and any other updates detected, downloaded, scheduled for installation,
installed, and the successful restart of the system following that
installation.
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install" almost 2
weeks ago. I consider to run WindowsUpdate manually, but are afraid I only
postpone the problem. Any suggestions? Here are today's entries in the local
5.8.0.2469, tz: +0200) ===========
C:\Windows\System32\svchost.exe
C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * WSUS status server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access disabled: No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0 downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day
at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes
(Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5 categories in
search
2005-08-22 07:12:24 1048 778 Report *********** Report: Initializing
static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c
2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:24 1048 778 Agent *************
2005-08-22 07:12:24 1048 e0 AU >>## RESUMED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU # 0 updates detected
2005-08-22 07:12:24 1048 e0 AU #########
2005-08-22 07:12:24 1048 e0 AU ## END ## AU: Search for updates [CallId
= {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU #############
2005-08-22 07:12:24 1048 e0 AU AU setting next detection timeout to
2005-08-22 09:26:23
{A54E443A-FBD5-45A5-B98D-41EA1817BC92} 2005-08-22
07:12:24+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{6E9C9BAF-04E1-4132-9D18-5D674ED33E42} 2005-08-22
07:12:24+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 07:21:04 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 07:21:04 1048 42c Report Reporter successfully uploaded 2
events.
2005-08-22 11:00:10 1048 c0 AU Forced install timer expired for scheduled
install
2005-08-22 11:26:23 1048 c0 AU #############
2005-08-22 11:26:23 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 11:26:23 1048 c0 AU #########
2005-08-22 11:26:23 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:23 1048 42c Agent *************
2005-08-22 11:26:23 1048 42c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:23 1048 42c Agent *********
2005-08-22 11:26:25 1048 42c Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup * IsUpdateRequired = No
2005-08-22 11:26:27 1048 42c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 11:26:27 1048 42c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 11:26:27 1048 42c PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 11:26:27 1048 42c PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 11:26:29 1048 42c Agent * Found 0 updates and 5 categories in
search
2005-08-22 11:26:29 1048 42c Agent *********
2005-08-22 11:26:29 1048 42c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:29 1048 42c Agent *************
2005-08-22 11:26:29 1048 42c AU >>## RESUMED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU # 0 updates detected
2005-08-22 11:26:29 1048 42c AU #########
2005-08-22 11:26:29 1048 42c AU ## END ## AU: Search for updates
[CallId
= {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU #############
2005-08-22 11:26:29 1048 42c AU AU setting next detection timeout to
2005-08-22 14:08:53
{D6746135-D6E6-4B02-A49E-FA179F4C252D} 2005-08-22
11:26:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{CC7DEDDF-30F5-475D-9F1B-69AEA47B63AF} 2005-08-22
11:26:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 11:35:05 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 11:35:05 1048 42c Report Reporter successfully uploaded 2
events.
Lawrence Garvin
2005-08-23 05:16:23 UTC
Permalink
Post by Trond Mahle
Lawrence, thanks for your detailed answer!
You're most welcome.... here are some more details to ponder... :-)
Post by Trond Mahle
(1) This WXP SP2 client is a member of group "ME laptops". ME is an
abbreviation for our company name - Moxy Engineering - see www.moxy.no :-).
Well.. I'm glad it wasn't the Millenium Edition thingy.... shucks, never
thought of it as a company acronym.
Post by Trond Mahle
(2) The following patches are approved for Install on clients in group "ME
- Critical Update for Windows XP (KB886185)
- Security Update for Microsoft Windows (KB898458)
- Security Update for Microsoft Messenger (KB887472)
- Security Update for Windows XP (KB885835)
- Security Update for Windows XP (KB890047)
- Security Update for Windows XP (KB890175)
- Security Update for Windows XP (KB896358)
- Update for Windows XP (KB896358)
Thanks for the list. We'll keep this handy for future reference.

But here's where I'd like to clarify something...
Post by Trond Mahle
(3) The problem occured when the laptop had a harddisk crash and we had to
buy/swap physical disk. After installing WXP SP2 on the new disk, the laptop
showed up again in group "Unassigned computers".
Are you using client-side targeting, or server-side targeting. My assumption
was "client-side" since the WUA is logging target name information. At least
it appears that the client /thinks/ it's using client-side targeting. If
you're using server-side targeting, then the client behaved as expected --
that is, a new system will always appear in "Unassigned computers" until it
is moved (at the server console) into it's assigned group.
Post by Trond Mahle
We then deleted the old
entry in group "ME Laptops" and moved this new entry to group "ME
Laptops".
Again, this implies that you're using server-side targeting, and you made
the change at the WSUS console, not by applying a different GPO with the new
target name. That's my assumption at this point.
Post by Trond Mahle
A lot of patches were then installed, except the 8 remaining mentioned
above.
Is there any record in the logs that the client ever detected or downloaded
those updates? If so, there would be entries in the ReportingEvents.log
found in
%windir%\SoftwareDistribution\ReportingEvents.log.

If there is no record that the WUA ever detected the updates, the question
becomes: Why is the detection failing?
Post by Trond Mahle
Windows Installer 3.1 is not among these, so I think that's OK.
Actually, it's /not/ okay. Windows Installer v3.1 should have been the
/first/ update detected and installed as soon as the new client contacted
the WSUS server, /unless/ you've slipstreamed the Windows Installer v3.1
code into your image, or your image master had been previously patched to
include Windows Installer v3.1 before the image was created.
Post by Trond Mahle
I have tried to log on the laptop as Administrator, but that didn't help.
All other 11 laptops in the group are OK (updated). Please advise what to try
next, I don't know what to try now.
I think the next step is to tell me exactly what date/time this system was
reinstalled, and then post all of the entries in the ReportingEvents.log
file starting at that date/time. Let's find out exactly what the client has
installed, or not installed, and detected or not detected.

As for the updates themselves...

KB898458 does not install on any of my XP SP2 systems. Unless the
Step-by-Step Interactive Training application is installed, the update is
N/A.
KB887472 has two considerations:
- there are two revisions of this update, Rev 10, released 2/8/05 --
which is what's installed on my XP SP2 systems,
and Rev 50, released 4/12/05 -- which my systems also report as "Not
Needed".
- if Windows Messenger is not installed, this update is N/A.
KB890047 is superceded by KB893086
KB890175 is superceded by KB896358

and..not listed in your list is KB898461, which is a WSUS-mandatory update,
released 7/26/05, which will also need to be installed prior to anything
else being detected, and may also create dependencies for some other updates
that need to use the code contained in this update.
Post by Trond Mahle
Regards Trond
----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Trond.. the client is /not/ detecting the updates.
(1) The client is configured in a different client-side group than the
approvals are set for.
In this case, the client is looking for approvals for
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
(Uhh.... question about the name "ME Laptops"... does this mean /your/
laptops as in me, mine, ours, and yours -- or does this mean "ME" as in
Millenium Edition?????. If the latter, then you should know that WSUS does
not support "Millenium Edition", Windows NT, or Windows 9x.)
The good news, though, is that I can see that this particular client is
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
(2) There is a /required/ (pre-requisite) update that is not approved for
installation. This occurs in some instances where SP2 is approved for
installation to an XP SP1 system, but not all post-SP1 updates are approved
for installation. (Contrary to released statements, it now appears that SP2
does not include /all/ post-SP1 updates.) It's generally not an issue for
SP2, except in the case where the client has not yet installed Windows
Installer v3.1 -- which will prevent the detection of /all/ updates.
Otherwise, there appears to be no abnormal behavior in this client. It's
simply not detecting any updates approved for installation, which pretty
much means that, however it happened, there are no updates eligible for
installation on this client at this time. I would suggest scanning the
Updates webpage of the WSUSAdmin console, to see what updates are reported
as "Needed" for this client, and make sure all "Needed" clients are actually
approved for installation for the "ME Laptops" target group.
To get a quick check on any WSUS-related activity at the client, review the
logfile at %windir%\SoftwareDistribution\ReportingEvents.log, which should
include entries for the successful installation of Windows Installer v3.1,
and any other updates detected, downloaded, scheduled for installation,
installed, and the successful restart of the system following that
installation.
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install"
almost
2
weeks ago. I consider to run WindowsUpdate manually, but are afraid I only
postpone the problem. Any suggestions? Here are today's entries in the local
5.8.0.2469, tz: +0200) ===========
C:\Windows\System32\svchost.exe
C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access disabled: No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0 downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day
at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes
(Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required
version
=
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5 categories in
search
2005-08-22 07:12:24 1048 778 Report *********** Report: Initializing
static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c
2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:24 1048 778 Agent *************
2005-08-22 07:12:24 1048 e0 AU >>## RESUMED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU # 0 updates detected
2005-08-22 07:12:24 1048 e0 AU #########
2005-08-22 07:12:24 1048 e0 AU ## END ## AU: Search for updates [CallId
= {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:24 1048 e0 AU #############
2005-08-22 07:12:24 1048 e0 AU AU setting next detection timeout to
2005-08-22 09:26:23
{A54E443A-FBD5-45A5-B98D-41EA1817BC92} 2005-08-22
07:12:24+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{6E9C9BAF-04E1-4132-9D18-5D674ED33E42} 2005-08-22
07:12:24+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 07:21:04 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 07:21:04 1048 42c Report Reporter successfully uploaded 2
events.
2005-08-22 11:00:10 1048 c0 AU Forced install timer expired for scheduled
install
2005-08-22 11:26:23 1048 c0 AU #############
2005-08-22 11:26:23 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 11:26:23 1048 c0 AU #########
2005-08-22 11:26:23 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:23 1048 42c Agent *************
2005-08-22 11:26:23 1048 42c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:23 1048 42c Agent *********
2005-08-22 11:26:25 1048 42c Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required
version
=
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 11:26:25 1048 42c Setup * IsUpdateRequired = No
2005-08-22 11:26:27 1048 42c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 11:26:27 1048 42c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 11:26:27 1048 42c PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 11:26:27 1048 42c PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 11:26:29 1048 42c Agent * Found 0 updates and 5 categories in
search
2005-08-22 11:26:29 1048 42c Agent *********
2005-08-22 11:26:29 1048 42c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 11:26:29 1048 42c Agent *************
2005-08-22 11:26:29 1048 42c AU >>## RESUMED ## AU: Search for updates
[CallId = {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU # 0 updates detected
2005-08-22 11:26:29 1048 42c AU #########
2005-08-22 11:26:29 1048 42c AU ## END ## AU: Search for updates
[CallId
= {150CBA46-8C72-4512-96F9-B37F2EAA8DDB}]
2005-08-22 11:26:29 1048 42c AU #############
2005-08-22 11:26:29 1048 42c AU AU setting next detection timeout to
2005-08-22 14:08:53
{D6746135-D6E6-4B02-A49E-FA179F4C252D} 2005-08-22
11:26:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{CC7DEDDF-30F5-475D-9F1B-69AEA47B63AF} 2005-08-22
11:26:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-08-22 11:35:05 1048 42c Report Uploading 2 events using cached
cookie,
reporting URL =
http://moxy-tst/ReportingWebService/ReportingWebService.asmx
2005-08-22 11:35:05 1048 42c Report Reporter successfully uploaded 2
events.
Trond Mahle
2005-08-23 11:09:03 UTC
Permalink
Thanks again for your time, I'm impressed of your extensive answer! I'll try
to answer as good as possible, please see below in the text. I feel we may be
able to solve this problem!
Post by Lawrence Garvin
Post by Trond Mahle
Lawrence, thanks for your detailed answer!
You're most welcome.... here are some more details to ponder... :-)
Post by Trond Mahle
(1) This WXP SP2 client is a member of group "ME laptops". ME is an
abbreviation for our company name - Moxy Engineering - see www.moxy.no :-).
Well.. I'm glad it wasn't the Millenium Edition thingy.... shucks, never
thought of it as a company acronym.
Post by Trond Mahle
(2) The following patches are approved for Install on clients in group "ME
- Critical Update for Windows XP (KB886185)
- Security Update for Microsoft Windows (KB898458)
- Security Update for Microsoft Messenger (KB887472)
- Security Update for Windows XP (KB885835)
- Security Update for Windows XP (KB890047)
- Security Update for Windows XP (KB890175)
- Security Update for Windows XP (KB896358)
- Update for Windows XP (KB896358)
Thanks for the list. We'll keep this handy for future reference.
But here's where I'd like to clarify something...
Post by Trond Mahle
(3) The problem occured when the laptop had a harddisk crash and we had to
buy/swap physical disk. After installing WXP SP2 on the new disk, the laptop
showed up again in group "Unassigned computers".
Are you using client-side targeting, or server-side targeting. My assumption
was "client-side" since the WUA is logging target name information. At least
it appears that the client /thinks/ it's using client-side targeting. If
you're using server-side targeting, then the client behaved as expected --
that is, a new system will always appear in "Unassigned computers" until it
is moved (at the server console) into it's assigned group.
I will say we use a combination of client-side and server-side targeting...
:-) We have enabled the setting "Enable client-side targeting" in Group
Policy Object Editor (Computer Configuration / Administrative Templates /
Windows Components / Windows Update) which put all laptops into WSUS group
"ME laptops". But at the same time we have choosed this option in the WSUS
Console / Options / Computer Options: "Use the Move computers task in Windows
Server Update Services". That's why all computers still appear in "Unassigned
computers" and we move them manually. The reason is that it's an easy way to
identify new computers entering into the system while we still are in a test
mode...
Post by Lawrence Garvin
Post by Trond Mahle
We then deleted the old
entry in group "ME Laptops" and moved this new entry to group "ME
Laptops".
Again, this implies that you're using server-side targeting, and you made
the change at the WSUS console, not by applying a different GPO with the new
target name. That's my assumption at this point.
See explanation above...
Post by Lawrence Garvin
Post by Trond Mahle
A lot of patches were then installed, except the 8 remaining mentioned
above.
Is there any record in the logs that the client ever detected or downloaded
those updates? If so, there would be entries in the ReportingEvents.log
found in
%windir%\SoftwareDistribution\ReportingEvents.log.
No, I don't find any of the 8 KB-numbers searching in this file.
Post by Lawrence Garvin
If there is no record that the WUA ever detected the updates, the question
becomes: Why is the detection failing?
Post by Trond Mahle
Windows Installer 3.1 is not among these, so I think that's OK.
Actually, it's /not/ okay. Windows Installer v3.1 should have been the
/first/ update detected and installed as soon as the new client contacted
the WSUS server, /unless/ you've slipstreamed the Windows Installer v3.1
code into your image, or your image master had been previously patched to
include Windows Installer v3.1 before the image was created.
I find this sentence in the ReportingEvents.log that verify that Windows
Installer 3.1 is OK:
"Installation successful and restart required for the following update:
Microsoft Windows Installer 3.1"
Post by Lawrence Garvin
Post by Trond Mahle
I have tried to log on the laptop as Administrator, but that didn't help.
All other 11 laptops in the group are OK (updated). Please advise what to try
next, I don't know what to try now.
I think the next step is to tell me exactly what date/time this system was
reinstalled, and then post all of the entries in the ReportingEvents.log
file starting at that date/time. Let's find out exactly what the client has
installed, or not installed, and detected or not detected.
The system was re-installed 04.08.2005 (august), and I post the complete
content of ReportingEvents.log since then. I put it below your last question
to avoid disorder...
Post by Lawrence Garvin
As for the updates themselves...
KB898458 does not install on any of my XP SP2 systems. Unless the
Step-by-Step Interactive Training application is installed, the update is
N/A.
I checked my own laptop now, and here KB898458 was installed 16.06.2005 by
WSUS.
Post by Lawrence Garvin
- there are two revisions of this update, Rev 10, released 2/8/05 --
which is what's installed on my XP SP2 systems,
and Rev 50, released 4/12/05 -- which my systems also report as "Not
Needed".
- if Windows Messenger is not installed, this update is N/A.
I checked my own laptop now, and here KB887472 was installed 24.02.2005 by
WUS.
Post by Lawrence Garvin
KB890047 is superceded by KB893086
KB890175 is superceded by KB896358
OK, but I thought WSUS handle that itself?
Post by Lawrence Garvin
and..not listed in your list is KB898461, which is a WSUS-mandatory update,
released 7/26/05, which will also need to be installed prior to anything
else being detected, and may also create dependencies for some other updates
that need to use the code contained in this update.
I checked my own laptop now, and here KB898461 was installed 25.07.2005 by
WSUS (or downloaded? I look at the date of the folder
c:\windows\$NtUninstallKB898461$).

****************************************************************
ReportingEvents.log (GPO: We have scheduled automatic update to 11:00 AM
every day)
****************************************************************

Oops, I got this message when I copied in the file content here and tried to
post this reply:

Your post is too long. Please reduce the amount of text. (Limit = 30000,
Current = 73257)

I'll try instead to mail it direct to you on ***@nospam.swbell.net.

Did you receive it?

****************************************************************
Post by Lawrence Garvin
Post by Trond Mahle
Regards Trond
----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Trond.. the client is /not/ detecting the updates.
(1) The client is configured in a different client-side group than the
approvals are set for.
In this case, the client is looking for approvals for
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
(Uhh.... question about the name "ME Laptops"... does this mean /your/
laptops as in me, mine, ours, and yours -- or does this mean "ME" as in
Millenium Edition?????. If the latter, then you should know that WSUS does
not support "Millenium Edition", Windows NT, or Windows 9x.)
The good news, though, is that I can see that this particular client is
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
(2) There is a /required/ (pre-requisite) update that is not approved for
installation. This occurs in some instances where SP2 is approved for
installation to an XP SP1 system, but not all post-SP1 updates are approved
for installation. (Contrary to released statements, it now appears that SP2
does not include /all/ post-SP1 updates.) It's generally not an issue for
SP2, except in the case where the client has not yet installed Windows
Installer v3.1 -- which will prevent the detection of /all/ updates.
Otherwise, there appears to be no abnormal behavior in this client. It's
simply not detecting any updates approved for installation, which pretty
much means that, however it happened, there are no updates eligible for
installation on this client at this time. I would suggest scanning the
Updates webpage of the WSUSAdmin console, to see what updates are reported
as "Needed" for this client, and make sure all "Needed" clients are actually
approved for installation for the "ME Laptops" target group.
To get a quick check on any WSUS-related activity at the client, review the
logfile at %windir%\SoftwareDistribution\ReportingEvents.log, which should
include entries for the successful installation of Windows Installer v3.1,
and any other updates detected, downloaded, scheduled for installation,
installed, and the successful restart of the system following that
installation.
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install"
almost
2
weeks ago. I consider to run WindowsUpdate manually, but are afraid I only
postpone the problem. Any suggestions? Here are today's entries in the local
5.8.0.2469, tz: +0200) ===========
C:\Windows\System32\svchost.exe
C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access disabled: No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0 downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day
at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes
(Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required
version
=
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5 categories in
search
2005-08-22 07:12:24 1048 778 Report *********** Report: Initializing
static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version = 5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c
2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
Lawrence Garvin
2005-08-24 03:58:55 UTC
Permalink
If you've enabled client-side targeting and provided the client with a
target name, then the client will only detect/download/install updates
approved for /that/ target group.

However, if you still have the client in the "Unassigned Computers" group on
the WSUS Server, you may also be seeing an 'artificial' problem, because the
client is reporting all of it's event data as a member of the "ME Laptops"
group. If the client isn't actually in that group on the WSUS Server,
methinks the WSUS server will not properly display the status information
for that client.

Also, if that group actually exists on the server, the client should
populate itself into that group, not "Unassigned Computers" My observation
has been that a client will populate itself into "Unassigned Computers" if
the target-group it has configured does not actually exist on the WSUS
Server.

And.. if that target group does not exist, the client will never detect any
eligible updates for the group it thinks it is a member of.
Post by Trond Mahle
Thanks again for your time, I'm impressed of your extensive answer! I'll try
to answer as good as possible, please see below in the text. I feel we may be
able to solve this problem!
Post by Lawrence Garvin
Post by Trond Mahle
Lawrence, thanks for your detailed answer!
You're most welcome.... here are some more details to ponder... :-)
Post by Trond Mahle
(1) This WXP SP2 client is a member of group "ME laptops". ME is an
abbreviation for our company name - Moxy Engineering - see www.moxy.no :-).
Well.. I'm glad it wasn't the Millenium Edition thingy.... shucks, never
thought of it as a company acronym.
Post by Trond Mahle
(2) The following patches are approved for Install on clients in group "ME
- Critical Update for Windows XP (KB886185)
- Security Update for Microsoft Windows (KB898458)
- Security Update for Microsoft Messenger (KB887472)
- Security Update for Windows XP (KB885835)
- Security Update for Windows XP (KB890047)
- Security Update for Windows XP (KB890175)
- Security Update for Windows XP (KB896358)
- Update for Windows XP (KB896358)
Thanks for the list. We'll keep this handy for future reference.
But here's where I'd like to clarify something...
Post by Trond Mahle
(3) The problem occured when the laptop had a harddisk crash and we had to
buy/swap physical disk. After installing WXP SP2 on the new disk, the laptop
showed up again in group "Unassigned computers".
Are you using client-side targeting, or server-side targeting. My assumption
was "client-side" since the WUA is logging target name information. At least
it appears that the client /thinks/ it's using client-side targeting. If
you're using server-side targeting, then the client behaved as expected --
that is, a new system will always appear in "Unassigned computers" until it
is moved (at the server console) into it's assigned group.
I will say we use a combination of client-side and server-side
targeting...
:-) We have enabled the setting "Enable client-side targeting" in Group
Policy Object Editor (Computer Configuration / Administrative Templates /
Windows Components / Windows Update) which put all laptops into WSUS group
"ME laptops". But at the same time we have choosed this option in the WSUS
Console / Options / Computer Options: "Use the Move computers task in Windows
Server Update Services". That's why all computers still appear in "Unassigned
computers" and we move them manually. The reason is that it's an easy way to
identify new computers entering into the system while we still are in a test
mode...
Post by Lawrence Garvin
Post by Trond Mahle
We then deleted the old
entry in group "ME Laptops" and moved this new entry to group "ME
Laptops".
Again, this implies that you're using server-side targeting, and you made
the change at the WSUS console, not by applying a different GPO with the new
target name. That's my assumption at this point.
See explanation above...
Post by Lawrence Garvin
Post by Trond Mahle
A lot of patches were then installed, except the 8 remaining mentioned
above.
Is there any record in the logs that the client ever detected or downloaded
those updates? If so, there would be entries in the ReportingEvents.log
found in
%windir%\SoftwareDistribution\ReportingEvents.log.
No, I don't find any of the 8 KB-numbers searching in this file.
Post by Lawrence Garvin
If there is no record that the WUA ever detected the updates, the question
becomes: Why is the detection failing?
Post by Trond Mahle
Windows Installer 3.1 is not among these, so I think that's OK.
Actually, it's /not/ okay. Windows Installer v3.1 should have been the
/first/ update detected and installed as soon as the new client contacted
the WSUS server, /unless/ you've slipstreamed the Windows Installer v3.1
code into your image, or your image master had been previously patched to
include Windows Installer v3.1 before the image was created.
I find this sentence in the ReportingEvents.log that verify that Windows
Microsoft Windows Installer 3.1"
Post by Lawrence Garvin
Post by Trond Mahle
I have tried to log on the laptop as Administrator, but that didn't help.
All other 11 laptops in the group are OK (updated). Please advise what
to
try
next, I don't know what to try now.
I think the next step is to tell me exactly what date/time this system was
reinstalled, and then post all of the entries in the ReportingEvents.log
file starting at that date/time. Let's find out exactly what the client has
installed, or not installed, and detected or not detected.
The system was re-installed 04.08.2005 (august), and I post the complete
content of ReportingEvents.log since then. I put it below your last question
to avoid disorder...
Post by Lawrence Garvin
As for the updates themselves...
KB898458 does not install on any of my XP SP2 systems. Unless the
Step-by-Step Interactive Training application is installed, the update is
N/A.
I checked my own laptop now, and here KB898458 was installed 16.06.2005 by
WSUS.
Post by Lawrence Garvin
- there are two revisions of this update, Rev 10, released 2/8/05 --
which is what's installed on my XP SP2 systems,
and Rev 50, released 4/12/05 -- which my systems also report as "Not
Needed".
- if Windows Messenger is not installed, this update is N/A.
I checked my own laptop now, and here KB887472 was installed 24.02.2005 by
WUS.
Post by Lawrence Garvin
KB890047 is superceded by KB893086
KB890175 is superceded by KB896358
OK, but I thought WSUS handle that itself?
Post by Lawrence Garvin
and..not listed in your list is KB898461, which is a WSUS-mandatory update,
released 7/26/05, which will also need to be installed prior to anything
else being detected, and may also create dependencies for some other updates
that need to use the code contained in this update.
I checked my own laptop now, and here KB898461 was installed 25.07.2005 by
WSUS (or downloaded? I look at the date of the folder
c:\windows\$NtUninstallKB898461$).
****************************************************************
ReportingEvents.log (GPO: We have scheduled automatic update to 11:00 AM
every day)
****************************************************************
Oops, I got this message when I copied in the file content here and tried to
Your post is too long. Please reduce the amount of text. (Limit = 30000,
Current = 73257)
Did you receive it?
****************************************************************
Post by Lawrence Garvin
Post by Trond Mahle
Regards Trond
----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Trond.. the client is /not/ detecting the updates.
(1) The client is configured in a different client-side group than the
approvals are set for.
In this case, the client is looking for approvals for
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
(Uhh.... question about the name "ME Laptops"... does this mean /your/
laptops as in me, mine, ours, and yours -- or does this mean "ME" as in
Millenium Edition?????. If the latter, then you should know that WSUS does
not support "Millenium Edition", Windows NT, or Windows 9x.)
The good news, though, is that I can see that this particular client is
2005-08-22 07:12:24 1048 778 Report * OS Version =
5.1.2600.2.0.65792
(2) There is a /required/ (pre-requisite) update that is not approved for
installation. This occurs in some instances where SP2 is approved for
installation to an XP SP1 system, but not all post-SP1 updates are approved
for installation. (Contrary to released statements, it now appears
that
SP2
does not include /all/ post-SP1 updates.) It's generally not an issue for
SP2, except in the case where the client has not yet installed Windows
Installer v3.1 -- which will prevent the detection of /all/ updates.
Otherwise, there appears to be no abnormal behavior in this client. It's
simply not detecting any updates approved for installation, which pretty
much means that, however it happened, there are no updates eligible for
installation on this client at this time. I would suggest scanning the
Updates webpage of the WSUSAdmin console, to see what updates are reported
as "Needed" for this client, and make sure all "Needed" clients are actually
approved for installation for the "ME Laptops" target group.
To get a quick check on any WSUS-related activity at the client,
review
the
logfile at %windir%\SoftwareDistribution\ReportingEvents.log, which should
include entries for the successful installation of Windows Installer v3.1,
and any other updates detected, downloaded, scheduled for
installation,
installed, and the successful restart of the system following that
installation.
I've problem with only 1 of several WSUS clients. This client is not
updating, despite that 8 needed patches are approved for "Install"
almost
2
weeks ago. I consider to run WindowsUpdate manually, but are afraid
I
only
postpone the problem. Any suggestions? Here are today's entries in
the
local
5.8.0.2469, tz: +0200) ===========
C:\Windows\System32\svchost.exe
C:\Windows\system32\wuaueng.dll
2005-08-22 07:11:16 1048 c0 Service *************
2005-08-22 07:11:16 1048 c0 Service ** START ** Service: Service startup
2005-08-22 07:11:16 1048 c0 Service *********
2005-08-22 07:11:16 1048 c0 Agent * WU client version 5.8.0.2469
2005-08-22 07:11:16 1048 c0 Agent * SusClientId =
'e4145361-9a60-4a6b-887b-495e15120e7f'
C:\Windows\SoftwareDistribution
2005-08-22 07:11:16 1048 c0 Agent * Access type: No proxy
2005-08-22 07:11:16 1048 c0 Agent * Network state: Connected
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-08-22 07:12:02 1048 c0 Agent *********** Agent: Initializing global
settings cache ***********
2005-08-22 07:12:02 1048 c0 Agent * WSUS server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * WSUS status server: http://moxy-tst
2005-08-22 07:12:02 1048 c0 Agent * Target group: ME Laptops
2005-08-22 07:12:02 1048 c0 Agent * Windows Update access
No
2005-08-22 07:12:04 1048 c0 DnldMgr Download manager restoring 0 downloads
2005-08-22 07:12:04 1048 c0 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-22 07:12:04 1048 c0 AU AU setting next detection timeout to
2005-08-22 05:12:04
2005-08-22 07:12:04 1048 c0 AU # WSUS server: http://moxy-tst
2005-08-22 07:12:04 1048 c0 AU # Detection frequency: 5
2005-08-22 07:12:04 1048 c0 AU # Target group: ME Laptops
2005-08-22 07:12:04 1048 c0 AU # Approval type: Scheduled (Policy)
2005-08-22 07:12:04 1048 c0 AU # Scheduled install day/time: Every day
at
11:00
2005-08-22 07:12:04 1048 c0 AU # Auto-install minor updates: Yes
(Policy)
2005-08-22 07:12:04 1048 c0 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-22 07:12:04 1048 c0 AU #############
2005-08-22 07:12:04 1048 c0 AU ## START ## AU: Search for updates
2005-08-22 07:12:04 1048 c0 AU #########
2005-08-22 07:12:04 1048 c0 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {29850EFC-D38B-4AB5-83FA-AED880DA4720}]
2005-08-22 07:12:04 1048 778 Agent *************
2005-08-22 07:12:04 1048 778 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-08-22 07:12:04 1048 778 Agent *********
2005-08-22 07:12:17 1048 778 Setup *********** Setup: Checking whether
self-update is required ***********
C:\Windows\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\cdm.dll: target version = 5.8.0.2469, required
version
=
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup Update NOT required for
C:\Windows\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-08-22 07:12:17 1048 778 Setup * IsUpdateRequired = No
2005-08-22 07:12:19 1048 778 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-08-22 07:12:19 1048 778 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://moxy-tst/ClientWebService/client.asmx
2005-08-22 07:12:20 1048 778 PT Initializing simple targeting cookie,
clientId = e4145361-9a60-4a6b-887b-495e15120e7f, target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-22 07:12:20 1048 778 PT Server URL =
http://moxy-tst/SimpleAuthWebService/SimpleAuth.asmx
2005-08-22 07:12:24 1048 778 Agent * Found 0 updates and 5
categories
in
search
Initializing
static
reporting data ***********
2005-08-22 07:12:24 1048 778 Report * OS Version =
5.1.2600.2.0.65792
2005-08-22 07:12:24 1048 778 Report * Computer Brand = Compaq
2005-08-22 07:12:24 1048 778 Report * Computer Model = Evo N600c
2005-08-22 07:12:24 1048 778 Report * Bios Revision = 686DF v2.47
2005-08-22 07:12:24 1048 778 Report * Bios Name = EPP runtime BIOS -
Version 1.1
2005-08-22 07:12:24 1048 778 Report * Bios Release Date =
2001-10-13T00:00:00
2005-08-22 07:12:24 1048 778 Report * Locale ID = 1033
2005-08-22 07:12:24 1048 778 Agent *********
2005-08-22 07:12:24 1048 778 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
Trond Mahle
2005-08-23 11:22:02 UTC
Permalink
(Emailing this file to you failed, so I try to post only this again)

************************************************************
ReportingEvents.log (part 1)
************************************************************
{51200BAC-959B-4D65-848E-A484B7907A9F} 2005-08-04
14:41:20+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.
{91EA3FC8-8DFD-4A4D-A472-4CECAD9E86A2} 2005-08-04
14:44:54+0200 1 162 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0 WindowsUpdate Success Content Download Download succeeded.
{CAA072D6-CCBE-4010-BBF8-FD61120B127B} 2005-08-04
14:45:25+0200 1 184 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP 5.1 (KB842773)
{E377564F-1464-4E08-AABA-C34198F4C6E7} 2005-08-04
14:48:12+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{9C9BA0E9-73DB-40AE-950C-D547274B94E3} 2005-08-04
14:50:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.
{BC1BD5AD-0340-4C0B-AD3D-A2116184533B} 2005-08-04
14:51:03+0200 1 162 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0 WindowsUpdate Success Content Download Download succeeded.
{0A1F770F-B076-4308-B96D-784677CF54CF} 2005-08-04
14:51:12+0200 1 162 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0 WindowsUpdate Success Content Download Download succeeded.
{284E4ADD-1748-43CB-8C94-6B77BC81DF55} 2005-08-04
14:51:16+0200 1 162 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0 WindowsUpdate Success Content Download Download succeeded.
{ED9211A0-75EE-4EDB-99A3-671E4A2DF1B9} 2005-08-04
14:51:22+0200 1 162 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0 WindowsUpdate Success Content Download Download succeeded.
{9A3218C8-488F-46DA-9F3A-823D788E842E} 2005-08-04
14:51:28+0200 1 162 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0 WindowsUpdate Success Content Download Download succeeded.
{4EC53112-7F22-4263-AC09-7470E9024BAF} 2005-08-04
14:51:44+0200 1 162 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0 WindowsUpdate Success Content Download Download succeeded.
{EFF52EBC-7000-461F-AD16-6D96A5BA41D4} 2005-08-04
14:51:51+0200 1 162 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0 WindowsUpdate Success Content Download Download succeeded.
{C49542B7-76AF-4F04-AA47-2228A12117FC} 2005-08-04
14:51:55+0200 1 162 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0 WindowsUpdate Success Content Download Download succeeded.
{6E53A72F-464D-4F2F-911C-88C1DF0D796F} 2005-08-04
14:52:01+0200 1 162 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0 WindowsUpdate Success Content Download Download succeeded.
{77A920E5-4EFF-491B-9331-6091995EAA60} 2005-08-04
14:52:06+0200 1 162 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0 WindowsUpdate Success Content Download Download succeeded.
{4C261E65-76CC-4899-BA08-2E5DA2231317} 2005-08-04
14:53:04+0200 1 162 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0 WindowsUpdate Success Content Download Download succeeded.
{CC8F48D2-7E55-4B10-883A-6353B70EE84A} 2005-08-04
14:53:07+0200 1 162 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0 WindowsUpdate Success Content Download Download succeeded.
{7DB803A1-282C-4240-BE9F-34C344682409} 2005-08-04
14:53:43+0200 1 162 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0 WindowsUpdate Success Content Download Download succeeded.
{65F4D51C-DCA4-460E-AC23-EA7419C36D7D} 2005-08-04
14:54:20+0200 1 162 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0 WindowsUpdate Success Content Download Download succeeded.
{9A5724CF-FDDF-4DDB-990B-3975F6ED84D0} 2005-08-04
14:54:25+0200 1 162 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0 WindowsUpdate Success Content Download Download succeeded.
{00BA3052-938D-4D02-9D8E-D3D0EC91F45F} 2005-08-04
14:54:55+0200 1 162 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0 WindowsUpdate Success Content Download Download succeeded.
{25B67F37-9CAF-4786-BF4D-1F731DFC7F4C} 2005-08-04
14:54:59+0200 1 162 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0 WindowsUpdate Success Content Download Download succeeded.
{CB35FCF6-D70F-4BC4-B35C-E0B18F1398BD} 2005-08-04
14:55:06+0200 1 162 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0 WindowsUpdate Success Content Download Download succeeded.
{F383854F-9B53-4F56-A523-A4A90FE6FB82} 2005-08-04
14:55:27+0200 1 184 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Q329048: Security Update
{750C65CB-A8E2-49B1-BE3E-72A3CF1DF79E} 2005-08-04
14:55:37+0200 1 183 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Q323255: Security Update (Windows XP)
{36C11980-D0CD-4265-A2E0-071D7863A9A3} 2005-08-04
14:55:46+0200 1 183 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Q329390: Security Update
{A4AE3694-2575-4CA0-8BD4-9693524B85C2} 2005-08-04
14:55:53+0200 1 183 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Q329115: Security Update (Windows XP)
{0F673CE2-F7C5-446E-959F-D6EF9AFEEF5D} 2005-08-04
14:57:09+0200 1 184 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 329170: Security Update
{85CC6E9C-93CB-4210-A9CF-B5AA650A6561} 2005-08-04
14:58:10+0200 1 183 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: 811630: Critical Update (Windows XP)
{DBBDDA61-4C57-4CED-9E64-BBD9C90AE141} 2005-08-04
14:59:22+0200 1 184 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 810577: Security Update
{ED2EA0B9-F00B-4F72-BBFB-8F488A7D9EAD} 2005-08-04
15:00:27+0200 1 183 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Q329441: Critical Update
{0489C1FD-3174-454A-82BE-99DE9C10284F} 2005-08-04
15:01:35+0200 1 184 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 817606: Security Update (Windows XP)
{179CD1C9-0538-401B-B9D7-3C0CD3A34630} 2005-08-04
15:02:36+0200 1 183 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: 823559: Security Update for Microsoft Windows
{DD8BCB23-E493-44F1-9F85-DE3F6B03156E} 2005-08-04
15:02:55+0200 1 184 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 816093: Security Update Microsoft Virtual Machine (Microsoft VM)
{9EF16527-F5F4-4884-B82C-5518BA2A3E15} 2005-08-04
15:03:05+0200 1 183 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Security Update for Windows XP (329834)
{E63D55A4-54CE-4A30-AB7C-7F645FD6AF0F} 2005-08-04
15:03:30+0200 1 184 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB828741)
{50448B87-4A5E-4D94-BAC4-E6E8102D2E6C} 2005-08-04
15:03:51+0200 1 184 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Cumulative Security Update for Internet Explorer 6 (KB834707)
{F6C3ACF4-84BD-45F7-8BA3-3ED7C1963B4D} 2005-08-04
15:05:02+0200 1 183 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: 810833: Security Update (Windows XP)
{D4C06C02-CF68-4678-9010-542B12908CB5} 2005-08-04
15:05:23+0200 1 184 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB835732)
{D25C8BDA-577B-45D0-9232-AA30B1927F6A} 2005-08-04
15:05:36+0200 1 183 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Critical Update for Windows (KB833407)
{6EDE3346-731F-4DAC-BDB8-50F241990A1E} 2005-08-04
15:05:46+0200 1 183 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Windows Malicious Software Removal Tool - July 2005 (KB890830)
{C0D63CA6-13F1-4EAC-904C-D4B5E871FCED} 2005-08-04
15:08:04+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{5F0306E6-34E9-45AE-991E-7788E63A6C4B} 2005-08-04
15:11:43+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.
{489AC236-F289-47FC-944F-19715A4160C5} 2005-08-04
15:39:59+0200 1 162 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0 WindowsUpdate Success Content Download Download succeeded.
{C0915366-D759-4B56-8D44-D15C4FCF504D} 2005-08-04
16:00:18+0200 1 184 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Windows XP Service Pack 2
{E0285061-6C8D-4AA1-B1CF-152147BD9404} 2005-08-04
16:17:14+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{C86DD579-251B-4D49-B7DC-D09184063549} 2005-08-04
16:20:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.
{29D43466-BA1D-411E-BEDE-EEFCAA28FA42} 2005-08-04
16:25:51+0200 1 162 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0 WindowsUpdate Success Content Download Download succeeded.
{FC0B4FFA-FB4A-4346-9391-7904F4964603} 2005-08-04
16:27:45+0200 1 162 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0 WindowsUpdate Success Content Download Download succeeded.
{691C1BD1-2DE8-4E63-86E8-23F818454B96} 2005-08-04
16:29:09+0200 1 162 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0 WindowsUpdate Success Content Download Download succeeded.
{25385FCB-400E-4D8B-BADA-E59CF7EABBDC} 2005-08-04
16:29:46+0200 1 184 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Microsoft Windows Installer 3.1
{027EAAFC-0706-4618-902B-CCD91789FC98} 2005-08-04
16:30:04+0200 1 183 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Windows Genuine Advantage Validation Tool (KB892130)
{53475F43-7B4F-4D22-B57B-3719D017B59D} 2005-08-04
16:30:10+0200 1 183 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0 WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the following
update: Update for Windows XP (KB898461)
{7F9DC850-B1C9-497D-8966-4FFAC1EB0CA8} 2005-08-04
16:31:56+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{05CDBB95-37BB-4FDC-BB04-54BC4A31FA2E} 2005-08-04
16:35:20+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{F950C9CB-76E6-4928-8DE0-CBF9677D19D0} 2005-08-04
17:21:28+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{E103CFC8-08CC-4DE2-803A-0E8AC66ED5D4} 2005-08-04
18:24:42+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{47CEF528-8305-49CA-B849-D65C597667CD} 2005-08-04
18:57:36+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80072ee2
{A1D456A5-A604-48D9-8D3B-89632960BE5E} 2005-08-05
07:39:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{054C4E26-2D35-4113-9331-25DC82D66862} 2005-08-05
07:39:13+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{AD313DAD-4FE2-4064-BEF5-076A20F010A8} 2005-08-05
12:00:57+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{004B15C8-BB84-4480-9229-5283096DBD39} 2005-08-05
12:00:57+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{A8A4B7D0-C223-4BAD-9B9E-4A1826E0572C} 2005-08-05
19:51:16+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{343BBA62-333C-4B98-8E10-BD2016167CF1} 2005-08-05
19:57:10+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{5A2E8BA3-DEF1-417A-9D89-70B1DD7E1AE1} 2005-08-05
19:57:10+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{CC77E0A8-D265-49E5-BF6D-434CDC8E7CED} 2005-08-06
09:45:35+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{0B982378-1381-455F-8C50-F98F12D47A1E} 2005-08-06
09:45:36+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{D51F85E7-1AE0-4E35-8D89-3F1D190EA6E3} 2005-08-08
07:37:31+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{7E997C4E-A9B2-41C0-B275-3C4D45E67F76} 2005-08-08
07:37:31+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{CBE9274F-B15C-4639-8503-4F47C7686D64} 2005-08-08
11:40:43+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{E12AF096-91D3-4B0E-8209-A830AC497C64} 2005-08-08
11:40:43+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{8DD75C4E-A51A-464A-8CF1-00697EF269E3} 2005-08-09
07:14:44+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{10D580FB-01C6-4109-92DF-03D4C0C6FAB8} 2005-08-09
07:14:44+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{3CB64392-9AD5-4465-A8F8-D96D5AD7E515} 2005-08-09
12:07:14+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{E4CBA4BA-3268-45E6-8E2D-3622C36308BB} 2005-08-09
12:07:14+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{48C938B8-6066-41F7-8D9A-20B1FD967F2F} 2005-08-10
07:04:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{884ABF1B-9558-4256-8BFE-A13032AF22A8} 2005-08-10
07:04:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{92F9BB46-E0B9-4552-8930-1EDF34E2DF1F} 2005-08-10
11:30:21+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{A4AC35FA-3738-4196-90C8-C80D67117A3E} 2005-08-10
11:30:21+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{63B3CEE5-DE74-47A6-B4E7-6E4721787E90} 2005-08-10
13:27:39+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{9E540D11-8BB7-46DE-9E98-E431AFAB7BE4} 2005-08-10
15:39:50+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{6399BE03-ACBE-48CF-8357-2B51ED490F59} 2005-08-10
15:39:50+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{3AD800CB-24F0-4FDA-AAD6-BE2D6432C42E} 2005-08-10
15:41:06+0200 1 162 101 {A2D28A3A-34AD-4044-A890-3231305FCF5F} 50 0 AutomaticUpdates Success Content Download Download succeeded.
{6D8F2409-625A-43F6-82F4-46F7F0561B05} 2005-08-10
15:41:06+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Cumulative Security
Update for Internet Explorer for Windows XP Service Pack 2 (KB890923)
{D1FD5600-78AC-41D6-96F3-07B11A5A6218} 2005-08-10
20:55:44+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Cumulative Security
Update for Internet Explorer for Windows XP Service Pack 2 (KB890923)
{8233FF7A-D4A7-4B3F-A946-70C4EC3E4F44} 2005-08-11
07:53:11+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Cumulative Security
Update for Internet Explorer for Windows XP Service Pack 2 (KB890923)
{478D7D24-046A-4115-9BE6-33FFF5D22B42} 2005-08-11
07:53:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{669DE37F-3144-4EA3-8470-D9BEE7A86413} 2005-08-11
07:53:27+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{00366F28-DFD4-40AC-A21C-7A18B3636241} 2005-08-11
07:53:59+0200 1 162 101 {5BC6E116-9964-4452-AE5A-C54BD709BC53} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{7534E84F-5FD8-4485-A50E-2C054FF8D6F3} 2005-08-11
07:53:59+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923)
{E93A5548-105C-4EEE-AA8E-C87865D8384D} 2005-08-11
07:54:40+0200 1 162 101 {9A127D52-45FA-44BA-ACC5-5EA9A637FE4E} 10 0 AutomaticUpdates Success Content Download Download succeeded.
{D6911C21-6EBC-4C0E-96E8-2847D1C1396D} 2005-08-11
07:54:40+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302)
{E4F5CAA9-1B2D-4043-AB16-C5AA22EDECDA} 2005-08-11
07:54:45+0200 1 162 101 {1E59F963-12F5-4BFD-A73D-366921779C28} 102 0 AutomaticUpdates Success Content Download Download succeeded.
{B7AB076D-EAF4-499B-921E-A44F77DB4C5E} 2005-08-11
07:54:45+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214)
{A4B5E0F2-FAC9-459C-8A05-5E895CCDD415} 2005-08-11
07:54:55+0200 1 162 101 {4324AC78-FDB4-42DE-BEDF-769A40627897} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{6AA50A48-ECE4-449A-AEF4-6EF16A1A7666} 2005-08-11
07:54:55+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066)
{CD619455-0F26-4AB5-AEA4-F359E15FF068} 2005-08-11
07:55:06+0200 1 162 101 {4CDB577B-FDD1-49D4-87CC-3808AD20ACBC} 101 0 AutomaticUpdates Success Content Download Download succeeded.
{875C9D3A-634D-47DB-9210-C87185122D24} 2005-08-11
07:55:06+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046)
{4A3BC1C7-C17D-4127-95C5-196A49925AD8} 2005-08-11
07:55:15+0200 1 162 101 {4B689082-CA9C-46CC-B2FC-720FEDE21299} 10 0 AutomaticUpdates Success Content Download Download succeeded.
{5723B74F-C1A8-4181-8BEA-5AF6B714D19C} 2005-08-11
07:55:15+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781)
{22B14601-E576-4A28-9487-C327AEF91041} 2005-08-11
07:55:18+0200 1 162 101 {3A7EFDB0-D88D-42A6-8439-C7D0B1BCAC82} 10 0 AutomaticUpdates Success Content Download Download succeeded.
{22871435-698D-4DA2-8D67-C760C665AC1F} 2005-08-11
07:55:18+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
{DCCDE213-C03F-4AA7-B3AC-56DDC6B614D5} 2005-08-11
07:55:23+0200 1 162 101 {E45B26C2-278F-48F3-97D1-AA0FD57423D5} 10 0 AutomaticUpdates Success Content Download Download succeeded.
{BDA5441A-2B24-4075-90A5-822A77EB13CB} 2005-08-11
07:55:23+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339)
{CB0DB710-1C4B-4027-B7A0-EFFB76192476} 2005-08-11
07:55:34+0200 1 162 101 {B20C7AC9-F972-480C-9601-DE0486342506} 11 0 AutomaticUpdates Success Content Download Download succeeded.
{B2B66B94-B00D-4130-BEF7-0EEDAB596CCB} 2005-08-11
07:55:34+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250)
{10CDCF0F-091F-4A0D-A39C-3D002DF8128C} 2005-08-11
07:55:38+0200 1 162 101 {BBE805EE-2CF7-4110-9BE8-4FE32B144E5A} 10 0 AutomaticUpdates Success Content Download Download succeeded.
{48573FAA-2289-4594-A230-DD16380F5DC6} 2005-08-11
07:55:38+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836)
Lawrence Garvin
2005-08-24 04:12:21 UTC
Permalink
Prior to 8/11, it appears that ALL updates applied to this system were
obtained via Windows Update. On the morning of 8/11, Automatic Updates
downloaded these updates, and scheduled them for installation at 11:00am

2005-08-11 07:55:38+0200
AutomaticUpdates Success Content Install Installation Ready:
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836) - Security Update for
Windows XP (KB896422)

The installation was successful, and the system restarted.

Then, on the morning of 8/12, these updates were detected and downloaded and
scheduled for installation on 8/12 at 11am.

2005-08-12 07:54:25+0200
AutomaticUpdates Success Content Install Installation Ready:
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for Windows XP
(KB899591) - Security Update for Windows XP (KB899587)

The installation was successful, and the system restarted.

No other updates were ever detected for installation, although the
detections continued to run twice daily.

A question to be asked, for sure, is what was the configuration of the
system on 8/11 and 8/12.

I suspect it has to do with how you're configuring and using target groups.

Part of this may be answered by the WindowsUpdate.log, so now I'm going to
ask you to email me the WindowsUpdate.log for 8/11 and 8/12.

Please remove the "nospam" subdomain prefix from my email address to get
it to me.
Post by Trond Mahle
(Emailing this file to you failed, so I try to post only this again)
************************************************************
ReportingEvents.log (part 1)
************************************************************
{51200BAC-959B-4D65-848E-A484B7907A9F} 2005-08-04
14:41:20+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{91EA3FC8-8DFD-4A4D-A472-4CECAD9E86A2} 2005-08-04
14:44:54+0200 1 162 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CAA072D6-CCBE-4010-BBF8-FD61120B127B} 2005-08-04
14:45:25+0200 1 184 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP 5.1 (KB842773)
{E377564F-1464-4E08-AABA-C34198F4C6E7} 2005-08-04
14:48:12+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{9C9BA0E9-73DB-40AE-950C-D547274B94E3} 2005-08-04
14:50:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{BC1BD5AD-0340-4C0B-AD3D-A2116184533B} 2005-08-04
14:51:03+0200 1 162 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content Download Download succeeded.
{0A1F770F-B076-4308-B96D-784677CF54CF} 2005-08-04
14:51:12+0200 1 162 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content Download Download succeeded.
{284E4ADD-1748-43CB-8C94-6B77BC81DF55} 2005-08-04
14:51:16+0200 1 162 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content Download Download succeeded.
{ED9211A0-75EE-4EDB-99A3-671E4A2DF1B9} 2005-08-04
14:51:22+0200 1 162 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content Download Download succeeded.
{9A3218C8-488F-46DA-9F3A-823D788E842E} 2005-08-04
14:51:28+0200 1 162 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4EC53112-7F22-4263-AC09-7470E9024BAF} 2005-08-04
14:51:44+0200 1 162 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content Download Download succeeded.
{EFF52EBC-7000-461F-AD16-6D96A5BA41D4} 2005-08-04
14:51:51+0200 1 162 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content Download Download succeeded.
{C49542B7-76AF-4F04-AA47-2228A12117FC} 2005-08-04
14:51:55+0200 1 162 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content Download Download succeeded.
{6E53A72F-464D-4F2F-911C-88C1DF0D796F} 2005-08-04
14:52:01+0200 1 162 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content Download Download succeeded.
{77A920E5-4EFF-491B-9331-6091995EAA60} 2005-08-04
14:52:06+0200 1 162 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4C261E65-76CC-4899-BA08-2E5DA2231317} 2005-08-04
14:53:04+0200 1 162 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CC8F48D2-7E55-4B10-883A-6353B70EE84A} 2005-08-04
14:53:07+0200 1 162 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content Download Download succeeded.
{7DB803A1-282C-4240-BE9F-34C344682409} 2005-08-04
14:53:43+0200 1 162 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content Download Download succeeded.
{65F4D51C-DCA4-460E-AC23-EA7419C36D7D} 2005-08-04
14:54:20+0200 1 162 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content Download Download succeeded.
{9A5724CF-FDDF-4DDB-990B-3975F6ED84D0} 2005-08-04
14:54:25+0200 1 162 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content Download Download succeeded.
{00BA3052-938D-4D02-9D8E-D3D0EC91F45F} 2005-08-04
14:54:55+0200 1 162 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content Download Download succeeded.
{25B67F37-9CAF-4786-BF4D-1F731DFC7F4C} 2005-08-04
14:54:59+0200 1 162 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CB35FCF6-D70F-4BC4-B35C-E0B18F1398BD} 2005-08-04
14:55:06+0200 1 162 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content Download Download succeeded.
{F383854F-9B53-4F56-A523-A4A90FE6FB82} 2005-08-04
14:55:27+0200 1 184 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Q329048: Security Update
{750C65CB-A8E2-49B1-BE3E-72A3CF1DF79E} 2005-08-04
14:55:37+0200 1 183 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q323255: Security Update (Windows XP)
{36C11980-D0CD-4265-A2E0-071D7863A9A3} 2005-08-04
14:55:46+0200 1 183 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329390: Security Update
{A4AE3694-2575-4CA0-8BD4-9693524B85C2} 2005-08-04
14:55:53+0200 1 183 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329115: Security Update (Windows XP)
{0F673CE2-F7C5-446E-959F-D6EF9AFEEF5D} 2005-08-04
14:57:09+0200 1 184 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 329170: Security Update
{85CC6E9C-93CB-4210-A9CF-B5AA650A6561} 2005-08-04
14:58:10+0200 1 183 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 811630: Critical Update (Windows XP)
{DBBDDA61-4C57-4CED-9E64-BBD9C90AE141} 2005-08-04
14:59:22+0200 1 184 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 810577: Security Update
{ED2EA0B9-F00B-4F72-BBFB-8F488A7D9EAD} 2005-08-04
15:00:27+0200 1 183 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329441: Critical Update
{0489C1FD-3174-454A-82BE-99DE9C10284F} 2005-08-04
15:01:35+0200 1 184 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 817606: Security Update (Windows XP)
{179CD1C9-0538-401B-B9D7-3C0CD3A34630} 2005-08-04
15:02:36+0200 1 183 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 823559: Security Update for Microsoft Windows
{DD8BCB23-E493-44F1-9F85-DE3F6B03156E} 2005-08-04
15:02:55+0200 1 184 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 816093: Security Update Microsoft Virtual Machine (Microsoft VM)
{9EF16527-F5F4-4884-B82C-5518BA2A3E15} 2005-08-04
15:03:05+0200 1 183 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Security Update for Windows XP (329834)
{E63D55A4-54CE-4A30-AB7C-7F645FD6AF0F} 2005-08-04
15:03:30+0200 1 184 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB828741)
{50448B87-4A5E-4D94-BAC4-E6E8102D2E6C} 2005-08-04
15:03:51+0200 1 184 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Cumulative Security Update for Internet Explorer 6 (KB834707)
{F6C3ACF4-84BD-45F7-8BA3-3ED7C1963B4D} 2005-08-04
15:05:02+0200 1 183 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 810833: Security Update (Windows XP)
{D4C06C02-CF68-4678-9010-542B12908CB5} 2005-08-04
15:05:23+0200 1 184 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB835732)
{D25C8BDA-577B-45D0-9232-AA30B1927F6A} 2005-08-04
15:05:36+0200 1 183 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Critical Update for Windows (KB833407)
{6EDE3346-731F-4DAC-BDB8-50F241990A1E} 2005-08-04
15:05:46+0200 1 183 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Windows Malicious Software Removal Tool - July 2005 (KB890830)
{C0D63CA6-13F1-4EAC-904C-D4B5E871FCED} 2005-08-04
15:08:04+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{5F0306E6-34E9-45AE-991E-7788E63A6C4B} 2005-08-04
15:11:43+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{489AC236-F289-47FC-944F-19715A4160C5} 2005-08-04
15:39:59+0200 1 162 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0
WindowsUpdate Success Content Download Download succeeded.
{C0915366-D759-4B56-8D44-D15C4FCF504D} 2005-08-04
16:00:18+0200 1 184 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Windows XP Service Pack 2
{E0285061-6C8D-4AA1-B1CF-152147BD9404} 2005-08-04
16:17:14+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{C86DD579-251B-4D49-B7DC-D09184063549} 2005-08-04
16:20:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{29D43466-BA1D-411E-BEDE-EEFCAA28FA42} 2005-08-04
16:25:51+0200 1 162 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0
WindowsUpdate Success Content Download Download succeeded.
{FC0B4FFA-FB4A-4346-9391-7904F4964603} 2005-08-04
16:27:45+0200 1 162 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0
WindowsUpdate Success Content Download Download succeeded.
{691C1BD1-2DE8-4E63-86E8-23F818454B96} 2005-08-04
16:29:09+0200 1 162 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0
WindowsUpdate Success Content Download Download succeeded.
{25385FCB-400E-4D8B-BADA-E59CF7EABBDC} 2005-08-04
16:29:46+0200 1 184 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Microsoft Windows Installer 3.1
{027EAAFC-0706-4618-902B-CCD91789FC98} 2005-08-04
16:30:04+0200 1 183 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Windows Genuine Advantage Validation Tool (KB892130)
{53475F43-7B4F-4D22-B57B-3719D017B59D} 2005-08-04
16:30:10+0200 1 183 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Update for Windows XP (KB898461)
{7F9DC850-B1C9-497D-8966-4FFAC1EB0CA8} 2005-08-04
16:31:56+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{05CDBB95-37BB-4FDC-BB04-54BC4A31FA2E} 2005-08-04
16:35:20+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{F950C9CB-76E6-4928-8DE0-CBF9677D19D0} 2005-08-04
17:21:28+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{E103CFC8-08CC-4DE2-803A-0E8AC66ED5D4} 2005-08-04
18:24:42+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{47CEF528-8305-49CA-B849-D65C597667CD} 2005-08-04
18:57:36+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2
AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80072ee2
{A1D456A5-A604-48D9-8D3B-89632960BE5E} 2005-08-05
07:39:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{054C4E26-2D35-4113-9331-25DC82D66862} 2005-08-05
07:39:13+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{AD313DAD-4FE2-4064-BEF5-076A20F010A8} 2005-08-05
12:00:57+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{004B15C8-BB84-4480-9229-5283096DBD39} 2005-08-05
12:00:57+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{A8A4B7D0-C223-4BAD-9B9E-4A1826E0572C} 2005-08-05
19:51:16+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{343BBA62-333C-4B98-8E10-BD2016167CF1} 2005-08-05
19:57:10+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{5A2E8BA3-DEF1-417A-9D89-70B1DD7E1AE1} 2005-08-05
19:57:10+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{CC77E0A8-D265-49E5-BF6D-434CDC8E7CED} 2005-08-06
09:45:35+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{0B982378-1381-455F-8C50-F98F12D47A1E} 2005-08-06
09:45:36+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{D51F85E7-1AE0-4E35-8D89-3F1D190EA6E3} 2005-08-08
07:37:31+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{7E997C4E-A9B2-41C0-B275-3C4D45E67F76} 2005-08-08
07:37:31+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{CBE9274F-B15C-4639-8503-4F47C7686D64} 2005-08-08
11:40:43+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{E12AF096-91D3-4B0E-8209-A830AC497C64} 2005-08-08
11:40:43+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{8DD75C4E-A51A-464A-8CF1-00697EF269E3} 2005-08-09
07:14:44+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{10D580FB-01C6-4109-92DF-03D4C0C6FAB8} 2005-08-09
07:14:44+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{3CB64392-9AD5-4465-A8F8-D96D5AD7E515} 2005-08-09
12:07:14+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{E4CBA4BA-3268-45E6-8E2D-3622C36308BB} 2005-08-09
12:07:14+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{48C938B8-6066-41F7-8D9A-20B1FD967F2F} 2005-08-10
07:04:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{884ABF1B-9558-4256-8BFE-A13032AF22A8} 2005-08-10
07:04:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{92F9BB46-E0B9-4552-8930-1EDF34E2DF1F} 2005-08-10
11:30:21+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{A4AC35FA-3738-4196-90C8-C80D67117A3E} 2005-08-10
11:30:21+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{63B3CEE5-DE74-47A6-B4E7-6E4721787E90} 2005-08-10
13:27:39+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{9E540D11-8BB7-46DE-9E98-E431AFAB7BE4} 2005-08-10
15:39:50+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{6399BE03-ACBE-48CF-8357-2B51ED490F59} 2005-08-10
15:39:50+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{3AD800CB-24F0-4FDA-AAD6-BE2D6432C42E} 2005-08-10
15:41:06+0200 1 162 101 {A2D28A3A-34AD-4044-A890-3231305FCF5F} 50 0
AutomaticUpdates Success Content Download Download succeeded.
{6D8F2409-625A-43F6-82F4-46F7F0561B05} 2005-08-10
15:41:06+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Cumulative Security
Update for Internet Explorer for Windows XP Service Pack 2 (KB890923)
{D1FD5600-78AC-41D6-96F3-07B11A5A6218} 2005-08-10
20:55:44+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Cumulative Security
Update for Internet Explorer for Windows XP Service Pack 2 (KB890923)
{8233FF7A-D4A7-4B3F-A946-70C4EC3E4F44} 2005-08-11
07:53:11+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Cumulative Security
Update for Internet Explorer for Windows XP Service Pack 2 (KB890923)
{478D7D24-046A-4115-9BE6-33FFF5D22B42} 2005-08-11
07:53:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
detecting items.
{669DE37F-3144-4EA3-8470-D9BEE7A86413} 2005-08-11
07:53:27+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{00366F28-DFD4-40AC-A21C-7A18B3636241} 2005-08-11
07:53:59+0200 1 162 101 {5BC6E116-9964-4452-AE5A-C54BD709BC53} 100 0
AutomaticUpdates Success Content Download Download succeeded.
{7534E84F-5FD8-4485-A50E-2C054FF8D6F3} 2005-08-11
07:53:59+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923)
{E93A5548-105C-4EEE-AA8E-C87865D8384D} 2005-08-11
07:54:40+0200 1 162 101 {9A127D52-45FA-44BA-ACC5-5EA9A637FE4E} 10 0
AutomaticUpdates Success Content Download Download succeeded.
{D6911C21-6EBC-4C0E-96E8-2847D1C1396D} 2005-08-11
07:54:40+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302)
{E4F5CAA9-1B2D-4043-AB16-C5AA22EDECDA} 2005-08-11
07:54:45+0200 1 162 101 {1E59F963-12F5-4BFD-A73D-366921779C28} 102 0
AutomaticUpdates Success Content Download Download succeeded.
{B7AB076D-EAF4-499B-921E-A44F77DB4C5E} 2005-08-11
07:54:45+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214)
{A4B5E0F2-FAC9-459C-8A05-5E895CCDD415} 2005-08-11
07:54:55+0200 1 162 101 {4324AC78-FDB4-42DE-BEDF-769A40627897} 100 0
AutomaticUpdates Success Content Download Download succeeded.
{6AA50A48-ECE4-449A-AEF4-6EF16A1A7666} 2005-08-11
07:54:55+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066)
{CD619455-0F26-4AB5-AEA4-F359E15FF068} 2005-08-11
07:55:06+0200 1 162 101 {4CDB577B-FDD1-49D4-87CC-3808AD20ACBC} 101 0
AutomaticUpdates Success Content Download Download succeeded.
{875C9D3A-634D-47DB-9210-C87185122D24} 2005-08-11
07:55:06+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046)
{4A3BC1C7-C17D-4127-95C5-196A49925AD8} 2005-08-11
07:55:15+0200 1 162 101 {4B689082-CA9C-46CC-B2FC-720FEDE21299} 10 0
AutomaticUpdates Success Content Download Download succeeded.
{5723B74F-C1A8-4181-8BEA-5AF6B714D19C} 2005-08-11
07:55:15+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781)
{22B14601-E576-4A28-9487-C327AEF91041} 2005-08-11
07:55:18+0200 1 162 101 {3A7EFDB0-D88D-42A6-8439-C7D0B1BCAC82} 10 0
AutomaticUpdates Success Content Download Download succeeded.
{22871435-698D-4DA2-8D67-C760C665AC1F} 2005-08-11
07:55:18+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
{DCCDE213-C03F-4AA7-B3AC-56DDC6B614D5} 2005-08-11
07:55:23+0200 1 162 101 {E45B26C2-278F-48F3-97D1-AA0FD57423D5} 10 0
AutomaticUpdates Success Content Download Download succeeded.
{BDA5441A-2B24-4075-90A5-822A77EB13CB} 2005-08-11
07:55:23+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339)
{CB0DB710-1C4B-4027-B7A0-EFFB76192476} 2005-08-11
07:55:34+0200 1 162 101 {B20C7AC9-F972-480C-9601-DE0486342506} 11 0
AutomaticUpdates Success Content Download Download succeeded.
{B2B66B94-B00D-4130-BEF7-0EEDAB596CCB} 2005-08-11
07:55:34+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250)
{10CDCF0F-091F-4A0D-A39C-3D002DF8128C} 2005-08-11
07:55:38+0200 1 162 101 {BBE805EE-2CF7-4110-9BE8-4FE32B144E5A} 10 0
AutomaticUpdates Success Content Download Download succeeded.
{48573FAA-2289-4594-A230-DD16380F5DC6} 2005-08-11
07:55:38+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836)
Trond Mahle
2005-08-24 07:21:01 UTC
Permalink
Thanks, but I'm not sure if I totally agree with your conclusion. The way we
use target groups has definitive worked the last 1/2 year for all other WSUS
clients in our network (servers, desktops, laptops). It's configured "after
the book" in our GPO Editor, the only difference is that we move the clients
manually from "Unassigned Computers" to their appropriate group in WSUS Admin
(with exactly the same group name as used in GPO Editor).

The special in this case was that the laptop already existed in our WSUS
group "ME Laptops" when it got a new blank harddisk which was configured like
this 04.08.2005 by my colleague (I was on holiday):
1. WXP installed from recovery CD following the laptop.
2. Connected direct to a brodband line logged in as local Administrator and
manually patched from windowsupdate.microsoft.com until WXP SP2 had been
installed (no more updates afterwards).
3. Connected to our LAN/domain to complete the rest of the WXP
configuration, installing applications etc.

When I came back from holiday 08.08.2005 I found the laptop both in the WSUS
group "Unassigned Computers" (new entry with a long list of updates
"Needed"), and in our WSUS group "ME Laptops" (old entry with an exclamation
mark in front of it indicating no contact last week).
4. I then deleted the old entry end moved the new entry into our WSUS group
"ME Laptops" where all needed updates for laptops with WXP SP1/SP2 have been
approved since we started with WUS in february 2005. I'm not sure exactly
what day I moved it, but it must have been between 8th-10th of August.
5. All updates except for the 8 remaining were then installed on the laptop
during the next days (11th-12th ?).
6. Almost at the same time, 10th of August 09:54 AM CEST, I successfully
synchronized the server with Microsoft because they had relased new August
patches. Afterwards all new August WXP SP2 updates were approved for WSUS
group "ME Laptops".

I now email you 3 files:
- Screendump of WSUS Admin showing the problem.
- Complete WindowsUpdate.log from the client.
- Complete ReportingEvents.log from the client.

Hope we come to a conclusion soon! :-))

Best regards Tron
-----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Prior to 8/11, it appears that ALL updates applied to this system were
obtained via Windows Update. On the morning of 8/11, Automatic Updates
downloaded these updates, and scheduled them for installation at 11:00am
2005-08-11 07:55:38+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836) - Security Update for
Windows XP (KB896422)
The installation was successful, and the system restarted.
Then, on the morning of 8/12, these updates were detected and downloaded and
scheduled for installation on 8/12 at 11am.
2005-08-12 07:54:25+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for Windows XP
(KB899591) - Security Update for Windows XP (KB899587)
The installation was successful, and the system restarted.
No other updates were ever detected for installation, although the
detections continued to run twice daily.
A question to be asked, for sure, is what was the configuration of the
system on 8/11 and 8/12.
I suspect it has to do with how you're configuring and using target groups.
Part of this may be answered by the WindowsUpdate.log, so now I'm going to
ask you to email me the WindowsUpdate.log for 8/11 and 8/12.
Please remove the "nospam" subdomain prefix from my email address to get
it to me.
Post by Trond Mahle
(Emailing this file to you failed, so I try to post only this again)
************************************************************
ReportingEvents.log (part 1)
************************************************************
{51200BAC-959B-4D65-848E-A484B7907A9F} 2005-08-04
14:41:20+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{91EA3FC8-8DFD-4A4D-A472-4CECAD9E86A2} 2005-08-04
14:44:54+0200 1 162 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CAA072D6-CCBE-4010-BBF8-FD61120B127B} 2005-08-04
14:45:25+0200 1 184 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP 5.1 (KB842773)
{E377564F-1464-4E08-AABA-C34198F4C6E7} 2005-08-04
14:48:12+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{9C9BA0E9-73DB-40AE-950C-D547274B94E3} 2005-08-04
14:50:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{BC1BD5AD-0340-4C0B-AD3D-A2116184533B} 2005-08-04
14:51:03+0200 1 162 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content Download Download succeeded.
{0A1F770F-B076-4308-B96D-784677CF54CF} 2005-08-04
14:51:12+0200 1 162 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content Download Download succeeded.
{284E4ADD-1748-43CB-8C94-6B77BC81DF55} 2005-08-04
14:51:16+0200 1 162 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content Download Download succeeded.
{ED9211A0-75EE-4EDB-99A3-671E4A2DF1B9} 2005-08-04
14:51:22+0200 1 162 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content Download Download succeeded.
{9A3218C8-488F-46DA-9F3A-823D788E842E} 2005-08-04
14:51:28+0200 1 162 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4EC53112-7F22-4263-AC09-7470E9024BAF} 2005-08-04
14:51:44+0200 1 162 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content Download Download succeeded.
{EFF52EBC-7000-461F-AD16-6D96A5BA41D4} 2005-08-04
14:51:51+0200 1 162 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content Download Download succeeded.
{C49542B7-76AF-4F04-AA47-2228A12117FC} 2005-08-04
14:51:55+0200 1 162 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content Download Download succeeded.
{6E53A72F-464D-4F2F-911C-88C1DF0D796F} 2005-08-04
14:52:01+0200 1 162 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content Download Download succeeded.
{77A920E5-4EFF-491B-9331-6091995EAA60} 2005-08-04
14:52:06+0200 1 162 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4C261E65-76CC-4899-BA08-2E5DA2231317} 2005-08-04
14:53:04+0200 1 162 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CC8F48D2-7E55-4B10-883A-6353B70EE84A} 2005-08-04
14:53:07+0200 1 162 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content Download Download succeeded.
{7DB803A1-282C-4240-BE9F-34C344682409} 2005-08-04
14:53:43+0200 1 162 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content Download Download succeeded.
{65F4D51C-DCA4-460E-AC23-EA7419C36D7D} 2005-08-04
14:54:20+0200 1 162 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content Download Download succeeded.
{9A5724CF-FDDF-4DDB-990B-3975F6ED84D0} 2005-08-04
14:54:25+0200 1 162 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content Download Download succeeded.
{00BA3052-938D-4D02-9D8E-D3D0EC91F45F} 2005-08-04
14:54:55+0200 1 162 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content Download Download succeeded.
{25B67F37-9CAF-4786-BF4D-1F731DFC7F4C} 2005-08-04
14:54:59+0200 1 162 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CB35FCF6-D70F-4BC4-B35C-E0B18F1398BD} 2005-08-04
14:55:06+0200 1 162 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content Download Download succeeded.
{F383854F-9B53-4F56-A523-A4A90FE6FB82} 2005-08-04
14:55:27+0200 1 184 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Q329048: Security Update
{750C65CB-A8E2-49B1-BE3E-72A3CF1DF79E} 2005-08-04
14:55:37+0200 1 183 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q323255: Security Update (Windows XP)
{36C11980-D0CD-4265-A2E0-071D7863A9A3} 2005-08-04
14:55:46+0200 1 183 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329390: Security Update
{A4AE3694-2575-4CA0-8BD4-9693524B85C2} 2005-08-04
14:55:53+0200 1 183 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329115: Security Update (Windows XP)
{0F673CE2-F7C5-446E-959F-D6EF9AFEEF5D} 2005-08-04
14:57:09+0200 1 184 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 329170: Security Update
{85CC6E9C-93CB-4210-A9CF-B5AA650A6561} 2005-08-04
14:58:10+0200 1 183 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 811630: Critical Update (Windows XP)
{DBBDDA61-4C57-4CED-9E64-BBD9C90AE141} 2005-08-04
14:59:22+0200 1 184 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 810577: Security Update
{ED2EA0B9-F00B-4F72-BBFB-8F488A7D9EAD} 2005-08-04
15:00:27+0200 1 183 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329441: Critical Update
{0489C1FD-3174-454A-82BE-99DE9C10284F} 2005-08-04
15:01:35+0200 1 184 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 817606: Security Update (Windows XP)
{179CD1C9-0538-401B-B9D7-3C0CD3A34630} 2005-08-04
15:02:36+0200 1 183 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 823559: Security Update for Microsoft Windows
{DD8BCB23-E493-44F1-9F85-DE3F6B03156E} 2005-08-04
15:02:55+0200 1 184 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 816093: Security Update Microsoft Virtual Machine (Microsoft VM)
{9EF16527-F5F4-4884-B82C-5518BA2A3E15} 2005-08-04
15:03:05+0200 1 183 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Security Update for Windows XP (329834)
{E63D55A4-54CE-4A30-AB7C-7F645FD6AF0F} 2005-08-04
15:03:30+0200 1 184 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB828741)
{50448B87-4A5E-4D94-BAC4-E6E8102D2E6C} 2005-08-04
15:03:51+0200 1 184 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Cumulative Security Update for Internet Explorer 6 (KB834707)
{F6C3ACF4-84BD-45F7-8BA3-3ED7C1963B4D} 2005-08-04
15:05:02+0200 1 183 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 810833: Security Update (Windows XP)
{D4C06C02-CF68-4678-9010-542B12908CB5} 2005-08-04
15:05:23+0200 1 184 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB835732)
{D25C8BDA-577B-45D0-9232-AA30B1927F6A} 2005-08-04
15:05:36+0200 1 183 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Critical Update for Windows (KB833407)
{6EDE3346-731F-4DAC-BDB8-50F241990A1E} 2005-08-04
15:05:46+0200 1 183 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Windows Malicious Software Removal Tool - July 2005 (KB890830)
{C0D63CA6-13F1-4EAC-904C-D4B5E871FCED} 2005-08-04
15:08:04+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{5F0306E6-34E9-45AE-991E-7788E63A6C4B} 2005-08-04
15:11:43+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{489AC236-F289-47FC-944F-19715A4160C5} 2005-08-04
15:39:59+0200 1 162 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0
WindowsUpdate Success Content Download Download succeeded.
{C0915366-D759-4B56-8D44-D15C4FCF504D} 2005-08-04
16:00:18+0200 1 184 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Windows XP Service Pack 2
{E0285061-6C8D-4AA1-B1CF-152147BD9404} 2005-08-04
16:17:14+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{C86DD579-251B-4D49-B7DC-D09184063549} 2005-08-04
16:20:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{29D43466-BA1D-411E-BEDE-EEFCAA28FA42} 2005-08-04
16:25:51+0200 1 162 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0
WindowsUpdate Success Content Download Download succeeded.
{FC0B4FFA-FB4A-4346-9391-7904F4964603} 2005-08-04
16:27:45+0200 1 162 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0
WindowsUpdate Success Content Download Download succeeded.
{691C1BD1-2DE8-4E63-86E8-23F818454B96} 2005-08-04
16:29:09+0200 1 162 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0
WindowsUpdate Success Content Download Download succeeded.
{25385FCB-400E-4D8B-BADA-E59CF7EABBDC} 2005-08-04
16:29:46+0200 1 184 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Microsoft Windows Installer 3.1
{027EAAFC-0706-4618-902B-CCD91789FC98} 2005-08-04
16:30:04+0200 1 183 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Windows Genuine Advantage Validation Tool (KB892130)
{53475F43-7B4F-4D22-B57B-3719D017B59D} 2005-08-04
16:30:10+0200 1 183 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Update for Windows XP (KB898461)
{7F9DC850-B1C9-497D-8966-4FFAC1EB0CA8} 2005-08-04
16:31:56+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{05CDBB95-37BB-4FDC-BB04-54BC4A31FA2E} 2005-08-04
16:35:20+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{F950C9CB-76E6-4928-8DE0-CBF9677D19D0} 2005-08-04
17:21:28+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{E103CFC8-08CC-4DE2-803A-0E8AC66ED5D4} 2005-08-04
18:24:42+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{47CEF528-8305-49CA-B849-D65C597667CD} 2005-08-04
18:57:36+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2
AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80072ee2
{A1D456A5-A604-48D9-8D3B-89632960BE5E} 2005-08-05
07:39:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
Lawrence Garvin
2005-08-26 10:02:15 UTC
Permalink
I received your email and attachements.

I'm letting go of the 'target group' consideration.... the client appears to
have been consistently a member of that group, and your screenshot of the
WSUS server shows those updates as approved for installation for that target
group.

What's problematic with this scenario is that the client has /never/
detected those eight updates, and still isn't detecting them. I suspect
there is corrupted data somewhere -- perhaps the datastore.edb on the
client, perhaps the data in the susdb.mdf on the server, perhaps both, even.

The updates should not be showing as "Needed" on the server because the
client has never detected, and thus never reported 'events' for that
detection. Whether the updates /should/ be detected at this point is really
a secondary issue. The client is not detecting them, and the data, as
reported on the WSUS server, is incorrect.

What I think happened. but I don't exactly understand how, is that
/something/ caused this client's record to be updated with these detections.
Maybe this is fallout from a duplicate SusClientID?

The questions we have at the moment: Are the updates actually installed? Are
they even required -- as noted, /some/ of the updates may, in fact, be N/A.

Here's what I would suggest as a "fix" for the whole situation -- it's a
radical fix, but I believe it will clean house - so to speak.

1. At the client, shutdown Automatic Updates service.

2. At the client, use bitsadmin to check the BITS queue, and flush it if
there's anything there.

3. At the client, make a backup of the %windir%\SoftwareDistribution folder
and all subfolders
and the %windir%\WindowsUpdate.log file.

4. At the client, purge the following folders of all content:
%windir%\SoftwareDistribution\Datastore\Logs\edb*.*
%windir%\SoftwareDistribution\Datastore\DataStore.edb
%windir%\SoftwareDistribution\Download
%windir%\SoftwareDistribution\EventCache
and delete the following files:
%windir%\SoftwareDistribution\ReportingEvents.log
%windir%\WindowsUpdate.log

5. At the client, delete the three values in the registry key at:
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new SusClientId, which
will force the creation of an all new database record (thus avoiding any
potential issues with corruption or bad data in the original record, that
may or may not actually be physically present in the database).

6. At the server, delete pc176.moxy.no from the WSUS server, completely.

7. At the client, restart the Automatic Updates service, and monitor the
WindowsUpdate.log and/or ReportingEvents.log for detection/download activity
for these eight updates. Following the detection and the uploading of events
to the ReportingWebService, review the status as reported by the WSUS
server, to determine if the new instance of this client appears and is
reported correctly with regard to installed and needed updates.
Post by Trond Mahle
Thanks, but I'm not sure if I totally agree with your conclusion. The way we
use target groups has definitive worked the last 1/2 year for all other WSUS
clients in our network (servers, desktops, laptops). It's configured "after
the book" in our GPO Editor, the only difference is that we move the clients
manually from "Unassigned Computers" to their appropriate group in WSUS Admin
(with exactly the same group name as used in GPO Editor).
The special in this case was that the laptop already existed in our WSUS
group "ME Laptops" when it got a new blank harddisk which was configured like
1. WXP installed from recovery CD following the laptop.
2. Connected direct to a brodband line logged in as local Administrator and
manually patched from windowsupdate.microsoft.com until WXP SP2 had been
installed (no more updates afterwards).
3. Connected to our LAN/domain to complete the rest of the WXP
configuration, installing applications etc.
When I came back from holiday 08.08.2005 I found the laptop both in the WSUS
group "Unassigned Computers" (new entry with a long list of updates
"Needed"), and in our WSUS group "ME Laptops" (old entry with an exclamation
mark in front of it indicating no contact last week).
4. I then deleted the old entry end moved the new entry into our WSUS group
"ME Laptops" where all needed updates for laptops with WXP SP1/SP2 have been
approved since we started with WUS in february 2005. I'm not sure exactly
what day I moved it, but it must have been between 8th-10th of August.
5. All updates except for the 8 remaining were then installed on the laptop
during the next days (11th-12th ?).
6. Almost at the same time, 10th of August 09:54 AM CEST, I successfully
synchronized the server with Microsoft because they had relased new August
patches. Afterwards all new August WXP SP2 updates were approved for WSUS
group "ME Laptops".
- Screendump of WSUS Admin showing the problem.
- Complete WindowsUpdate.log from the client.
- Complete ReportingEvents.log from the client.
Hope we come to a conclusion soon! :-))
Best regards Trond
-----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Prior to 8/11, it appears that ALL updates applied to this system were
obtained via Windows Update. On the morning of 8/11, Automatic Updates
downloaded these updates, and scheduled them for installation at 11:00am
2005-08-11 07:55:38+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836) - Security Update for
Windows XP (KB896422)
The installation was successful, and the system restarted.
Then, on the morning of 8/12, these updates were detected and downloaded and
scheduled for installation on 8/12 at 11am.
2005-08-12 07:54:25+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for Windows XP
(KB899591) - Security Update for Windows XP (KB899587)
The installation was successful, and the system restarted.
No other updates were ever detected for installation, although the
detections continued to run twice daily.
A question to be asked, for sure, is what was the configuration of the
system on 8/11 and 8/12.
I suspect it has to do with how you're configuring and using target groups.
Part of this may be answered by the WindowsUpdate.log, so now I'm going to
ask you to email me the WindowsUpdate.log for 8/11 and 8/12.
Please remove the "nospam" subdomain prefix from my email address to get
it to me.
Post by Trond Mahle
(Emailing this file to you failed, so I try to post only this again)
************************************************************
ReportingEvents.log (part 1)
************************************************************
{51200BAC-959B-4D65-848E-A484B7907A9F} 2005-08-04
14:41:20+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{91EA3FC8-8DFD-4A4D-A472-4CECAD9E86A2} 2005-08-04
14:44:54+0200 1 162 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CAA072D6-CCBE-4010-BBF8-FD61120B127B} 2005-08-04
14:45:25+0200 1 184 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP 5.1 (KB842773)
{E377564F-1464-4E08-AABA-C34198F4C6E7} 2005-08-04
14:48:12+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{9C9BA0E9-73DB-40AE-950C-D547274B94E3} 2005-08-04
14:50:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{BC1BD5AD-0340-4C0B-AD3D-A2116184533B} 2005-08-04
14:51:03+0200 1 162 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content Download Download succeeded.
{0A1F770F-B076-4308-B96D-784677CF54CF} 2005-08-04
14:51:12+0200 1 162 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content Download Download succeeded.
{284E4ADD-1748-43CB-8C94-6B77BC81DF55} 2005-08-04
14:51:16+0200 1 162 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content Download Download succeeded.
{ED9211A0-75EE-4EDB-99A3-671E4A2DF1B9} 2005-08-04
14:51:22+0200 1 162 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content Download Download succeeded.
{9A3218C8-488F-46DA-9F3A-823D788E842E} 2005-08-04
14:51:28+0200 1 162 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4EC53112-7F22-4263-AC09-7470E9024BAF} 2005-08-04
14:51:44+0200 1 162 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content Download Download succeeded.
{EFF52EBC-7000-461F-AD16-6D96A5BA41D4} 2005-08-04
14:51:51+0200 1 162 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content Download Download succeeded.
{C49542B7-76AF-4F04-AA47-2228A12117FC} 2005-08-04
14:51:55+0200 1 162 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content Download Download succeeded.
{6E53A72F-464D-4F2F-911C-88C1DF0D796F} 2005-08-04
14:52:01+0200 1 162 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content Download Download succeeded.
{77A920E5-4EFF-491B-9331-6091995EAA60} 2005-08-04
14:52:06+0200 1 162 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4C261E65-76CC-4899-BA08-2E5DA2231317} 2005-08-04
14:53:04+0200 1 162 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CC8F48D2-7E55-4B10-883A-6353B70EE84A} 2005-08-04
14:53:07+0200 1 162 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content Download Download succeeded.
{7DB803A1-282C-4240-BE9F-34C344682409} 2005-08-04
14:53:43+0200 1 162 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content Download Download succeeded.
{65F4D51C-DCA4-460E-AC23-EA7419C36D7D} 2005-08-04
14:54:20+0200 1 162 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content Download Download succeeded.
{9A5724CF-FDDF-4DDB-990B-3975F6ED84D0} 2005-08-04
14:54:25+0200 1 162 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content Download Download succeeded.
{00BA3052-938D-4D02-9D8E-D3D0EC91F45F} 2005-08-04
14:54:55+0200 1 162 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content Download Download succeeded.
{25B67F37-9CAF-4786-BF4D-1F731DFC7F4C} 2005-08-04
14:54:59+0200 1 162 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CB35FCF6-D70F-4BC4-B35C-E0B18F1398BD} 2005-08-04
14:55:06+0200 1 162 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content Download Download succeeded.
{F383854F-9B53-4F56-A523-A4A90FE6FB82} 2005-08-04
14:55:27+0200 1 184 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Q329048: Security Update
{750C65CB-A8E2-49B1-BE3E-72A3CF1DF79E} 2005-08-04
14:55:37+0200 1 183 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q323255: Security Update (Windows XP)
{36C11980-D0CD-4265-A2E0-071D7863A9A3} 2005-08-04
14:55:46+0200 1 183 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329390: Security Update
{A4AE3694-2575-4CA0-8BD4-9693524B85C2} 2005-08-04
14:55:53+0200 1 183 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329115: Security Update (Windows XP)
{0F673CE2-F7C5-446E-959F-D6EF9AFEEF5D} 2005-08-04
14:57:09+0200 1 184 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 329170: Security Update
{85CC6E9C-93CB-4210-A9CF-B5AA650A6561} 2005-08-04
14:58:10+0200 1 183 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 811630: Critical Update (Windows XP)
{DBBDDA61-4C57-4CED-9E64-BBD9C90AE141} 2005-08-04
14:59:22+0200 1 184 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 810577: Security Update
{ED2EA0B9-F00B-4F72-BBFB-8F488A7D9EAD} 2005-08-04
15:00:27+0200 1 183 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329441: Critical Update
{0489C1FD-3174-454A-82BE-99DE9C10284F} 2005-08-04
15:01:35+0200 1 184 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 817606: Security Update (Windows XP)
{179CD1C9-0538-401B-B9D7-3C0CD3A34630} 2005-08-04
15:02:36+0200 1 183 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 823559: Security Update for Microsoft Windows
{DD8BCB23-E493-44F1-9F85-DE3F6B03156E} 2005-08-04
15:02:55+0200 1 184 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 816093: Security Update Microsoft Virtual Machine (Microsoft VM)
{9EF16527-F5F4-4884-B82C-5518BA2A3E15} 2005-08-04
15:03:05+0200 1 183 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Security Update for Windows XP (329834)
{E63D55A4-54CE-4A30-AB7C-7F645FD6AF0F} 2005-08-04
15:03:30+0200 1 184 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB828741)
{50448B87-4A5E-4D94-BAC4-E6E8102D2E6C} 2005-08-04
15:03:51+0200 1 184 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Cumulative Security Update for Internet Explorer 6 (KB834707)
{F6C3ACF4-84BD-45F7-8BA3-3ED7C1963B4D} 2005-08-04
15:05:02+0200 1 183 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: 810833: Security Update (Windows XP)
{D4C06C02-CF68-4678-9010-542B12908CB5} 2005-08-04
15:05:23+0200 1 184 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB835732)
{D25C8BDA-577B-45D0-9232-AA30B1927F6A} 2005-08-04
15:05:36+0200 1 183 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Critical Update for Windows (KB833407)
{6EDE3346-731F-4DAC-BDB8-50F241990A1E} 2005-08-04
15:05:46+0200 1 183 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Windows Malicious Software Removal Tool - July 2005 (KB890830)
{C0D63CA6-13F1-4EAC-904C-D4B5E871FCED} 2005-08-04
15:08:04+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{5F0306E6-34E9-45AE-991E-7788E63A6C4B} 2005-08-04
15:11:43+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{489AC236-F289-47FC-944F-19715A4160C5} 2005-08-04
15:39:59+0200 1 162 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0
WindowsUpdate Success Content Download Download succeeded.
{C0915366-D759-4B56-8D44-D15C4FCF504D} 2005-08-04
16:00:18+0200 1 184 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 124 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Windows XP Service Pack 2
{E0285061-6C8D-4AA1-B1CF-152147BD9404} 2005-08-04
16:17:14+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{C86DD579-251B-4D49-B7DC-D09184063549} 2005-08-04
16:20:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{29D43466-BA1D-411E-BEDE-EEFCAA28FA42} 2005-08-04
16:25:51+0200 1 162 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0
WindowsUpdate Success Content Download Download succeeded.
{FC0B4FFA-FB4A-4346-9391-7904F4964603} 2005-08-04
16:27:45+0200 1 162 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0
WindowsUpdate Success Content Download Download succeeded.
{691C1BD1-2DE8-4E63-86E8-23F818454B96} 2005-08-04
16:29:09+0200 1 162 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0
WindowsUpdate Success Content Download Download succeeded.
{25385FCB-400E-4D8B-BADA-E59CF7EABBDC} 2005-08-04
16:29:46+0200 1 184 101 {B166A6A9-398B-4C81-B8DB-2043CF0672A1} 103 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Microsoft Windows Installer 3.1
{027EAAFC-0706-4618-902B-CCD91789FC98} 2005-08-04
16:30:04+0200 1 183 101 {279FE710-6AA0-4691-89F0-3B3012720B51} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Windows Genuine Advantage Validation Tool (KB892130)
{53475F43-7B4F-4D22-B57B-3719D017B59D} 2005-08-04
16:30:10+0200 1 183 101 {D3AC165E-D7C4-4BDF-83F0-E249ECBE873B} 101 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Update for Windows XP (KB898461)
{7F9DC850-B1C9-497D-8966-4FFAC1EB0CA8} 2005-08-04
16:31:56+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{05CDBB95-37BB-4FDC-BB04-54BC4A31FA2E} 2005-08-04
16:35:20+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{F950C9CB-76E6-4928-8DE0-CBF9677D19D0} 2005-08-04
17:21:28+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{E103CFC8-08CC-4DE2-803A-0E8AC66ED5D4} 2005-08-04
18:24:42+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{47CEF528-8305-49CA-B849-D65C597667CD} 2005-08-04
18:57:36+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2
AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80072ee2
{A1D456A5-A604-48D9-8D3B-89632960BE5E} 2005-08-05
07:39:13+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Software Synchronization Agent has finished
Trond Mahle
2005-08-29 11:27:02 UTC
Permalink
Hello Lawrence,
I've now followed your proposal below in detail (1-7) without success. The
WSUS Console still report the same 8 updates as Needed! I e-mail you a report
showing you the procedure we followed and the result.

Meanwhile we had to re-install another desktop in the same way as this
"problem laptop", and that went very well. The only difference between the 2
re-installations are:
1. The laptop got WXP without SP from its restore CD, and was then patched
to WXP SP2 from windowsupdate.microsoft.com. The desktop got WXP SP2 directly
from a CD.
2. The laptop belongs to our WSUS group "ME Laptops". The desktop belongs to
our WSUS group "ME Desktops".

I suspect the problem is related to how WXP was re-installed on the 2 PCs
(point 1) because our two WSUS groups have been built/used in the same way.
Should I only try to install the updates manually on the laptop to get rid of
this problem, or do you have another proposal? Hopefully this is a disposable
case.....
Post by Lawrence Garvin
I received your email and attachements.
I'm letting go of the 'target group' consideration.... the client appears to
have been consistently a member of that group, and your screenshot of the
WSUS server shows those updates as approved for installation for that target
group.
What's problematic with this scenario is that the client has /never/
detected those eight updates, and still isn't detecting them. I suspect
there is corrupted data somewhere -- perhaps the datastore.edb on the
client, perhaps the data in the susdb.mdf on the server, perhaps both, even.
The updates should not be showing as "Needed" on the server because the
client has never detected, and thus never reported 'events' for that
detection. Whether the updates /should/ be detected at this point is really
a secondary issue. The client is not detecting them, and the data, as
reported on the WSUS server, is incorrect.
What I think happened. but I don't exactly understand how, is that
/something/ caused this client's record to be updated with these detections.
Maybe this is fallout from a duplicate SusClientID?
The questions we have at the moment: Are the updates actually installed? Are
they even required -- as noted, /some/ of the updates may, in fact, be N/A.
Here's what I would suggest as a "fix" for the whole situation -- it's a
radical fix, but I believe it will clean house - so to speak.
1. At the client, shutdown Automatic Updates service.
2. At the client, use bitsadmin to check the BITS queue, and flush it if
there's anything there.
3. At the client, make a backup of the %windir%\SoftwareDistribution folder
and all subfolders
and the %windir%\WindowsUpdate.log file.
%windir%\SoftwareDistribution\Datastore\Logs\edb*.*
%windir%\SoftwareDistribution\Datastore\DataStore.edb
%windir%\SoftwareDistribution\Download
%windir%\SoftwareDistribution\EventCache
%windir%\SoftwareDistribution\ReportingEvents.log
%windir%\WindowsUpdate.log
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new SusClientId, which
will force the creation of an all new database record (thus avoiding any
potential issues with corruption or bad data in the original record, that
may or may not actually be physically present in the database).
6. At the server, delete pc176.moxy.no from the WSUS server, completely.
7. At the client, restart the Automatic Updates service, and monitor the
WindowsUpdate.log and/or ReportingEvents.log for detection/download activity
for these eight updates. Following the detection and the uploading of events
to the ReportingWebService, review the status as reported by the WSUS
server, to determine if the new instance of this client appears and is
reported correctly with regard to installed and needed updates.
Post by Trond Mahle
Thanks, but I'm not sure if I totally agree with your conclusion. The way we
use target groups has definitive worked the last 1/2 year for all other WSUS
clients in our network (servers, desktops, laptops). It's configured "after
the book" in our GPO Editor, the only difference is that we move the clients
manually from "Unassigned Computers" to their appropriate group in WSUS Admin
(with exactly the same group name as used in GPO Editor).
The special in this case was that the laptop already existed in our WSUS
group "ME Laptops" when it got a new blank harddisk which was configured like
1. WXP installed from recovery CD following the laptop.
2. Connected direct to a brodband line logged in as local Administrator and
manually patched from windowsupdate.microsoft.com until WXP SP2 had been
installed (no more updates afterwards).
3. Connected to our LAN/domain to complete the rest of the WXP
configuration, installing applications etc.
When I came back from holiday 08.08.2005 I found the laptop both in the WSUS
group "Unassigned Computers" (new entry with a long list of updates
"Needed"), and in our WSUS group "ME Laptops" (old entry with an exclamation
mark in front of it indicating no contact last week).
4. I then deleted the old entry end moved the new entry into our WSUS group
"ME Laptops" where all needed updates for laptops with WXP SP1/SP2 have been
approved since we started with WUS in february 2005. I'm not sure exactly
what day I moved it, but it must have been between 8th-10th of August.
5. All updates except for the 8 remaining were then installed on the laptop
during the next days (11th-12th ?).
6. Almost at the same time, 10th of August 09:54 AM CEST, I successfully
synchronized the server with Microsoft because they had relased new August
patches. Afterwards all new August WXP SP2 updates were approved for WSUS
group "ME Laptops".
- Screendump of WSUS Admin showing the problem.
- Complete WindowsUpdate.log from the client.
- Complete ReportingEvents.log from the client.
Hope we come to a conclusion soon! :-))
Best regards Trond
-----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Prior to 8/11, it appears that ALL updates applied to this system were
obtained via Windows Update. On the morning of 8/11, Automatic Updates
downloaded these updates, and scheduled them for installation at 11:00am
2005-08-11 07:55:38+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836) - Security Update for
Windows XP (KB896422)
The installation was successful, and the system restarted.
Then, on the morning of 8/12, these updates were detected and downloaded and
scheduled for installation on 8/12 at 11am.
2005-08-12 07:54:25+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for Windows XP
(KB899591) - Security Update for Windows XP (KB899587)
The installation was successful, and the system restarted.
No other updates were ever detected for installation, although the
detections continued to run twice daily.
A question to be asked, for sure, is what was the configuration of the
system on 8/11 and 8/12.
I suspect it has to do with how you're configuring and using target groups.
Part of this may be answered by the WindowsUpdate.log, so now I'm going to
ask you to email me the WindowsUpdate.log for 8/11 and 8/12.
Please remove the "nospam" subdomain prefix from my email address to get
it to me.
Post by Trond Mahle
(Emailing this file to you failed, so I try to post only this again)
************************************************************
ReportingEvents.log (part 1)
************************************************************
{51200BAC-959B-4D65-848E-A484B7907A9F} 2005-08-04
14:41:20+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{91EA3FC8-8DFD-4A4D-A472-4CECAD9E86A2} 2005-08-04
14:44:54+0200 1 162 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CAA072D6-CCBE-4010-BBF8-FD61120B127B} 2005-08-04
14:45:25+0200 1 184 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP 5.1 (KB842773)
{E377564F-1464-4E08-AABA-C34198F4C6E7} 2005-08-04
14:48:12+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{9C9BA0E9-73DB-40AE-950C-D547274B94E3} 2005-08-04
14:50:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{BC1BD5AD-0340-4C0B-AD3D-A2116184533B} 2005-08-04
14:51:03+0200 1 162 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content Download Download succeeded.
{0A1F770F-B076-4308-B96D-784677CF54CF} 2005-08-04
14:51:12+0200 1 162 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content Download Download succeeded.
{284E4ADD-1748-43CB-8C94-6B77BC81DF55} 2005-08-04
14:51:16+0200 1 162 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content Download Download succeeded.
{ED9211A0-75EE-4EDB-99A3-671E4A2DF1B9} 2005-08-04
14:51:22+0200 1 162 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content Download Download succeeded.
{9A3218C8-488F-46DA-9F3A-823D788E842E} 2005-08-04
14:51:28+0200 1 162 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4EC53112-7F22-4263-AC09-7470E9024BAF} 2005-08-04
14:51:44+0200 1 162 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content Download Download succeeded.
{EFF52EBC-7000-461F-AD16-6D96A5BA41D4} 2005-08-04
14:51:51+0200 1 162 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content Download Download succeeded.
{C49542B7-76AF-4F04-AA47-2228A12117FC} 2005-08-04
14:51:55+0200 1 162 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content Download Download succeeded.
{6E53A72F-464D-4F2F-911C-88C1DF0D796F} 2005-08-04
14:52:01+0200 1 162 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content Download Download succeeded.
{77A920E5-4EFF-491B-9331-6091995EAA60} 2005-08-04
14:52:06+0200 1 162 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4C261E65-76CC-4899-BA08-2E5DA2231317} 2005-08-04
14:53:04+0200 1 162 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CC8F48D2-7E55-4B10-883A-6353B70EE84A} 2005-08-04
14:53:07+0200 1 162 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content Download Download succeeded.
{7DB803A1-282C-4240-BE9F-34C344682409} 2005-08-04
14:53:43+0200 1 162 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content Download Download succeeded.
{65F4D51C-DCA4-460E-AC23-EA7419C36D7D} 2005-08-04
14:54:20+0200 1 162 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content Download Download succeeded.
{9A5724CF-FDDF-4DDB-990B-3975F6ED84D0} 2005-08-04
14:54:25+0200 1 162 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content Download Download succeeded.
{00BA3052-938D-4D02-9D8E-D3D0EC91F45F} 2005-08-04
14:54:55+0200 1 162 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content Download Download succeeded.
{25B67F37-9CAF-4786-BF4D-1F731DFC7F4C} 2005-08-04
14:54:59+0200 1 162 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CB35FCF6-D70F-4BC4-B35C-E0B18F1398BD} 2005-08-04
14:55:06+0200 1 162 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content Download Download succeeded.
{F383854F-9B53-4F56-A523-A4A90FE6FB82} 2005-08-04
14:55:27+0200 1 184 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Q329048: Security Update
{750C65CB-A8E2-49B1-BE3E-72A3CF1DF79E} 2005-08-04
14:55:37+0200 1 183 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q323255: Security Update (Windows XP)
{36C11980-D0CD-4265-A2E0-071D7863A9A3} 2005-08-04
14:55:46+0200 1 183 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329390: Security Update
{A4AE3694-2575-4CA0-8BD4-9693524B85C2} 2005-08-04
14:55:53+0200 1 183 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329115: Security Update (Windows XP)
{0F673CE2-F7C5-446E-959F-D6EF9AFEEF5D} 2005-08-04
14:57:09+0200 1 184 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 329170: Security Update
{85CC6E9C-93CB-4210-A9CF-B5AA650A6561} 2005-08-04
14:58:10+0200 1 183 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
Lawrence Garvin
2005-08-29 15:43:28 UTC
Permalink
I got your email... reviewed the results.

I have two possibilities.

Either another system is reporting with the same SusClientID (not likely
since this system was rebuilt from scratch)

or the database on the WSUS server has corrupted data that is reappearing on
the console.

The other thing you should do is inspect the IIS Logs and find out /what/
reported to the WSUS server between the time the new system reported
originally, and the time the '8 updates needed' appeared on the WSUS server.
I think the WUA is accurate in it assessment, those updates are not needed.
As I recall, some of those updates were contingent upon software being
installed, and a couple of them are actually superceded by newer
(installed??) updates.

There are definitely possibilities that things are being 'misreported' since
you actually did the updates from windowsupdate.com, and then directed the
system to the WSUS server. (Side note: see
http://wsusinfo.onsitechsolutions.com/articles/012.htm and 010.htm for some
insight on how you can use your WSUS server to fully update new systems,
totally unattended, in less time than it takes you to do them from
WindowsUpdate.com interactively. Doing so may also help stablize your
reporting to WSUS.)

This can also be an unanticipated side-effect of mixing and matching
client-side targeting with server-side targeting.

It could even be that the cumulative combination of all of these unique
conditions is causing some conflict in reporting.

It seems to me that the /best/ option for further testing at this point
would be:

(1) Shutdown the notebook.

(2) Remove the computer from the WSUS Server (make sure you choose the
option to completely remove the data, not just move the computer to
Unassigned Computers). Note: In general, when systems are known to be
rebuilt, I think it would be a good idea to purge the old system from the
WSUS server /before/ putting the new system online if the same machine name
is going to be used.

(3) Install the OS from media and then /update/ the system exclusively from
WSUS.
Post by Trond Mahle
Hello Lawrence,
I've now followed your proposal below in detail (1-7) without success. The
WSUS Console still report the same 8 updates as Needed! I e-mail you a report
showing you the procedure we followed and the result.
Meanwhile we had to re-install another desktop in the same way as this
"problem laptop", and that went very well. The only difference between the 2
1. The laptop got WXP without SP from its restore CD, and was then patched
to WXP SP2 from windowsupdate.microsoft.com. The desktop got WXP SP2 directly
from a CD.
2. The laptop belongs to our WSUS group "ME Laptops". The desktop belongs to
our WSUS group "ME Desktops".
I suspect the problem is related to how WXP was re-installed on the 2 PCs
(point 1) because our two WSUS groups have been built/used in the same way.
Should I only try to install the updates manually on the laptop to get rid of
this problem, or do you have another proposal? Hopefully this is a disposable
case.....
Post by Lawrence Garvin
I received your email and attachements.
I'm letting go of the 'target group' consideration.... the client appears to
have been consistently a member of that group, and your screenshot of the
WSUS server shows those updates as approved for installation for that target
group.
What's problematic with this scenario is that the client has /never/
detected those eight updates, and still isn't detecting them. I suspect
there is corrupted data somewhere -- perhaps the datastore.edb on the
client, perhaps the data in the susdb.mdf on the server, perhaps both, even.
The updates should not be showing as "Needed" on the server because the
client has never detected, and thus never reported 'events' for that
detection. Whether the updates /should/ be detected at this point is really
a secondary issue. The client is not detecting them, and the data, as
reported on the WSUS server, is incorrect.
What I think happened. but I don't exactly understand how, is that
/something/ caused this client's record to be updated with these detections.
Maybe this is fallout from a duplicate SusClientID?
The questions we have at the moment: Are the updates actually installed? Are
they even required -- as noted, /some/ of the updates may, in fact, be N/A.
Here's what I would suggest as a "fix" for the whole situation -- it's a
radical fix, but I believe it will clean house - so to speak.
1. At the client, shutdown Automatic Updates service.
2. At the client, use bitsadmin to check the BITS queue, and flush it if
there's anything there.
3. At the client, make a backup of the %windir%\SoftwareDistribution folder
and all subfolders
and the %windir%\WindowsUpdate.log file.
%windir%\SoftwareDistribution\Datastore\Logs\edb*.*
%windir%\SoftwareDistribution\Datastore\DataStore.edb
%windir%\SoftwareDistribution\Download
%windir%\SoftwareDistribution\EventCache
%windir%\SoftwareDistribution\ReportingEvents.log
%windir%\WindowsUpdate.log
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new SusClientId, which
will force the creation of an all new database record (thus avoiding any
potential issues with corruption or bad data in the original record, that
may or may not actually be physically present in the database).
6. At the server, delete pc176.moxy.no from the WSUS server, completely.
7. At the client, restart the Automatic Updates service, and monitor the
WindowsUpdate.log and/or ReportingEvents.log for detection/download activity
for these eight updates. Following the detection and the uploading of events
to the ReportingWebService, review the status as reported by the WSUS
server, to determine if the new instance of this client appears and is
reported correctly with regard to installed and needed updates.
Post by Trond Mahle
Thanks, but I'm not sure if I totally agree with your conclusion. The
way
we
use target groups has definitive worked the last 1/2 year for all other WSUS
clients in our network (servers, desktops, laptops). It's configured "after
the book" in our GPO Editor, the only difference is that we move the clients
manually from "Unassigned Computers" to their appropriate group in WSUS Admin
(with exactly the same group name as used in GPO Editor).
The special in this case was that the laptop already existed in our WSUS
group "ME Laptops" when it got a new blank harddisk which was
configured
like
1. WXP installed from recovery CD following the laptop.
2. Connected direct to a brodband line logged in as local Administrator and
manually patched from windowsupdate.microsoft.com until WXP SP2 had been
installed (no more updates afterwards).
3. Connected to our LAN/domain to complete the rest of the WXP
configuration, installing applications etc.
When I came back from holiday 08.08.2005 I found the laptop both in the WSUS
group "Unassigned Computers" (new entry with a long list of updates
"Needed"), and in our WSUS group "ME Laptops" (old entry with an exclamation
mark in front of it indicating no contact last week).
4. I then deleted the old entry end moved the new entry into our WSUS group
"ME Laptops" where all needed updates for laptops with WXP SP1/SP2 have been
approved since we started with WUS in february 2005. I'm not sure exactly
what day I moved it, but it must have been between 8th-10th of August.
5. All updates except for the 8 remaining were then installed on the laptop
during the next days (11th-12th ?).
6. Almost at the same time, 10th of August 09:54 AM CEST, I
successfully
synchronized the server with Microsoft because they had relased new August
patches. Afterwards all new August WXP SP2 updates were approved for WSUS
group "ME Laptops".
- Screendump of WSUS Admin showing the problem.
- Complete WindowsUpdate.log from the client.
- Complete ReportingEvents.log from the client.
Hope we come to a conclusion soon! :-))
Best regards Trond
-----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Prior to 8/11, it appears that ALL updates applied to this system were
obtained via Windows Update. On the morning of 8/11, Automatic Updates
downloaded these updates, and scheduled them for installation at 11:00am
2005-08-11 07:55:38+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet
Explorer
for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security
Update
for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for
Windows
XP
(KB885250) - Security Update for Windows XP (KB885836) - Security
Update
for
Windows XP (KB896422)
The installation was successful, and the system restarted.
Then, on the morning of 8/12, these updates were detected and
downloaded
and
scheduled for installation on 8/12 at 11am.
2005-08-12 07:54:25+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP
(KB896423) -
Security Update for Windows XP (KB893756) - Security Update for
Windows
XP
(KB899591) - Security Update for Windows XP (KB899587)
The installation was successful, and the system restarted.
No other updates were ever detected for installation, although the
detections continued to run twice daily.
A question to be asked, for sure, is what was the configuration of the
system on 8/11 and 8/12.
I suspect it has to do with how you're configuring and using target groups.
Part of this may be answered by the WindowsUpdate.log, so now I'm
going
to
ask you to email me the WindowsUpdate.log for 8/11 and 8/12.
Please remove the "nospam" subdomain prefix from my email address
to
get
it to me.
Post by Trond Mahle
(Emailing this file to you failed, so I try to post only this again)
************************************************************
ReportingEvents.log (part 1)
************************************************************
{51200BAC-959B-4D65-848E-A484B7907A9F} 2005-08-04
14:41:20+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{91EA3FC8-8DFD-4A4D-A472-4CECAD9E86A2} 2005-08-04
14:44:54+0200 1 162 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CAA072D6-CCBE-4010-BBF8-FD61120B127B} 2005-08-04
14:45:25+0200 1 184 101 {3E1EE9BF-A5F6-4CD8-BF9F-310F4CFDBAD1} 101 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Update for Background Intelligent Transfer Service (BITS)
2.0
and
WinHTTP 5.1 (KB842773)
{E377564F-1464-4E08-AABA-C34198F4C6E7} 2005-08-04
14:48:12+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0
AutomaticUpdates Success Content Install Reboot completed.
{9C9BA0E9-73DB-40AE-950C-D547274B94E3} 2005-08-04
14:50:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
WindowsUpdate Success Software Synchronization Agent has finished
detecting items.
{BC1BD5AD-0340-4C0B-AD3D-A2116184533B} 2005-08-04
14:51:03+0200 1 162 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content Download Download succeeded.
{0A1F770F-B076-4308-B96D-784677CF54CF} 2005-08-04
14:51:12+0200 1 162 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content Download Download succeeded.
{284E4ADD-1748-43CB-8C94-6B77BC81DF55} 2005-08-04
14:51:16+0200 1 162 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content Download Download succeeded.
{ED9211A0-75EE-4EDB-99A3-671E4A2DF1B9} 2005-08-04
14:51:22+0200 1 162 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content Download Download succeeded.
{9A3218C8-488F-46DA-9F3A-823D788E842E} 2005-08-04
14:51:28+0200 1 162 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4EC53112-7F22-4263-AC09-7470E9024BAF} 2005-08-04
14:51:44+0200 1 162 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content Download Download succeeded.
{EFF52EBC-7000-461F-AD16-6D96A5BA41D4} 2005-08-04
14:51:51+0200 1 162 101 {805C16AB-EA6E-411D-9A48-DF7E0440E871} 100 0
WindowsUpdate Success Content Download Download succeeded.
{C49542B7-76AF-4F04-AA47-2228A12117FC} 2005-08-04
14:51:55+0200 1 162 101 {B2B4FF3A-BA40-4E3E-98E6-A54CACF66998} 100 0
WindowsUpdate Success Content Download Download succeeded.
{6E53A72F-464D-4F2F-911C-88C1DF0D796F} 2005-08-04
14:52:01+0200 1 162 101 {3893052E-B8AD-4943-81F8-DEAE9335B340} 100 0
WindowsUpdate Success Content Download Download succeeded.
{77A920E5-4EFF-491B-9331-6091995EAA60} 2005-08-04
14:52:06+0200 1 162 101 {4B55C1C5-F1B7-46E9-A4AF-DABC8D341743} 100 0
WindowsUpdate Success Content Download Download succeeded.
{4C261E65-76CC-4899-BA08-2E5DA2231317} 2005-08-04
14:53:04+0200 1 162 101 {9E76C27B-C53A-4D17-8E30-5D8B703F8778} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CC8F48D2-7E55-4B10-883A-6353B70EE84A} 2005-08-04
14:53:07+0200 1 162 101 {8274F4C5-6130-4B8A-A632-9E2115ACFD1E} 101 0
WindowsUpdate Success Content Download Download succeeded.
{7DB803A1-282C-4240-BE9F-34C344682409} 2005-08-04
14:53:43+0200 1 162 101 {ABD1C3EF-987D-4A04-83DB-CEC22495D3B7} 102 0
WindowsUpdate Success Content Download Download succeeded.
{65F4D51C-DCA4-460E-AC23-EA7419C36D7D} 2005-08-04
14:54:20+0200 1 162 101 {049E0EAC-F3D7-4F23-8546-9729202E1A72} 101 0
WindowsUpdate Success Content Download Download succeeded.
{9A5724CF-FDDF-4DDB-990B-3975F6ED84D0} 2005-08-04
14:54:25+0200 1 162 101 {E9871499-E316-45EF-845D-55E4F28190B0} 102 0
WindowsUpdate Success Content Download Download succeeded.
{00BA3052-938D-4D02-9D8E-D3D0EC91F45F} 2005-08-04
14:54:55+0200 1 162 101 {ED095ADB-093B-4755-8EA4-F84A8AB40C11} 104 0
WindowsUpdate Success Content Download Download succeeded.
{25B67F37-9CAF-4786-BF4D-1F731DFC7F4C} 2005-08-04
14:54:59+0200 1 162 101 {0CF85BCD-9C4E-495E-AB26-B634A4D0E7C6} 101 0
WindowsUpdate Success Content Download Download succeeded.
{CB35FCF6-D70F-4BC4-B35C-E0B18F1398BD} 2005-08-04
14:55:06+0200 1 162 101 {32BC69AD-E033-4000-9613-0604FFF996D2} 100 0
WindowsUpdate Success Content Download Download succeeded.
{F383854F-9B53-4F56-A523-A4A90FE6FB82} 2005-08-04
14:55:27+0200 1 184 101 {DEF7E2BD-44F0-4FEB-AA92-B1D8A289D740} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Q329048: Security Update
{750C65CB-A8E2-49B1-BE3E-72A3CF1DF79E} 2005-08-04
14:55:37+0200 1 183 101 {6DDF4501-647A-4FF7-B437-34B53F16F32C} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q323255: Security Update (Windows XP)
{36C11980-D0CD-4265-A2E0-071D7863A9A3} 2005-08-04
14:55:46+0200 1 183 101 {D9ADFD01-6C60-45DD-91ED-CDA4CC476C08} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329390: Security Update
{A4AE3694-2575-4CA0-8BD4-9693524B85C2} 2005-08-04
14:55:53+0200 1 183 101 {E5AB6B0A-EB0B-4EC1-BAD0-FB2E5DBC3665} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
following
update: Q329115: Security Update (Windows XP)
{0F673CE2-F7C5-446E-959F-D6EF9AFEEF5D} 2005-08-04
14:57:09+0200 1 184 101 {58035B1F-FB5C-48C5-B7CE-A19A2F788C39} 100 0
WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: 329170: Security Update
{85CC6E9C-93CB-4210-A9CF-B5AA650A6561} 2005-08-04
14:58:10+0200 1 183 101 {3BDA7C76-2FB7-42EB-B3FC-299FBA109833} 100 0
WindowsUpdate Success Content
Install Installation Successful: Windows successfully installed the
Trond Mahle
2005-08-30 12:49:36 UTC
Permalink
Hello Lawrence,
Today I have some good news for you - everything is now OK!! At 11:00 AM
this morning the last 8 'Needed' patches installed themselves without me
doing anything. Actually I was preparing a manual installation of them, but
luckily I was disturbed and the clock passed the time for WSUS installation
set in GPO.... I was noticed by the user that had got a question about reboot
on his screen.

So your previous solution worked (point 1-7), it only took some time! I
e-mail you the last version of the 2 log-files if you are interested to take
a final look at them. Thanks a lot for your patience and help!!

Best regards Trond :-)))
Post by Lawrence Garvin
I got your email... reviewed the results.
I have two possibilities.
Either another system is reporting with the same SusClientID (not likely
since this system was rebuilt from scratch)
or the database on the WSUS server has corrupted data that is reappearing on
the console.
The other thing you should do is inspect the IIS Logs and find out /what/
reported to the WSUS server between the time the new system reported
originally, and the time the '8 updates needed' appeared on the WSUS server.
I think the WUA is accurate in it assessment, those updates are not needed.
As I recall, some of those updates were contingent upon software being
installed, and a couple of them are actually superceded by newer
(installed??) updates.
There are definitely possibilities that things are being 'misreported' since
you actually did the updates from windowsupdate.com, and then directed the
system to the WSUS server. (Side note: see
http://wsusinfo.onsitechsolutions.com/articles/012.htm and 010.htm for some
insight on how you can use your WSUS server to fully update new systems,
totally unattended, in less time than it takes you to do them from
WindowsUpdate.com interactively. Doing so may also help stablize your
reporting to WSUS.)
This can also be an unanticipated side-effect of mixing and matching
client-side targeting with server-side targeting.
It could even be that the cumulative combination of all of these unique
conditions is causing some conflict in reporting.
It seems to me that the /best/ option for further testing at this point
(1) Shutdown the notebook.
(2) Remove the computer from the WSUS Server (make sure you choose the
option to completely remove the data, not just move the computer to
Unassigned Computers). Note: In general, when systems are known to be
rebuilt, I think it would be a good idea to purge the old system from the
WSUS server /before/ putting the new system online if the same machine name
is going to be used.
(3) Install the OS from media and then /update/ the system exclusively from
WSUS.
Post by Trond Mahle
Hello Lawrence,
I've now followed your proposal below in detail (1-7) without success. The
WSUS Console still report the same 8 updates as Needed! I e-mail you a report
showing you the procedure we followed and the result.
Meanwhile we had to re-install another desktop in the same way as this
"problem laptop", and that went very well. The only difference between the 2
1. The laptop got WXP without SP from its restore CD, and was then patched
to WXP SP2 from windowsupdate.microsoft.com. The desktop got WXP SP2 directly
from a CD.
2. The laptop belongs to our WSUS group "ME Laptops". The desktop belongs to
our WSUS group "ME Desktops".
I suspect the problem is related to how WXP was re-installed on the 2 PCs
(point 1) because our two WSUS groups have been built/used in the same way.
Should I only try to install the updates manually on the laptop to get rid of
this problem, or do you have another proposal? Hopefully this is a disposable
case.....
Post by Lawrence Garvin
I received your email and attachements.
I'm letting go of the 'target group' consideration.... the client appears to
have been consistently a member of that group, and your screenshot of the
WSUS server shows those updates as approved for installation for that target
group.
What's problematic with this scenario is that the client has /never/
detected those eight updates, and still isn't detecting them. I suspect
there is corrupted data somewhere -- perhaps the datastore.edb on the
client, perhaps the data in the susdb.mdf on the server, perhaps both, even.
The updates should not be showing as "Needed" on the server because the
client has never detected, and thus never reported 'events' for that
detection. Whether the updates /should/ be detected at this point is really
a secondary issue. The client is not detecting them, and the data, as
reported on the WSUS server, is incorrect.
What I think happened. but I don't exactly understand how, is that
/something/ caused this client's record to be updated with these detections.
Maybe this is fallout from a duplicate SusClientID?
The questions we have at the moment: Are the updates actually installed? Are
they even required -- as noted, /some/ of the updates may, in fact, be N/A.
Here's what I would suggest as a "fix" for the whole situation -- it's a
radical fix, but I believe it will clean house - so to speak.
1. At the client, shutdown Automatic Updates service.
2. At the client, use bitsadmin to check the BITS queue, and flush it if
there's anything there.
3. At the client, make a backup of the %windir%\SoftwareDistribution folder
and all subfolders
and the %windir%\WindowsUpdate.log file.
%windir%\SoftwareDistribution\Datastore\Logs\edb*.*
%windir%\SoftwareDistribution\Datastore\DataStore.edb
%windir%\SoftwareDistribution\Download
%windir%\SoftwareDistribution\EventCache
%windir%\SoftwareDistribution\ReportingEvents.log
%windir%\WindowsUpdate.log
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new SusClientId, which
will force the creation of an all new database record (thus avoiding any
potential issues with corruption or bad data in the original record, that
may or may not actually be physically present in the database).
6. At the server, delete pc176.moxy.no from the WSUS server, completely.
7. At the client, restart the Automatic Updates service, and monitor the
WindowsUpdate.log and/or ReportingEvents.log for detection/download activity
for these eight updates. Following the detection and the uploading of events
to the ReportingWebService, review the status as reported by the WSUS
server, to determine if the new instance of this client appears and is
reported correctly with regard to installed and needed updates.
Post by Trond Mahle
Thanks, but I'm not sure if I totally agree with your conclusion. The
way
we
use target groups has definitive worked the last 1/2 year for all other WSUS
clients in our network (servers, desktops, laptops). It's configured "after
the book" in our GPO Editor, the only difference is that we move the clients
manually from "Unassigned Computers" to their appropriate group in WSUS Admin
(with exactly the same group name as used in GPO Editor).
The special in this case was that the laptop already existed in our WSUS
group "ME Laptops" when it got a new blank harddisk which was
configured
like
1. WXP installed from recovery CD following the laptop.
2. Connected direct to a brodband line logged in as local Administrator and
manually patched from windowsupdate.microsoft.com until WXP SP2 had been
installed (no more updates afterwards).
3. Connected to our LAN/domain to complete the rest of the WXP
configuration, installing applications etc.
When I came back from holiday 08.08.2005 I found the laptop both in the WSUS
group "Unassigned Computers" (new entry with a long list of updates
"Needed"), and in our WSUS group "ME Laptops" (old entry with an exclamation
mark in front of it indicating no contact last week).
4. I then deleted the old entry end moved the new entry into our WSUS group
"ME Laptops" where all needed updates for laptops with WXP SP1/SP2 have been
approved since we started with WUS in february 2005. I'm not sure exactly
what day I moved it, but it must have been between 8th-10th of August.
5. All updates except for the 8 remaining were then installed on the laptop
during the next days (11th-12th ?).
6. Almost at the same time, 10th of August 09:54 AM CEST, I successfully
synchronized the server with Microsoft because they had relased new August
patches. Afterwards all new August WXP SP2 updates were approved for WSUS
group "ME Laptops".
- Screendump of WSUS Admin showing the problem.
- Complete WindowsUpdate.log from the client.
- Complete ReportingEvents.log from the client.
Hope we come to a conclusion soon! :-))
Best regards Trond
-----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Prior to 8/11, it appears that ALL updates applied to this system were
obtained via Windows Update. On the morning of 8/11, Automatic Updates
downloaded these updates, and scheduled them for installation at 11:00am
2005-08-11 07:55:38+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet
Explorer
for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security
Update
for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for
Windows
XP
(KB885250) - Security Update for Windows XP (KB885836) - Security
Update
for
Windows XP (KB896422)
The installation was successful, and the system restarted.
Then, on the morning of 8/12, these updates were detected and
downloaded
and
scheduled for installation on 8/12 at 11am.
2005-08-12 07:54:25+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for
Windows
XP
(KB899591) - Security Update for Windows XP (KB899587)
The installation was successful, and the system restarted.
No other updates were ever detected for installation, although the
detections continued to run twice daily.
A question to be asked, for sure, is what was the configuration of the
system on 8/11 and 8/12.
I suspect it has to do with how you're configuring and using target groups.
Part of this may be answered by the WindowsUpdate.log, so now I'm
going
to
ask you to email me the WindowsUpdate.log for 8/11 and 8/12.
Please remove the "nospam" subdomain prefix from my email address
to
get
it to me.
Post by Trond Mahle
(Emailing this file to you failed, so I try to post only this again)
************************************************************
Lawrence Garvin
2005-08-30 16:44:09 UTC
Permalink
I saw that in your email.

I also saw /NO/ activity in the WindowsUpdate.log file from 8/29 at noon
(when -0- updates were detected) until the next morning when amazingly, the
client detected the remaining updatse.

I'm glad it worked out... but I'm still curious (and confused).. about why
that client did not detect the updates the previous day.

One thing I did notice, following your clean up of the client...

These five log lines did not appear in any transactions on 8/29, but first
appeared at 8/30, when the detection successfully completed. I'm thinking
there may have been an issue on 8/29 with a missing SusClientId...

2005-08-30 08:10:55 1048 10c Agent * WU client version 5.8.0.2469
2005-08-30 08:10:55 1048 10c Agent * SusClientId =
'9823efc8-5d7f-43a4-94f1-0869a93a9ad6'
2005-08-30 08:10:55 1048 10c Agent * Base directory:
C:\Windows\SoftwareDistribution
2005-08-30 08:10:55 1048 10c Agent * Access type: No proxy
2005-08-30 08:10:55 1048 10c Agent * Network state: Connected

which, of course, was not present following the purge of the registry keys:

2005-08-29 10:46:11 1044 ec0 Agent * WU client version 5.8.0.2469
2005-08-29 10:46:11 1044 ec0 Agent * WARNING: Failed to obtain
SusClientId
2005-08-29 10:46:11 1044 ec0 Agent * Base directory:
C:\Windows\SoftwareDistribution
2005-08-29 10:46:11 1044 ec0 Agent * Access type: No proxy
2005-08-29 10:46:11 1044 ec0 Agent * Network state: Connected

and, so, probably affected the detection that ran at 12:14pm.. where the
'new' SusClientID was probably obtained for use at the next detection
cycle -- but there could have been yet another (undetermined) reason why the
detection did not succeed on 8/29 at 12:14pm.

2005-08-29 12:14:44 1052 f4 AU #############
2005-08-29 12:14:44 1052 f4 AU ## START ## AU: Search for updates
2005-08-29 12:14:44 1052 f4 AU #########

2005-08-29 12:14:48 1052 554 PT Initializing simple targeting cookie,
clientId = 9823efc8-5d7f-43a4-94f1-0869a93a9ad6,
target group = ME Laptops,
DNS name = pc176.moxy.no

2005-08-29 12:14:57 1052 554 Agent * Found 0 updates and 5 categories
in search

2005-08-29 12:14:58 1052 554 AU #########
2005-08-29 12:14:58 1052 554 AU ## END ## AU: Search for updates
2005-08-29 12:14:58 1052 554 AU #############
2005-08-29 12:14:58 1052 554 AU AU setting next detection timeout to
2005-08-29 14:54:23

2005-08-29 12:28:43 1052 5e0 Report Reporter successfully uploaded 2
events.

It was also complicated because the next scheduled detection, which would
have occurred at 16:54 local time, did not run because the system was
powered down at 16:01pm:

2005-08-29 16:01:27 1052 c7c AU AU found 0 updates for install at
shutdown
2005-08-29 16:02:26 1052 c7c AU AU Restart required....
2005-08-29 16:02:30 1052 f4 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-29 16:02:30 1052 f4 AU # WSUS server: http://moxy-tst
2005-08-29 16:02:30 1052 f4 AU # Detection frequency: 5
2005-08-29 16:02:30 1052 f4 AU # Target group: ME Laptops
2005-08-29 16:02:30 1052 f4 AU # Approval type: Scheduled (Policy)
2005-08-29 16:02:30 1052 f4 AU # Scheduled install day/time: Every
day at 11:00
2005-08-29 16:02:30 1052 f4 AU # Auto-install minor updates: Yes
(Policy)
2005-08-29 16:02:30 1052 f4 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-29 16:02:30 1052 f4 AU # AU is paused, not initializing any
handlers
2005-08-29 16:02:30 1052 f4 AU # WARNING: Exit code = 0x80004015
2005-08-29 16:02:30 1052 f4 AU AU Restart required....
2005-08-29 16:02:30 1052 f4 Service *********
2005-08-29 16:02:30 1052 f4 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2005-08-29 16:02:30 1052 f4 Service *************

Which suggests that I should add a forced /detectnow to my procedure, to be
run 5-10 minutes after the Automatic Updates service is restarted. It would
appear that the initial detection, not having a SusClientID, merely obtains
one, and does not actually succeed at detecting any updates. A subsequent
detection, with the SusClientID available, would be necessary to detect new
updates. In your case, it didn't actually run until 8:00am the next
morning - but could have been forced as early as 11:00am the previous day.
Post by Trond Mahle
Hello Lawrence,
Today I have some good news for you - everything is now OK!! At 11:00 AM
this morning the last 8 'Needed' patches installed themselves without me
doing anything. Actually I was preparing a manual installation of them, but
luckily I was disturbed and the clock passed the time for WSUS
installation
set in GPO.... I was noticed by the user that had got a question about reboot
on his screen.
So your previous solution worked (point 1-7), it only took some time! I
e-mail you the last version of the 2 log-files if you are interested to take
a final look at them. Thanks a lot for your patience and help!!
Best regards Trond :-)))
Post by Lawrence Garvin
I got your email... reviewed the results.
I have two possibilities.
Either another system is reporting with the same SusClientID (not likely
since this system was rebuilt from scratch)
or the database on the WSUS server has corrupted data that is reappearing on
the console.
The other thing you should do is inspect the IIS Logs and find out /what/
reported to the WSUS server between the time the new system reported
originally, and the time the '8 updates needed' appeared on the WSUS server.
I think the WUA is accurate in it assessment, those updates are not needed.
As I recall, some of those updates were contingent upon software being
installed, and a couple of them are actually superceded by newer
(installed??) updates.
There are definitely possibilities that things are being 'misreported' since
you actually did the updates from windowsupdate.com, and then directed the
system to the WSUS server. (Side note: see
http://wsusinfo.onsitechsolutions.com/articles/012.htm and 010.htm for some
insight on how you can use your WSUS server to fully update new systems,
totally unattended, in less time than it takes you to do them from
WindowsUpdate.com interactively. Doing so may also help stablize your
reporting to WSUS.)
This can also be an unanticipated side-effect of mixing and matching
client-side targeting with server-side targeting.
It could even be that the cumulative combination of all of these unique
conditions is causing some conflict in reporting.
It seems to me that the /best/ option for further testing at this point
(1) Shutdown the notebook.
(2) Remove the computer from the WSUS Server (make sure you choose the
option to completely remove the data, not just move the computer to
Unassigned Computers). Note: In general, when systems are known to be
rebuilt, I think it would be a good idea to purge the old system from the
WSUS server /before/ putting the new system online if the same machine name
is going to be used.
(3) Install the OS from media and then /update/ the system exclusively from
WSUS.
Post by Trond Mahle
Hello Lawrence,
I've now followed your proposal below in detail (1-7) without success. The
WSUS Console still report the same 8 updates as Needed! I e-mail you a report
showing you the procedure we followed and the result.
Meanwhile we had to re-install another desktop in the same way as this
"problem laptop", and that went very well. The only difference between
the
2
1. The laptop got WXP without SP from its restore CD, and was then patched
to WXP SP2 from windowsupdate.microsoft.com. The desktop got WXP SP2 directly
from a CD.
2. The laptop belongs to our WSUS group "ME Laptops". The desktop
belongs
to
our WSUS group "ME Desktops".
I suspect the problem is related to how WXP was re-installed on the 2 PCs
(point 1) because our two WSUS groups have been built/used in the same way.
Should I only try to install the updates manually on the laptop to get
rid
of
this problem, or do you have another proposal? Hopefully this is a disposable
case.....
Post by Lawrence Garvin
I received your email and attachements.
I'm letting go of the 'target group' consideration.... the client
appears
to
have been consistently a member of that group, and your screenshot of the
WSUS server shows those updates as approved for installation for that target
group.
What's problematic with this scenario is that the client has /never/
detected those eight updates, and still isn't detecting them. I suspect
there is corrupted data somewhere -- perhaps the datastore.edb on the
client, perhaps the data in the susdb.mdf on the server, perhaps both, even.
The updates should not be showing as "Needed" on the server because the
client has never detected, and thus never reported 'events' for that
detection. Whether the updates /should/ be detected at this point is really
a secondary issue. The client is not detecting them, and the data, as
reported on the WSUS server, is incorrect.
What I think happened. but I don't exactly understand how, is that
/something/ caused this client's record to be updated with these detections.
Maybe this is fallout from a duplicate SusClientID?
The questions we have at the moment: Are the updates actually
installed?
Are
they even required -- as noted, /some/ of the updates may, in fact, be N/A.
Here's what I would suggest as a "fix" for the whole situation -- it's a
radical fix, but I believe it will clean house - so to speak.
1. At the client, shutdown Automatic Updates service.
2. At the client, use bitsadmin to check the BITS queue, and flush it if
there's anything there.
3. At the client, make a backup of the %windir%\SoftwareDistribution folder
and all subfolders
and the %windir%\WindowsUpdate.log file.
%windir%\SoftwareDistribution\Datastore\Logs\edb*.*
%windir%\SoftwareDistribution\Datastore\DataStore.edb
%windir%\SoftwareDistribution\Download
%windir%\SoftwareDistribution\EventCache
%windir%\SoftwareDistribution\ReportingEvents.log
%windir%\WindowsUpdate.log
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new SusClientId, which
will force the creation of an all new database record (thus avoiding any
potential issues with corruption or bad data in the original record, that
may or may not actually be physically present in the database).
6. At the server, delete pc176.moxy.no from the WSUS server, completely.
7. At the client, restart the Automatic Updates service, and monitor the
WindowsUpdate.log and/or ReportingEvents.log for detection/download activity
for these eight updates. Following the detection and the uploading of events
to the ReportingWebService, review the status as reported by the WSUS
server, to determine if the new instance of this client appears and is
reported correctly with regard to installed and needed updates.
Post by Trond Mahle
Thanks, but I'm not sure if I totally agree with your conclusion. The
way
we
use target groups has definitive worked the last 1/2 year for all
other
WSUS
clients in our network (servers, desktops, laptops). It's configured "after
the book" in our GPO Editor, the only difference is that we move the clients
manually from "Unassigned Computers" to their appropriate group in
WSUS
Admin
(with exactly the same group name as used in GPO Editor).
The special in this case was that the laptop already existed in our WSUS
group "ME Laptops" when it got a new blank harddisk which was
configured
like
1. WXP installed from recovery CD following the laptop.
2. Connected direct to a brodband line logged in as local
Administrator
and
manually patched from windowsupdate.microsoft.com until WXP SP2 had been
installed (no more updates afterwards).
3. Connected to our LAN/domain to complete the rest of the WXP
configuration, installing applications etc.
When I came back from holiday 08.08.2005 I found the laptop both in
the
WSUS
group "Unassigned Computers" (new entry with a long list of updates
"Needed"), and in our WSUS group "ME Laptops" (old entry with an exclamation
mark in front of it indicating no contact last week).
4. I then deleted the old entry end moved the new entry into our
WSUS
group
"ME Laptops" where all needed updates for laptops with WXP SP1/SP2
have
been
approved since we started with WUS in february 2005. I'm not sure exactly
what day I moved it, but it must have been between 8th-10th of August.
5. All updates except for the 8 remaining were then installed on the laptop
during the next days (11th-12th ?).
6. Almost at the same time, 10th of August 09:54 AM CEST, I successfully
synchronized the server with Microsoft because they had relased new August
patches. Afterwards all new August WXP SP2 updates were approved for WSUS
group "ME Laptops".
- Screendump of WSUS Admin showing the problem.
- Complete WindowsUpdate.log from the client.
- Complete ReportingEvents.log from the client.
Hope we come to a conclusion soon! :-))
Best regards Trond
-----------------------------------------------------------------------------------------------
Post by Lawrence Garvin
Prior to 8/11, it appears that ALL updates applied to this system were
obtained via Windows Update. On the morning of 8/11, Automatic Updates
downloaded these updates, and scheduled them for installation at 11:00am
2005-08-11 07:55:38+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security
Update
for
Windows XP (KB896428) - Cumulative Security Update for Internet
Explorer
for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security
Update
for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for
Windows
XP
(KB885250) - Security Update for Windows XP (KB885836) - Security
Update
for
Windows XP (KB896422)
The installation was successful, and the system restarted.
Then, on the morning of 8/12, these updates were detected and
downloaded
and
scheduled for installation on 8/12 at 11am.
2005-08-12 07:54:25+0200
The following updates are downloaded and ready for installation.
This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for
Windows
XP
(KB899591) - Security Update for Windows XP (KB899587)
The installation was successful, and the system restarted.
No other updates were ever detected for installation, although the
detections continued to run twice daily.
A question to be asked, for sure, is what was the configuration of the
system on 8/11 and 8/12.
I suspect it has to do with how you're configuring and using target groups.
Part of this may be answered by the WindowsUpdate.log, so now I'm
going
to
ask you to email me the WindowsUpdate.log for 8/11 and 8/12.
Please remove the "nospam" subdomain prefix from my email address
to
get
it to me.
Post by Trond Mahle
(Emailing this file to you failed, so I try to post only this again)
************************************************************
Trond Mahle
2005-08-31 06:55:39 UTC
Permalink
I want to add this missing point that you mention to my own procedure too:
"... Which suggests that I should add a forced /detectnow to my procedure,
to be
run 5-10 minutes after the Automatic Updates service is restarted."
This will be item 8 in your solution, how will you formulate it in detail
for a "novice"?
Post by Lawrence Garvin
I saw that in your email.
I also saw /NO/ activity in the WindowsUpdate.log file from 8/29 at noon
(when -0- updates were detected) until the next morning when amazingly, the
client detected the remaining updatse.
I'm glad it worked out... but I'm still curious (and confused).. about why
that client did not detect the updates the previous day.
One thing I did notice, following your clean up of the client...
These five log lines did not appear in any transactions on 8/29, but first
appeared at 8/30, when the detection successfully completed. I'm thinking
there may have been an issue on 8/29 with a missing SusClientId...
2005-08-30 08:10:55 1048 10c Agent * WU client version 5.8.0.2469
2005-08-30 08:10:55 1048 10c Agent * SusClientId =
'9823efc8-5d7f-43a4-94f1-0869a93a9ad6'
C:\Windows\SoftwareDistribution
2005-08-30 08:10:55 1048 10c Agent * Access type: No proxy
2005-08-30 08:10:55 1048 10c Agent * Network state: Connected
2005-08-29 10:46:11 1044 ec0 Agent * WU client version 5.8.0.2469
2005-08-29 10:46:11 1044 ec0 Agent * WARNING: Failed to obtain
SusClientId
C:\Windows\SoftwareDistribution
2005-08-29 10:46:11 1044 ec0 Agent * Access type: No proxy
2005-08-29 10:46:11 1044 ec0 Agent * Network state: Connected
and, so, probably affected the detection that ran at 12:14pm.. where the
'new' SusClientID was probably obtained for use at the next detection
cycle -- but there could have been yet another (undetermined) reason why the
detection did not succeed on 8/29 at 12:14pm.
2005-08-29 12:14:44 1052 f4 AU #############
2005-08-29 12:14:44 1052 f4 AU ## START ## AU: Search for updates
2005-08-29 12:14:44 1052 f4 AU #########
2005-08-29 12:14:48 1052 554 PT Initializing simple targeting cookie,
clientId = 9823efc8-5d7f-43a4-94f1-0869a93a9ad6,
target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-29 12:14:57 1052 554 Agent * Found 0 updates and 5 categories
in search
2005-08-29 12:14:58 1052 554 AU #########
2005-08-29 12:14:58 1052 554 AU ## END ## AU: Search for updates
2005-08-29 12:14:58 1052 554 AU #############
2005-08-29 12:14:58 1052 554 AU AU setting next detection timeout to
2005-08-29 14:54:23
2005-08-29 12:28:43 1052 5e0 Report Reporter successfully uploaded 2
events.
It was also complicated because the next scheduled detection, which would
have occurred at 16:54 local time, did not run because the system was
2005-08-29 16:01:27 1052 c7c AU AU found 0 updates for install at
shutdown
2005-08-29 16:02:26 1052 c7c AU AU Restart required....
2005-08-29 16:02:30 1052 f4 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-29 16:02:30 1052 f4 AU # WSUS server: http://moxy-tst
2005-08-29 16:02:30 1052 f4 AU # Detection frequency: 5
2005-08-29 16:02:30 1052 f4 AU # Target group: ME Laptops
2005-08-29 16:02:30 1052 f4 AU # Approval type: Scheduled (Policy)
2005-08-29 16:02:30 1052 f4 AU # Scheduled install day/time: Every
day at 11:00
2005-08-29 16:02:30 1052 f4 AU # Auto-install minor updates: Yes
(Policy)
2005-08-29 16:02:30 1052 f4 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-29 16:02:30 1052 f4 AU # AU is paused, not initializing any
handlers
2005-08-29 16:02:30 1052 f4 AU # WARNING: Exit code = 0x80004015
2005-08-29 16:02:30 1052 f4 AU AU Restart required....
2005-08-29 16:02:30 1052 f4 Service *********
2005-08-29 16:02:30 1052 f4 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2005-08-29 16:02:30 1052 f4 Service *************
Which suggests that I should add a forced /detectnow to my procedure, to be
run 5-10 minutes after the Automatic Updates service is restarted. It would
appear that the initial detection, not having a SusClientID, merely obtains
one, and does not actually succeed at detecting any updates. A subsequent
detection, with the SusClientID available, would be necessary to detect new
updates. In your case, it didn't actually run until 8:00am the next
morning - but could have been forced as early as 11:00am the previous day.
Post by Trond Mahle
Hello Lawrence,
Today I have some good news for you - everything is now OK!! At 11:00 AM
this morning the last 8 'Needed' patches installed themselves without me
doing anything. Actually I was preparing a manual installation of them, but
luckily I was disturbed and the clock passed the time for WSUS installation
set in GPO.... I was noticed by the user that had got a question about reboot
on his screen.
So your previous solution worked (point 1-7), it only took some time! I
e-mail you the last version of the 2 log-files if you are interested to take
a final look at them. Thanks a lot for your patience and help!!
Best regards Trond :-)))
Post by Lawrence Garvin
I got your email... reviewed the results.
I have two possibilities.
Either another system is reporting with the same SusClientID (not likely
since this system was rebuilt from scratch)
or the database on the WSUS server has corrupted data that is reappearing on
the console.
The other thing you should do is inspect the IIS Logs and find out /what/
reported to the WSUS server between the time the new system reported
originally, and the time the '8 updates needed' appeared on the WSUS server.
I think the WUA is accurate in it assessment, those updates are not needed.
As I recall, some of those updates were contingent upon software being
installed, and a couple of them are actually superceded by newer
(installed??) updates.
There are definitely possibilities that things are being 'misreported' since
you actually did the updates from windowsupdate.com, and then directed the
system to the WSUS server. (Side note: see
http://wsusinfo.onsitechsolutions.com/articles/012.htm and 010.htm for some
insight on how you can use your WSUS server to fully update new systems,
totally unattended, in less time than it takes you to do them from
WindowsUpdate.com interactively. Doing so may also help stablize your
reporting to WSUS.)
This can also be an unanticipated side-effect of mixing and matching
client-side targeting with server-side targeting.
It could even be that the cumulative combination of all of these unique
conditions is causing some conflict in reporting.
It seems to me that the /best/ option for further testing at this point
(1) Shutdown the notebook.
(2) Remove the computer from the WSUS Server (make sure you choose the
option to completely remove the data, not just move the computer to
Unassigned Computers). Note: In general, when systems are known to be
rebuilt, I think it would be a good idea to purge the old system from the
WSUS server /before/ putting the new system online if the same machine name
is going to be used.
(3) Install the OS from media and then /update/ the system exclusively from
WSUS.
Post by Trond Mahle
Hello Lawrence,
I've now followed your proposal below in detail (1-7) without success. The
WSUS Console still report the same 8 updates as Needed! I e-mail you a report
showing you the procedure we followed and the result.
Meanwhile we had to re-install another desktop in the same way as this
"problem laptop", and that went very well. The only difference between
the
2
1. The laptop got WXP without SP from its restore CD, and was then patched
to WXP SP2 from windowsupdate.microsoft.com. The desktop got WXP SP2 directly
from a CD.
2. The laptop belongs to our WSUS group "ME Laptops". The desktop
belongs
to
our WSUS group "ME Desktops".
I suspect the problem is related to how WXP was re-installed on the 2 PCs
(point 1) because our two WSUS groups have been built/used in the same way.
Should I only try to install the updates manually on the laptop to get
rid
of
this problem, or do you have another proposal? Hopefully this is a disposable
case.....
Post by Lawrence Garvin
I received your email and attachements.
I'm letting go of the 'target group' consideration.... the client
appears
to
have been consistently a member of that group, and your screenshot of the
WSUS server shows those updates as approved for installation for that target
group.
What's problematic with this scenario is that the client has /never/
detected those eight updates, and still isn't detecting them. I suspect
there is corrupted data somewhere -- perhaps the datastore.edb on the
client, perhaps the data in the susdb.mdf on the server, perhaps both, even.
The updates should not be showing as "Needed" on the server because the
client has never detected, and thus never reported 'events' for that
detection. Whether the updates /should/ be detected at this point is really
a secondary issue. The client is not detecting them, and the data, as
reported on the WSUS server, is incorrect.
What I think happened. but I don't exactly understand how, is that
/something/ caused this client's record to be updated with these detections.
Maybe this is fallout from a duplicate SusClientID?
The questions we have at the moment: Are the updates actually
installed?
Are
they even required -- as noted, /some/ of the updates may, in fact, be N/A.
Here's what I would suggest as a "fix" for the whole situation -- it's a
radical fix, but I believe it will clean house - so to speak.
1. At the client, shutdown Automatic Updates service.
2. At the client, use bitsadmin to check the BITS queue, and flush it if
there's anything there.
3. At the client, make a backup of the %windir%\SoftwareDistribution folder
and all subfolders
and the %windir%\WindowsUpdate.log file.
%windir%\SoftwareDistribution\Datastore\Logs\edb*.*
%windir%\SoftwareDistribution\Datastore\DataStore.edb
%windir%\SoftwareDistribution\Download
%windir%\SoftwareDistribution\EventCache
%windir%\SoftwareDistribution\ReportingEvents.log
%windir%\WindowsUpdate.log
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new SusClientId, which
will force the creation of an all new database record (thus avoiding any
potential issues with corruption or bad data in the original record, that
may or may not actually be physically present in the database).
6. At the server, delete pc176.moxy.no from the WSUS server, completely.
7. At the client, restart the Automatic Updates service, and monitor the
WindowsUpdate.log and/or ReportingEvents.log for detection/download activity
for these eight updates. Following the detection and the uploading of events
to the ReportingWebService, review the status as reported by the WSUS
server, to determine if the new instance of this client appears and is
reported correctly with regard to installed and needed updates.
Post by Trond Mahle
Thanks, but I'm not sure if I totally agree with your conclusion. The
Lawrence Garvin
2005-08-31 14:20:43 UTC
Permalink
8. If the client does not appear on the WSUS server, or does not detect
updates known to be available, execute 'wuauclt /detectnow'.
Post by Trond Mahle
"... Which suggests that I should add a forced /detectnow to my procedure,
to be
run 5-10 minutes after the Automatic Updates service is restarted."
This will be item 8 in your solution, how will you formulate it in detail
for a "novice"?
Post by Lawrence Garvin
I saw that in your email.
I also saw /NO/ activity in the WindowsUpdate.log file from 8/29 at noon
(when -0- updates were detected) until the next morning when amazingly, the
client detected the remaining updatse.
I'm glad it worked out... but I'm still curious (and confused).. about why
that client did not detect the updates the previous day.
One thing I did notice, following your clean up of the client...
These five log lines did not appear in any transactions on 8/29, but first
appeared at 8/30, when the detection successfully completed. I'm thinking
there may have been an issue on 8/29 with a missing SusClientId...
2005-08-30 08:10:55 1048 10c Agent * WU client version 5.8.0.2469
2005-08-30 08:10:55 1048 10c Agent * SusClientId =
'9823efc8-5d7f-43a4-94f1-0869a93a9ad6'
C:\Windows\SoftwareDistribution
2005-08-30 08:10:55 1048 10c Agent * Access type: No proxy
2005-08-30 08:10:55 1048 10c Agent * Network state: Connected
2005-08-29 10:46:11 1044 ec0 Agent * WU client version 5.8.0.2469
2005-08-29 10:46:11 1044 ec0 Agent * WARNING: Failed to obtain
SusClientId
C:\Windows\SoftwareDistribution
2005-08-29 10:46:11 1044 ec0 Agent * Access type: No proxy
2005-08-29 10:46:11 1044 ec0 Agent * Network state: Connected
and, so, probably affected the detection that ran at 12:14pm.. where the
'new' SusClientID was probably obtained for use at the next detection
cycle -- but there could have been yet another (undetermined) reason why the
detection did not succeed on 8/29 at 12:14pm.
2005-08-29 12:14:44 1052 f4 AU #############
2005-08-29 12:14:44 1052 f4 AU ## START ## AU: Search for updates
2005-08-29 12:14:44 1052 f4 AU #########
2005-08-29 12:14:48 1052 554 PT Initializing simple targeting cookie,
clientId = 9823efc8-5d7f-43a4-94f1-0869a93a9ad6,
target group = ME Laptops,
DNS name = pc176.moxy.no
2005-08-29 12:14:57 1052 554 Agent * Found 0 updates and 5 categories
in search
2005-08-29 12:14:58 1052 554 AU #########
2005-08-29 12:14:58 1052 554 AU ## END ## AU: Search for updates
2005-08-29 12:14:58 1052 554 AU #############
2005-08-29 12:14:58 1052 554 AU AU setting next detection timeout to
2005-08-29 14:54:23
2005-08-29 12:28:43 1052 5e0 Report Reporter successfully uploaded 2
events.
It was also complicated because the next scheduled detection, which would
have occurred at 16:54 local time, did not run because the system was
2005-08-29 16:01:27 1052 c7c AU AU found 0 updates for install at
shutdown
2005-08-29 16:02:26 1052 c7c AU AU Restart required....
2005-08-29 16:02:30 1052 f4 AU ########### AU: Initializing Automatic
Updates ###########
2005-08-29 16:02:30 1052 f4 AU # WSUS server: http://moxy-tst
2005-08-29 16:02:30 1052 f4 AU # Detection frequency: 5
2005-08-29 16:02:30 1052 f4 AU # Target group: ME Laptops
2005-08-29 16:02:30 1052 f4 AU # Approval type: Scheduled (Policy)
2005-08-29 16:02:30 1052 f4 AU # Scheduled install day/time: Every
day at 11:00
2005-08-29 16:02:30 1052 f4 AU # Auto-install minor updates: Yes
(Policy)
2005-08-29 16:02:30 1052 f4 AU # Will interact with non-admins
(Non-admins are elevated)
2005-08-29 16:02:30 1052 f4 AU # AU is paused, not initializing any
handlers
2005-08-29 16:02:30 1052 f4 AU # WARNING: Exit code = 0x80004015
2005-08-29 16:02:30 1052 f4 AU AU Restart required....
2005-08-29 16:02:30 1052 f4 Service *********
2005-08-29 16:02:30 1052 f4 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2005-08-29 16:02:30 1052 f4 Service *************
Which suggests that I should add a forced /detectnow to my procedure, to be
run 5-10 minutes after the Automatic Updates service is restarted. It would
appear that the initial detection, not having a SusClientID, merely obtains
one, and does not actually succeed at detecting any updates. A subsequent
detection, with the SusClientID available, would be necessary to detect new
updates. In your case, it didn't actually run until 8:00am the next
morning - but could have been forced as early as 11:00am the previous day.
Post by Trond Mahle
Hello Lawrence,
Today I have some good news for you - everything is now OK!! At 11:00 AM
this morning the last 8 'Needed' patches installed themselves without me
doing anything. Actually I was preparing a manual installation of them, but
luckily I was disturbed and the clock passed the time for WSUS installation
set in GPO.... I was noticed by the user that had got a question about reboot
on his screen.
So your previous solution worked (point 1-7), it only took some time!
I
e-mail you the last version of the 2 log-files if you are interested to take
a final look at them. Thanks a lot for your patience and help!!
Best regards Trond :-)))
Post by Lawrence Garvin
I got your email... reviewed the results.
I have two possibilities.
Either another system is reporting with the same SusClientID (not likely
since this system was rebuilt from scratch)
or the database on the WSUS server has corrupted data that is
reappearing
on
the console.
The other thing you should do is inspect the IIS Logs and find out /what/
reported to the WSUS server between the time the new system reported
originally, and the time the '8 updates needed' appeared on the WSUS server.
I think the WUA is accurate in it assessment, those updates are not needed.
As I recall, some of those updates were contingent upon software being
installed, and a couple of them are actually superceded by newer
(installed??) updates.
There are definitely possibilities that things are being 'misreported' since
you actually did the updates from windowsupdate.com, and then directed the
system to the WSUS server. (Side note: see
http://wsusinfo.onsitechsolutions.com/articles/012.htm and 010.htm for some
insight on how you can use your WSUS server to fully update new systems,
totally unattended, in less time than it takes you to do them from
WindowsUpdate.com interactively. Doing so may also help stablize your
reporting to WSUS.)
This can also be an unanticipated side-effect of mixing and matching
client-side targeting with server-side targeting.
It could even be that the cumulative combination of all of these unique
conditions is causing some conflict in reporting.
It seems to me that the /best/ option for further testing at this point
(1) Shutdown the notebook.
(2) Remove the computer from the WSUS Server (make sure you choose the
option to completely remove the data, not just move the computer to
Unassigned Computers). Note: In general, when systems are known to be
rebuilt, I think it would be a good idea to purge the old system from the
WSUS server /before/ putting the new system online if the same machine name
is going to be used.
(3) Install the OS from media and then /update/ the system exclusively from
WSUS.
Post by Trond Mahle
Hello Lawrence,
I've now followed your proposal below in detail (1-7) without
success.
The
WSUS Console still report the same 8 updates as Needed! I e-mail you
a
report
showing you the procedure we followed and the result.
Meanwhile we had to re-install another desktop in the same way as this
"problem laptop", and that went very well. The only difference between
the
2
1. The laptop got WXP without SP from its restore CD, and was then patched
to WXP SP2 from windowsupdate.microsoft.com. The desktop got WXP SP2 directly
from a CD.
2. The laptop belongs to our WSUS group "ME Laptops". The desktop
belongs
to
our WSUS group "ME Desktops".
I suspect the problem is related to how WXP was re-installed on the
2
PCs
(point 1) because our two WSUS groups have been built/used in the
same
way.
Should I only try to install the updates manually on the laptop to get
rid
of
this problem, or do you have another proposal? Hopefully this is a disposable
case.....
Post by Lawrence Garvin
I received your email and attachements.
I'm letting go of the 'target group' consideration.... the client
appears
to
have been consistently a member of that group, and your screenshot
of
the
WSUS server shows those updates as approved for installation for
that
target
group.
What's problematic with this scenario is that the client has /never/
detected those eight updates, and still isn't detecting them. I suspect
there is corrupted data somewhere -- perhaps the datastore.edb on the
client, perhaps the data in the susdb.mdf on the server, perhaps
both,
even.
The updates should not be showing as "Needed" on the server because the
client has never detected, and thus never reported 'events' for that
detection. Whether the updates /should/ be detected at this point
is
really
a secondary issue. The client is not detecting them, and the data, as
reported on the WSUS server, is incorrect.
What I think happened. but I don't exactly understand how, is that
/something/ caused this client's record to be updated with these detections.
Maybe this is fallout from a duplicate SusClientID?
The questions we have at the moment: Are the updates actually
installed?
Are
they even required -- as noted, /some/ of the updates may, in fact,
be
N/A.
Here's what I would suggest as a "fix" for the whole situation --
it's
a
radical fix, but I believe it will clean house - so to speak.
1. At the client, shutdown Automatic Updates service.
2. At the client, use bitsadmin to check the BITS queue, and flush
it
if
there's anything there.
3. At the client, make a backup of the
%windir%\SoftwareDistribution
folder
and all subfolders
and the %windir%\WindowsUpdate.log file.
%windir%\SoftwareDistribution\Datastore\Logs\edb*.*
%windir%\SoftwareDistribution\Datastore\DataStore.edb
%windir%\SoftwareDistribution\Download
%windir%\SoftwareDistribution\EventCache
%windir%\SoftwareDistribution\ReportingEvents.log
%windir%\WindowsUpdate.log
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new
SusClientId,
which
will force the creation of an all new database record (thus
avoiding
any
potential issues with corruption or bad data in the original
record,
that
may or may not actually be physically present in the database).
6. At the server, delete pc176.moxy.no from the WSUS server, completely.
7. At the client, restart the Automatic Updates service, and
monitor
the
WindowsUpdate.log and/or ReportingEvents.log for detection/download activity
for these eight updates. Following the detection and the uploading
of
events
to the ReportingWebService, review the status as reported by the WSUS
server, to determine if the new instance of this client appears and is
reported correctly with regard to installed and needed updates.
Post by Trond Mahle
Thanks, but I'm not sure if I totally agree with your conclusion. The
George
2006-10-03 10:48:01 UTC
Permalink
hello,
i have a problem with the WSUS, it still shows : 'One or more Update
Service components could not be contacted. Check your server status and
ensure that the Windows Server Update Service is running. Non-running
services: SelfUpdate'
and for the last 3 weeks no client has received any updates, although in the
wsus shows that are needed and have been approved.
can anyone help?
thank you in advance
Winfried Sonntag [MVP]
2006-10-03 12:39:24 UTC
Permalink
Post by George
i have a problem with the WSUS, it still shows : 'One or more Update
Service components could not be contacted. Check your server status and
ensure that the Windows Server Update Service is running. Non-running
services: SelfUpdate'
and for the last 3 weeks no client has received any updates, although in the
wsus shows that are needed and have been approved.
can anyone help?
http://msmvps.com/blogs/athif/articles/67954.aspx

Winfried
--
http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx
http://www.wsuswiki.com/Home
Trond Mahle
2005-08-23 11:23:04 UTC
Permalink
************************************************************
ReportingEvents.log (part 2)
************************************************************
{78774A57-D19E-4ABD-BF80-BF2A559BA87D} 2005-08-11
07:55:44+0200 1 162 101 {9306CDFC-C4A1-4A22-9996-848CB67EDDC3} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{A4BAB1C5-1743-4EA5-807A-4C2EE2BC0CE0} 2005-08-11
07:55:44+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Thursday, August 11, 2005 at 11:00 AM: - Security Update for
Windows XP (KB896428) - Cumulative Security Update for Internet Explorer for
Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836) - Security Update for
Windows XP (KB896422)
{99C7C6C3-BCB4-4B97-BCE4-17A242378AC9} 2005-08-11
11:00:29+0200 1 190 101 {5BC6E116-9964-4452-AE5A-C54BD709BC53} 100 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following
update: Security Update for Windows XP (KB896428)
{3E7386B4-6C42-44B1-BE83-75369245EA85} 2005-08-11
11:00:44+0200 1 191 101 {A2D28A3A-34AD-4044-A890-3231305FCF5F} 50 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Cumulative Security Update for Internet Explorer for Windows XP
Service Pack 2 (KB890923)
{45941841-58F0-466F-82D4-E835799771FE} 2005-08-11
11:00:50+0200 1 191 101 {9A127D52-45FA-44BA-ACC5-5EA9A637FE4E} 10 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB888302)
{09931D0F-B3C9-49E7-9640-CFE550AB9743} 2005-08-11
11:00:56+0200 1 190 101 {1E59F963-12F5-4BFD-A73D-366921779C28} 102 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following
update: Security Update for Windows XP (KB901214)
{FCB95FF9-2DE7-421B-8ED4-5B30CF4B32AC} 2005-08-11
11:01:02+0200 1 191 101 {4324AC78-FDB4-42DE-BEDF-769A40627897} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB893066)
{BB208260-2C9A-448B-A1FA-1C50B4E6F482} 2005-08-11
11:01:09+0200 1 191 101 {4CDB577B-FDD1-49D4-87CC-3808AD20ACBC} 101 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB890046)
{E400849F-565F-4DD1-A365-F7625992BD15} 2005-08-11
11:01:15+0200 1 190 101 {4B689082-CA9C-46CC-B2FC-720FEDE21299} 10 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following
update: Security Update for Windows XP (KB891781)
{9F4B33E9-AE23-4D14-B8F2-B7A3479B8A6D} 2005-08-11
11:01:21+0200 1 190 101 {3A7EFDB0-D88D-42A6-8439-C7D0B1BCAC82} 10 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following
update: Security Update for Windows XP (KB888113)
{5B2E0F63-145F-472B-BF12-F90964299938} 2005-08-11
11:01:27+0200 1 190 101 {E45B26C2-278F-48F3-97D1-AA0FD57423D5} 10 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following
update: Security Update for Windows XP (KB873339)
{102632D5-E27B-496A-9849-957AB84F405F} 2005-08-11
11:01:34+0200 1 191 101 {B20C7AC9-F972-480C-9601-DE0486342506} 11 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB885250)
{A8EA2614-1B4B-4F6B-ACFF-AA089054A23E} 2005-08-11
11:01:40+0200 1 190 101 {BBE805EE-2CF7-4110-9BE8-4FE32B144E5A} 10 0 AutomaticUpdates Success Content
Install Installation Successful: Windows successfully installed the following
update: Security Update for Windows XP (KB885836)
{65F2134C-A1A6-465B-B6BE-0232DF079A1E} 2005-08-11
11:01:46+0200 1 191 101 {9306CDFC-C4A1-4A22-9996-848CB67EDDC3} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB896422)
{7AC850AA-50B0-439C-956F-5B801352B06E} 2005-08-11
11:01:46+0200 1 194 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Restart Required: To complete the installation of the following
updates, the computer will be restarted within 25 minutes: - Security Update
for Windows XP (KB896428) - Cumulative Security Update for Internet Explorer
for Windows XP Service Pack 2 (KB890923) - Security Update for Windows XP
(KB888302) - Security Update for Windows XP (KB901214) - Security Update for
Windows XP (KB893066) - Security Update for Windows XP (KB890046) - Security
Update for Windows XP (KB891781) - Security Update for Windows XP (KB888113)
- Security Update for Windows XP (KB873339) - Security Update for Windows XP
(KB885250) - Security Update for Windows XP (KB885836) - Security Update for
Windows XP (KB896422)
{541F7DB5-4817-49EA-9199-77B8939A5191} 2005-08-11
11:04:21+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{D879AB20-B23E-49EE-A511-92AF759DAF9C} 2005-08-11
12:22:22+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{6A2A938A-04BF-4883-B149-FF085475FCE8} 2005-08-11
12:22:22+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{C5651102-9013-4AA2-9FA5-AD4C4B7A3DAA} 2005-08-11
12:24:46+0200 1 162 101 {DD167F04-69E8-46A0-83DA-D4A5143EDBF1} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{E4F93B12-4798-4B2A-B30B-42CF3C7FD7FA} 2005-08-11
12:24:46+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859)
{050E93F0-9A6A-4E63-BF17-58E030F8903A} 2005-08-11
12:25:37+0200 1 162 101 {06F7520C-2CF3-46AB-A457-402327016632} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{E343565F-4CAE-4CA1-BC03-448A11C72DA0} 2005-08-11
12:25:37+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391)
{007DFC97-40FD-4DE2-B988-481EB7077C59} 2005-08-11
12:25:42+0200 1 162 101 {4BD8393B-9142-444D-BD40-B74172F48B86} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{F7B5B32B-B09E-404A-A481-C3610BF59F57} 2005-08-11
12:25:42+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588)
{DB409E2C-17A5-4C98-99C6-E7156F1A4C3A} 2005-08-11
12:26:39+0200 1 162 101 {76A9ECC1-0AC2-4F09-8BAF-4FC5F68EEA0C} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{FD9F8DCC-66A6-431C-9644-8B9A89F26E98} 2005-08-11
12:26:39+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727)
{24BFFF06-FEF9-4158-9193-D9FF8226B28F} 2005-08-11
12:26:41+0200 1 162 101 {70E702CB-5D44-494D-8594-476AC774CD51} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{5DCCDB8B-2E22-484D-9DFA-74EBBAC64A51} 2005-08-11
12:26:41+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423)
{1C7A48EF-35F7-4FB1-81A7-1193EDD07A3C} 2005-08-11
12:26:49+0200 1 162 101 {D80D91CF-6361-4FDF-B35D-F05077902973} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{F9461343-514E-4A4F-897C-6F9DD59E1E1E} 2005-08-11
12:26:49+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756)
{BBB9E00C-1A45-4814-B345-CECAF4711F96} 2005-08-11
12:26:55+0200 1 162 101 {2FCDEFD7-B98F-4A25-8DF4-F8060AFC0942} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{6A760186-0038-4387-983F-231B99BB0BB9} 2005-08-11
12:26:55+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for Windows XP
(KB899591)
{691071F3-622B-41FC-81A0-DF755366C720} 2005-08-11
12:27:38+0200 1 162 101 {1AFB1AFE-9AAF-4DC4-9DAC-C75303A84655} 100 0 AutomaticUpdates Success Content Download Download succeeded.
{B3A2664C-6B53-463E-8A11-DAB313B4C11F} 2005-08-11
12:27:38+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for Windows XP
(KB899591) - Security Update for Windows XP (KB899587)
{46F17A58-6F28-41A9-A41C-0393136D1B2F} 2005-08-12
07:54:25+0200 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and ready
for installation. This computer is currently scheduled to install these
updates on Friday, August 12, 2005 at 11:00 AM: - Security Update for
Windows XP (KB890859) - Update for Windows XP (KB894391) - Security Update
for Windows XP (KB899588) - Cumulative Security Update for Internet Explorer
for Windows XP (KB896727) - Security Update for Windows XP (KB896423) -
Security Update for Windows XP (KB893756) - Security Update for Windows XP
(KB899591) - Security Update for Windows XP (KB899587)
{08E19517-AFE9-40AA-9FE8-D048A9C83508} 2005-08-12
07:54:44+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{3175EAE5-6D12-4309-9C17-827F0638ED72} 2005-08-12
07:54:44+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{10BF34C7-03CE-4490-82F1-D53569BA2FB8} 2005-08-12
11:00:41+0200 1 191 101 {DD167F04-69E8-46A0-83DA-D4A5143EDBF1} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB890859)
{D5364B97-C88A-459C-813E-59F002B7488D} 2005-08-12
11:00:50+0200 1 191 101 {06F7520C-2CF3-46AB-A457-402327016632} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Update for Windows XP (KB894391)
{94FC488E-E76C-4486-A065-5D39F10B44AF} 2005-08-12
11:00:56+0200 1 191 101 {4BD8393B-9142-444D-BD40-B74172F48B86} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB899588)
{DBAB303E-21F2-4491-B16B-BF036D300CDA} 2005-08-12
11:01:13+0200 1 191 101 {76A9ECC1-0AC2-4F09-8BAF-4FC5F68EEA0C} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Cumulative Security Update for Internet Explorer for Windows XP
(KB896727)
{C02A3F84-2B07-4685-BA5D-2EFDD88FB7D0} 2005-08-12
11:01:20+0200 1 191 101 {70E702CB-5D44-494D-8594-476AC774CD51} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB896423)
{9B233023-C696-4ABB-9C8A-09D818961717} 2005-08-12
11:01:28+0200 1 191 101 {D80D91CF-6361-4FDF-B35D-F05077902973} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB893756)
{3B95A922-4021-4866-A14C-8D554B193FFB} 2005-08-12
11:01:35+0200 1 191 101 {2FCDEFD7-B98F-4A25-8DF4-F8060AFC0942} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB899591)
{5FB0A119-9683-4626-AD42-2EDC032F820A} 2005-08-12
11:01:41+0200 1 191 101 {1AFB1AFE-9AAF-4DC4-9DAC-C75303A84655} 100 0 AutomaticUpdates Success Content
Install Installation successful and restart required for the following
update: Security Update for Windows XP (KB899587)
{F916E06F-6200-407B-9653-8C9BBB924287} 2005-08-12
11:01:41+0200 1 194 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Restart Required: To complete the installation of the following
updates, the computer will be restarted within 25 minutes: - Security Update
for Windows XP (KB890859) - Update for Windows XP (KB894391) - Security
Update for Windows XP (KB899588) - Cumulative Security Update for Internet
Explorer for Windows XP (KB896727) - Security Update for Windows XP
(KB896423) - Security Update for Windows XP (KB893756) - Security Update for
Windows XP (KB899591) - Security Update for Windows XP (KB899587)
{2E6782A3-FAE6-47B6-8642-84B31A5C1135} 2005-08-12
11:05:35+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{138B344F-9171-4744-A74C-C9C3FA666AD3} 2005-08-12
12:43:07+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{4287B3E9-B5B5-4226-8422-0B452C0B93CC} 2005-08-12
12:43:07+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{178C5E62-09E9-44C4-8596-F6257A1C49AB} 2005-08-12
20:43:40+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{C22D9D6F-64CD-487F-8816-A8F8B8386A1E} 2005-08-12
20:43:40+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{BF477FF2-0FB8-4D66-8F09-EF94A3B3DD96} 2005-08-13
19:17:41+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{55D88B64-1884-4A15-A5C9-A40150A5F84F} 2005-08-13
19:17:41+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{A82BC657-F11C-4A56-8062-7AF75C3D466A} 2005-08-13
23:52:20+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{C9203427-A4E1-49F7-9201-D8CBBEA3F7FC} 2005-08-13
23:52:20+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{033B92D7-C40E-48C6-9EC5-B8550D033364} 2005-08-14
18:07:32+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{81FC2F35-6F4C-4F0D-A17F-82780539E725} 2005-08-14
18:07:32+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{12DF9C74-780A-47A9-A5B8-1D7033E6388D} 2005-08-15
08:01:31+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{6453BEC8-5D33-425A-932C-26E5EFAAC1DC} 2005-08-15
08:01:31+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{E925BA9C-19BC-4C65-A98F-EFFA60372BE9} 2005-08-15
12:46:56+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{258140C2-07BB-4391-A31C-A76DB301BAA7} 2005-08-15
12:46:56+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{64316DF9-08DF-4059-84E4-4B03BD84809D} 2005-08-16
07:35:46+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{9221E363-91E3-4577-B468-A21F6D76ED07} 2005-08-16
07:35:46+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{76FCE7AF-E90F-4E5E-B17E-FF8DCF3718FF} 2005-08-16
12:17:54+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{D2E63333-433C-4E5C-A9C1-2976C715A037} 2005-08-16
12:17:54+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{06B59183-E586-4B81-87AC-A942984B288D} 2005-08-16
19:09:59+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{BEA49F03-FE87-48C9-9CF1-12FC6969CEDF} 2005-08-16
19:09:59+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{D78A078B-FA55-47D4-BEB6-832C84054F54} 2005-08-17
07:57:23+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{85F7A660-BC70-4E5D-9FA2-08F5249EF65F} 2005-08-17
07:57:23+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{EC88C874-A7DF-45C5-A095-CE32BD5C3989} 2005-08-17
12:04:00+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{AABE9809-198F-4CB1-A22F-81FB877611C8} 2005-08-17
12:04:00+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{D8447AD6-C137-4A7D-9DA4-6F0277E1EBB9} 2005-08-17
15:01:02+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{8D19AFE8-B980-4AA4-AD54-B304B455D533} 2005-08-17
15:01:02+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{D5D5BEB8-583E-4CDC-AF0F-EA9248A998F2} 2005-08-17
23:39:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{81253917-B87F-4BA3-B0FC-94F99AC24994} 2005-08-17
23:39:27+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{EC278EF2-F453-4C51-BC03-E3DDB7154F12} 2005-08-18
09:20:00+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{9D51441A-0165-44A2-9401-9C7E5AA74963} 2005-08-18
09:20:00+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{11AA810A-31EE-4BE7-A631-FD94DEA172C6} 2005-08-18
14:18:27+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{47506714-AF2E-4908-864C-14488B218BAD} 2005-08-18
14:18:27+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{3FE01676-1286-4251-921D-14457BA2B588} 2005-08-19
07:00:34+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{DBA91077-5EF2-43E3-8F34-F6333DD7AC27} 2005-08-19
07:00:34+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{29868C83-7ED5-4510-9453-D45E81475DC4} 2005-08-19
11:33:43+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{38DC20B2-2BD5-4797-92DD-7DB5837BCDB2} 2005-08-19
11:33:43+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{E18B7A49-5F20-4AD4-A076-F3F74E39005D} 2005-08-19
20:32:49+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{B3FB176E-CFB4-4854-B68A-C4B9AF71BDB9} 2005-08-19
20:32:49+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{97D8030E-C597-4186-B620-3D351D6C1F89} 2005-08-20
00:45:39+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{8F6B6F2B-51D9-4A8D-938C-69D9F835F922} 2005-08-20
00:45:39+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{1F45F29A-301F-4C1C-B49A-C2789AFC3132} 2005-08-20
13:40:52+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{45DF6423-A4BE-4193-88C9-D9C7E34325F4} 2005-08-20
13:40:52+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{7F83C2A0-7204-4BBA-B83C-139CD8EC2CF2} 2005-08-20
18:25:00+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{182866E6-B7AC-497D-BBE0-2494FEB70812} 2005-08-20
18:25:00+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{656E1E59-7E3E-468A-A5AB-96447A206B04} 2005-08-20
22:53:09+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{06A98EC0-F5E6-43CE-8061-4FBC5648CA74} 2005-08-20
22:53:09+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{318C09E7-80ED-4573-B9C8-261C19C78546} 2005-08-21
11:04:04+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{5A035B65-0386-41FD-938B-40C18797859F} 2005-08-21
11:04:04+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{77CCDD8A-E35E-4159-A113-B1038883A70A} 2005-08-21
15:19:58+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{D9D3B706-CFDF-489E-BA16-0FA77DEC1581} 2005-08-21
15:19:58+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{344D2D6C-4AC0-435A-8DB0-2E1F8B73D7DF} 2005-08-21
20:22:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{D423E81C-E06C-494B-BB68-B845197ECE13} 2005-08-21
20:22:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{A54E443A-FBD5-45A5-B98D-41EA1817BC92} 2005-08-22
07:12:24+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{6E9C9BAF-04E1-4132-9D18-5D674ED33E42} 2005-08-22
07:12:24+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{D6746135-D6E6-4B02-A49E-FA179F4C252D} 2005-08-22
11:26:29+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{CC7DEDDF-30F5-475D-9F1B-69AEA47B63AF} 2005-08-22
11:26:29+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{208D3303-EA65-4755-8BB7-2FBB6D0FF566} 2005-08-22
16:08:59+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{9D390DE8-4520-4BA6-BB10-FE4390B4E3DB} 2005-08-22
16:08:59+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{38011BCA-98D8-4581-B2B3-30EFC287EF08} 2005-08-22
20:59:39+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{CB4A0677-0FD1-40F8-A117-FD10E79A2378} 2005-08-22
20:59:40+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{F8EA5EC0-0DBE-439B-BD88-EF5E36A60342} 2005-08-23
07:02:11+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{0BBF0F02-E195-4E9A-B0A8-7531F34E6C56} 2005-08-23
07:02:11+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
{8104367B-9674-444D-A7E3-4F16F20B9048} 2005-08-23
11:14:03+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
{CA922946-6727-4C94-A1F6-4C632062BEC4} 2005-08-23
11:14:03+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
Continue reading on narkive:
Loading...