Computers not reporting

am running wsus 2.0, and I have two problems. I ahve about 20 computers
that will not conncet to wsus anymore. here is the window update log for one
of the computers:

2009-08-12 08:08:07:923 1104 2104 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:08:07:923 1104 2104 PT Initializing simple targeting cookie,
clientId = 3de52689-ce1a-4e62-a756-423108253475, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:08:07:923 1104 2104 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:08:16:966 1104 2104 Misc WARNING: Send failed with hr =
80072ee7.
2009-08-12 08:08:16:966 1104 2104 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:08:16:966 1104 2104 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:08:16:966 1104 2104 PT + Caller provided credentials = No
2009-08-12 08:08:16:966 1104 2104 PT + Impersonate flags = 0
2009-08-12 08:08:16:966 1104 2104 PT + Possible authorization schemes used
=
2009-08-12 08:08:16:966 1104 2104 PT WARNING: GetAuthorizationCookie
failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP
status code = 200
2009-08-12 08:08:16:966 1104 2104 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:08:16:966 1104 2104 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:08:16:966 1104 2104 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:08:16:966 1104 2104 PT WARNING: RefreshPTState failed:
0x8024402c
2009-08-12 08:08:16:966 1104 2104 PT WARNING: PTError: 0x8024402c
2009-08-12 08:08:16:966 1104 2104 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:09:04:494 1104 280 AU ########### AU: Uninitializing
Automatic Updates ###########
2009-08-12 08:09:04:895 1104 280 Service *********
2009-08-12 08:09:04:895 1104 280 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2009-08-12 08:09:04:895 1104 280 Service *************
2009-08-12 08:10:05:662 1108 298 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0700) ===========
2009-08-12 08:10:05:732 1108 298 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-08-12 08:10:05:732 1108 298 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-08-12 08:10:05:522 1108 298 Service *************
2009-08-12 08:10:05:742 1108 298 Service ** START ** Service: Service startup
2009-08-12 08:10:05:792 1108 298 Service *********
2009-08-12 08:10:05:832 1108 298 Agent * WU client version 7.2.6001.788
2009-08-12 08:10:05:832 1108 298 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-08-12 08:10:05:832 1108 298 Agent * Access type: No proxy
2009-08-12 08:10:05:842 1108 298 Agent * Network state: Connected
2009-08-12 08:10:57:847 1108 298 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-08-12 08:10:57:847 1108 298 Agent *********** Agent: Initializing
global settings cache ***********
2009-08-12 08:10:57:857 1108 298 Agent * WSUS server: http://spear
2009-08-12 08:10:57:857 1108 298 Agent * WSUS status server: http://spear
2009-08-12 08:10:57:857 1108 298 Agent * Target group: XP CAL
2009-08-12 08:10:57:857 1108 298 Agent * Windows Update access disabled: No
2009-08-12 08:10:57:907 1108 298 DnldMgr Download manager restoring 0
downloads
2009-08-12 08:10:57:997 1108 298 AU ########### AU: Initializing Automatic
Updates ###########
2009-08-12 08:10:57:997 1108 298 AU # WSUS server: http://spear
2009-08-12 08:10:57:997 1108 298 AU # Detection frequency: 22
2009-08-12 08:10:57:997 1108 298 AU # Target group: XP CAL
2009-08-12 08:10:58:017 1108 298 AU # Approval type: Scheduled (Policy)
2009-08-12 08:10:58:017 1108 298 AU # Scheduled install day/time: Every
day at 10:00
2009-08-12 08:10:58:017 1108 298 AU # Auto-install minor updates: Yes
(Policy)
2009-08-12 08:10:58:157 1108 298 AU Setting AU scheduled install time to
2009-08-12 17:00:00
2009-08-12 08:10:58:157 1108 298 AU AU finished delayed initialization
2009-08-12 08:10:58:157 1108 298 Report *********** Report: Initializing
static reporting data ***********
2009-08-12 08:10:58:157 1108 298 Report * OS Version = 5.1.2600.3.0.65792
2009-08-12 08:11:00:060 1108 298 Report * Computer Brand = Dell Inc.

2009-08-12 08:11:00:060 1108 298 Report * Computer Model = OptiPlex GX280

2009-08-12 08:11:00:070 1108 298 Report * Bios Revision = A08
2009-08-12 08:11:00:070 1108 298 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 A08
2009-08-12 08:11:00:070 1108 298 Report * Bios Release Date =
2006-03-03T00:00:00
2009-08-12 08:11:00:070 1108 298 Report * Locale ID = 1033
2009-08-12 08:11:05:678 1108 ee0 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:11:05:678 1108 ee0 PT Initializing simple targeting cookie,
clientId = 3de52689-ce1a-4e62-a756-423108253475, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:11:05:678 1108 ee0 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:11:16:814 1108 ee0 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:11:16:814 1108 ee0 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:11:16:814 1108 ee0 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:11:16:814 1108 ee0 PT + Caller provided credentials = No
2009-08-12 08:11:16:814 1108 ee0 PT + Impersonate flags = 0
2009-08-12 08:11:16:814 1108 ee0 PT + Possible authorization schemes used =
2009-08-12 08:11:16:814 1108 ee0 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:11:16:814 1108 ee0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:11:16:824 1108 ee0 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:11:16:824 1108 ee0 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:11:16:824 1108 ee0 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:11:16:824 1108 ee0 PT WARNING: PTError: 0x8024402c
2009-08-12 08:11:16:824 1108 ee0 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:11:17:155 1108 ee0 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:11:17:155 1108 ee0 PT Initializing simple targeting cookie,
clientId = 3de52689-ce1a-4e62-a756-423108253475, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:11:17:155 1108 ee0 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:11:21:671 1108 ee0 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:11:21:671 1108 ee0 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:11:21:671 1108 ee0 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:11:21:671 1108 ee0 PT + Caller provided credentials = No
2009-08-12 08:11:21:671 1108 ee0 PT + Impersonate flags = 0
2009-08-12 08:11:21:671 1108 ee0 PT + Possible authorization schemes used =
2009-08-12 08:11:21:671 1108 ee0 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:11:21:671 1108 ee0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:11:21:671 1108 ee0 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:11:21:671 1108 ee0 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:11:21:671 1108 ee0 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:11:21:671 1108 ee0 PT WARNING: PTError: 0x8024402c
2009-08-12 08:11:21:671 1108 ee0 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:11:21:721 1108 ee0 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:11:21:721 1108 ee0 PT Initializing simple targeting cookie,
clientId = 3de52689-ce1a-4e62-a756-423108253475, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:11:21:721 1108 ee0 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:11:26:228 1108 ee0 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:11:26:228 1108 ee0 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:11:26:228 1108 ee0 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:11:26:228 1108 ee0 PT + Caller provided credentials = No
2009-08-12 08:11:26:228 1108 ee0 PT + Impersonate flags = 0
2009-08-12 08:11:26:228 1108 ee0 PT + Possible authorization schemes used =
2009-08-12 08:11:26:228 1108 ee0 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:11:26:228 1108 ee0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:11:26:228 1108 ee0 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:11:26:228 1108 ee0 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:11:26:228 1108 ee0 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:11:26:228 1108 ee0 PT WARNING: PTError: 0x8024402c
2009-08-12 08:11:26:238 1108 ee0 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:12:13:185 1108 298 AU ########### AU: Uninitializing
Automatic Updates ###########
2009-08-12 08:12:13:295 1108 298 Service *********
2009-08-12 08:12:13:295 1108 298 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2009-08-12 08:12:13:295 1108 298 Service *************
2009-08-12 08:12:16:210 1108 294 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0700) ===========
2009-08-12 08:12:16:210 1108 294 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-08-12 08:12:16:210 1108 294 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-08-12 08:12:16:210 1108 294 Service *************
2009-08-12 08:12:16:210 1108 294 Service ** START ** Service: Service startup
2009-08-12 08:12:16:210 1108 294 Service *********
2009-08-12 08:12:16:210 1108 294 Agent * WU client version 7.2.6001.788
2009-08-12 08:12:16:210 1108 294 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-08-12 08:12:16:210 1108 294 Agent * Access type: No proxy
2009-08-12 08:12:16:220 1108 294 Agent * Network state: Connected
2009-08-12 08:12:18:883 1108 4f8 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-08-12 08:12:18:893 1108 294 Agent Created new random SusClientId
a005e515-4b6a-4acc-8e18-9b92e8778257. Old Id: none.
2009-08-12 08:12:18:893 1108 294 Report *********** Report: Initializing
static reporting data ***********
2009-08-12 08:12:18:893 1108 294 Report * OS Version = 5.1.2600.3.0.65792
2009-08-12 08:12:18:903 1108 4f8 Agent *********** Agent: Initializing
global settings cache ***********
2009-08-12 08:12:18:903 1108 4f8 Agent * WSUS server: http://spear
2009-08-12 08:12:18:903 1108 4f8 Agent * WSUS status server: http://spear
2009-08-12 08:12:18:903 1108 4f8 Agent * Target group: XP CAL
2009-08-12 08:12:18:903 1108 4f8 Agent * Windows Update access disabled: No
2009-08-12 08:12:18:913 1108 4f8 DnldMgr Download manager restoring 0
downloads
2009-08-12 08:12:18:924 1108 4f8 AU ########### AU: Initializing Automatic
Updates ###########
2009-08-12 08:12:18:924 1108 4f8 AU # WSUS server: http://spear
2009-08-12 08:12:18:924 1108 4f8 AU # Detection frequency: 22
2009-08-12 08:12:18:924 1108 4f8 AU # Target group: XP CAL
2009-08-12 08:12:18:924 1108 4f8 AU # Approval type: Scheduled (Policy)
2009-08-12 08:12:18:934 1108 4f8 AU # Scheduled install day/time: Every
day at 10:00
2009-08-12 08:12:18:934 1108 4f8 AU # Auto-install minor updates: Yes
(Policy)
2009-08-12 08:12:18:934 1108 4f8 AU Setting AU scheduled install time to
2009-08-12 17:00:00
2009-08-12 08:12:18:944 1108 4f8 AU AU finished delayed initialization
2009-08-12 08:12:18:944 1108 4f8 AU Triggering AU detection through
DetectNow API
2009-08-12 08:12:18:944 1108 4f8 AU Triggering Online detection
(non-interactive)
2009-08-12 08:12:19:004 1108 294 Report * Computer Brand = Dell Inc.

2009-08-12 08:12:19:004 1108 294 Report * Computer Model = OptiPlex GX280

2009-08-12 08:12:19:004 1108 294 Report * Bios Revision = A08
2009-08-12 08:12:19:004 1108 294 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 A08
2009-08-12 08:12:19:014 1108 294 Report * Bios Release Date =
2006-03-03T00:00:00
2009-08-12 08:12:19:014 1108 294 Report * Locale ID = 1033
2009-08-12 08:12:19:014 1108 294 AU #############
2009-08-12 08:12:19:014 1108 294 AU ## START ## AU: Search for updates
2009-08-12 08:12:19:014 1108 294 AU #########
2009-08-12 08:12:19:034 1108 294 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {E1419F41-E964-4DB2-9B39-59D1BF136F14}]
2009-08-12 08:12:20:486 1108 5e0 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:12:20:486 1108 5e0 PT Initializing simple targeting cookie,
clientId = a005e515-4b6a-4acc-8e18-9b92e8778257, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:12:20:486 1108 5e0 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:12:27:586 1108 5f0 AU AU found 0 updates for install at shutdown
2009-08-12 08:12:27:606 2744 b98 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0700) ===========
2009-08-12 08:12:27:606 2744 b98 Misc = Process: C:\WINDOWS\Explorer.EXE
2009-08-12 08:12:27:606 2744 b98 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-08-12 08:12:27:606 2744 b98 Shutdwn Install at shutdown: no updates to
install
2009-08-12 08:12:29:519 1108 5e0 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:12:29:519 1108 5e0 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:12:29:519 1108 5e0 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:12:29:519 1108 5e0 PT + Caller provided credentials = No
2009-08-12 08:12:29:519 1108 5e0 PT + Impersonate flags = 0
2009-08-12 08:12:29:519 1108 5e0 PT + Possible authorization schemes used =
2009-08-12 08:12:29:519 1108 5e0 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:12:29:519 1108 5e0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:12:29:529 1108 5e0 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:12:29:529 1108 5e0 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:12:29:529 1108 5e0 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:12:29:529 1108 5e0 PT WARNING: PTError: 0x8024402c
2009-08-12 08:12:29:529 1108 5e0 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:12:29:569 1108 5e0 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:12:29:569 1108 5e0 PT Initializing simple targeting cookie,
clientId = a005e515-4b6a-4acc-8e18-9b92e8778257, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:12:29:569 1108 5e0 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:12:34:085 1108 5e0 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:12:34:085 1108 5e0 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:12:34:085 1108 5e0 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:12:34:085 1108 5e0 PT + Caller provided credentials = No
2009-08-12 08:12:34:085 1108 5e0 PT + Impersonate flags = 0
2009-08-12 08:12:34:085 1108 5e0 PT + Possible authorization schemes used =
2009-08-12 08:12:34:085 1108 5e0 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:12:34:085 1108 5e0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:12:34:085 1108 5e0 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:12:34:085 1108 5e0 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:12:34:085 1108 5e0 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:12:34:085 1108 5e0 PT WARNING: PTError: 0x8024402c
2009-08-12 08:12:34:085 1108 5e0 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:12:34:676 1108 5e0 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:12:34:676 1108 5e0 PT Initializing simple targeting cookie,
clientId = a005e515-4b6a-4acc-8e18-9b92e8778257, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:12:34:676 1108 5e0 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:12:36:959 1108 294 AU ########### AU: Uninitializing
Automatic Updates ###########
2009-08-12 08:12:39:183 1108 5e0 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:12:39:183 1108 5e0 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:12:39:183 1108 5e0 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:12:39:183 1108 5e0 PT + Caller provided credentials = No
2009-08-12 08:12:39:183 1108 5e0 PT + Impersonate flags = 0
2009-08-12 08:12:39:183 1108 5e0 PT + Possible authorization schemes used =
2009-08-12 08:12:39:183 1108 5e0 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:12:39:183 1108 5e0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:12:39:183 1108 5e0 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:12:39:183 1108 5e0 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:12:39:183 1108 5e0 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:12:39:183 1108 5e0 PT WARNING: PTError: 0x8024402c
2009-08-12 08:12:39:183 1108 5e0 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:12:39:183 1108 294 Service *********
2009-08-12 08:12:39:183 1108 294 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2009-08-12 08:12:39:183 1108 294 Service *************
2009-08-12 08:13:40:078 1104 264 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0700) ===========
2009-08-12 08:13:40:158 1104 264 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-08-12 08:13:40:709 1104 264 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-08-12 08:13:40:078 1104 264 Service *************
2009-08-12 08:13:40:799 1104 264 Service ** START ** Service: Service startup
2009-08-12 08:13:40:799 1104 264 Service *********
2009-08-12 08:13:40:809 1104 264 Agent * WU client version 7.2.6001.788
2009-08-12 08:13:40:809 1104 264 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-08-12 08:13:40:809 1104 264 Agent * Access type: No proxy
2009-08-12 08:13:40:829 1104 264 Agent * Network state: Connected
2009-08-12 08:14:27:937 1104 264 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-08-12 08:14:27:947 1104 264 Agent *********** Agent: Initializing
global settings cache ***********
2009-08-12 08:14:27:947 1104 264 Agent * WSUS server: http://spear
2009-08-12 08:14:27:947 1104 264 Agent * WSUS status server: http://spear
2009-08-12 08:14:27:947 1104 264 Agent * Target group: XP CAL
2009-08-12 08:14:27:947 1104 264 Agent * Windows Update access disabled: No
2009-08-12 08:14:27:947 1104 264 DnldMgr Download manager restoring 0
downloads
2009-08-12 08:14:27:957 1104 264 AU ########### AU: Initializing Automatic
Updates ###########
2009-08-12 08:14:27:967 1104 264 AU # WSUS server: http://spear
2009-08-12 08:14:27:967 1104 264 AU # Detection frequency: 22
2009-08-12 08:14:27:967 1104 264 AU # Target group: XP CAL
2009-08-12 08:14:27:967 1104 264 AU # Approval type: Scheduled (Policy)
2009-08-12 08:14:27:967 1104 264 AU # Scheduled install day/time: Every
day at 10:00
2009-08-12 08:14:27:987 1104 264 AU # Auto-install minor updates: Yes
(Policy)
2009-08-12 08:14:27:997 1104 264 AU Setting AU scheduled install time to
2009-08-12 17:00:00
2009-08-12 08:14:27:997 1104 264 AU AU finished delayed initialization
2009-08-12 08:14:28:007 1104 264 Report *********** Report: Initializing
static reporting data ***********
2009-08-12 08:14:28:037 1104 264 Report * OS Version = 5.1.2600.3.0.65792
2009-08-12 08:14:29:609 1104 264 Report * Computer Brand = Dell Inc.

2009-08-12 08:14:29:609 1104 264 Report * Computer Model = OptiPlex GX280

2009-08-12 08:14:29:609 1104 264 Report * Bios Revision = A08
2009-08-12 08:14:29:609 1104 264 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 A08
2009-08-12 08:14:29:609 1104 264 Report * Bios Release Date =
2006-03-03T00:00:00
2009-08-12 08:14:29:609 1104 264 Report * Locale ID = 1033
2009-08-12 08:14:31:331 1104 934 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:14:31:331 1104 934 PT Initializing simple targeting cookie,
clientId = a005e515-4b6a-4acc-8e18-9b92e8778257, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:14:31:331 1104 934 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:14:40:545 1104 934 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:14:40:545 1104 934 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:14:40:545 1104 934 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:14:40:545 1104 934 PT + Caller provided credentials = No
2009-08-12 08:14:40:545 1104 934 PT + Impersonate flags = 0
2009-08-12 08:14:40:545 1104 934 PT + Possible authorization schemes used =
2009-08-12 08:14:40:545 1104 934 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:14:40:545 1104 934 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:14:40:545 1104 934 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:14:40:545 1104 934 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:14:40:545 1104 934 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:14:40:545 1104 934 PT WARNING: PTError: 0x8024402c
2009-08-12 08:14:40:545 1104 934 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:14:40:585 1104 934 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:14:40:585 1104 934 PT Initializing simple targeting cookie,
clientId = a005e515-4b6a-4acc-8e18-9b92e8778257, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:14:40:585 1104 934 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:14:45:091 1104 934 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:14:45:091 1104 934 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:14:45:091 1104 934 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:14:45:091 1104 934 PT + Caller provided credentials = No
2009-08-12 08:14:45:091 1104 934 PT + Impersonate flags = 0
2009-08-12 08:14:45:091 1104 934 PT + Possible authorization schemes used =
2009-08-12 08:14:45:091 1104 934 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:14:45:091 1104 934 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:14:45:091 1104 934 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:14:45:091 1104 934 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:14:45:091 1104 934 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:14:45:091 1104 934 PT WARNING: PTError: 0x8024402c
2009-08-12 08:14:45:091 1104 934 Report WARNING: Reporter failed to upload
events with hr = 8024402c.
2009-08-12 08:14:45:131 1104 934 PT WARNING: Cached cookie has expired or
new PID is available
2009-08-12 08:14:45:131 1104 934 PT Initializing simple targeting cookie,
clientId = a005e515-4b6a-4acc-8e18-9b92e8778257, target group = XP CAL, DNS
name = de658-hy41c71
2009-08-12 08:14:45:131 1104 934 PT Server URL =
http://spear/SimpleAuthWebService/SimpleAuth.asmx
2009-08-12 08:14:49:698 1104 934 Misc WARNING: Send failed with hr = 80072ee7.
2009-08-12 08:14:49:698 1104 934 Misc WARNING: SendRequest failed with hr =
80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2009-08-12 08:14:49:698 1104 934 PT + Last proxy send request failed with
hr = 0x80072EE7, HTTP status code = 0
2009-08-12 08:14:49:808 1104 934 PT + Caller provided credentials = No
2009-08-12 08:14:49:808 1104 934 PT + Impersonate flags = 0
2009-08-12 08:14:49:808 1104 934 PT + Possible authorization schemes used =
2009-08-12 08:14:49:888 1104 934 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status
code = 200
2009-08-12 08:14:49:888 1104 934 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024402c
2009-08-12 08:14:49:888 1104 934 PT WARNING: PopulateAuthCookies failed:
0x8024402c
2009-08-12 08:14:49:888 1104 934 PT WARNING: RefreshCookie failed: 0x8024402c
2009-08-12 08:14:49:898 1104 934 PT WARNING: RefreshPTState failed: 0x8024402c
2009-08-12 08:14:49:898 1104 934 PT WARNING: PTError: 0x8024402c
2009-08-12 08:14:49:898 1104 934 Report WARNING: Reporter failed to upload
events with hr = 8024402c.

I looked up a few of the errors, and from the information I got, the client
does not have the correct name of the wsus server it is supposed to point to.
Is there anything on the server side that could cause this to happen? Note
this server is also a domain controller running dns.

The second problem I had is the computers that do show up on wsus are broken
into groups such as lab, w2k, and xp. The xp group disappeared, and all the
computers in the group disappeared. some computers are reappearing in the
unassigned group. Is there any way to restore the xp group back without
waiting for all the computers to reappear in unassigned computers, and then
recreating the xp group?

Thanks for any assistance.

"zeb2100" <> wrote in message
news:70ECC588-5302-41E3-84E0-...

> am running wsus 2.0, and I have two problems.

> I have about 20 computers that will not conncet to wsus anymore.

Does this mean they used to connect? If so, what changed?


> here is the window update log for one of the computers:
>
> 2009-08-12 08:08:07:923 1104 2104 PT Server URL =
> http://spear/SimpleAuthWebService/SimpleAuth.asmx
> 2009-08-12 08:08:16:966 1104 2104 Misc WARNING: Send failed with hr =
> 80072ee7.

The =2ee7= error! <g>

0x80072EE7 -2147012889 ERROR_INTERNET_NAME_NOT_RESOLVED The server name
could not be resolved.

What is returned from the command 'nslookup spear' on this machine?

Are the machine(s) using DHCP? Have they recently started using a different
DHCP Server, or has anything been changed in the scope definitions of the
DHCP Server Scope that would have removed the default domain suffix? or were
the DNS Server options removed or misconfigured?

Has anything changed in DNS that would impact the resolution of the hostname
'spear' from these systems?


> I looked up a few of the errors, and from the information I got, the
> client
> does not have the correct name of the wsus server it is supposed to point
> to.

Well.. no.. that's not necessarily what it says, although that is *one*
possible cause of this error.

The more common scenario is that the client has the correct name, but the
name isn't resolvable via the DNS services available to the client.


> Is there anything on the server side that could cause this to happen?

No. This is exclusively a relationship between the WUAgent and DNS.


> Note this server is also a domain controller running dns.

Well, now, that's certainly interesting.

Okay.. forget the DHCP related questions, as now you've pointed out this
machine cannot possibly be using DHCP and must, in fact, have a Fixed IP
Address configured.

Next set of questions then:
Is the TCP/IP configuration of this machine correctly set to use *itself* as
the DNS Server?
Is the hostname 'spear' correctly configured in the appropriate zone file on
this machine?
Is the DNS Service actually running on this Domain Controller?


> The second problem I had is the computers that do show up on wsus are
> broken
> into groups such as lab, w2k, and xp. The xp group disappeared, and all
> the
> computers in the group disappeared.

"Disappeared"??? As in -- are no longer visible in the WSUS console at all?

There's only two ways for this to happen:

1. An administrator explicitly deletes them from the console using the
Delete Computer option.

2. The Server Cleanup Wizard.... oh yeah.. you're still using WSUS v2.

Never mind.. only *one* way for that to happen in your case.


> some computers are reappearing in the unassigned group.

This can happen for a number of reasons:

1. WSUS is using server-based targeting and the computer was previously
deleted from the WSUS console.

2. WSUS is using policy-based targeting and the policy has been changed to
identify a target that does not exist on the WSUS server.

3. WSUS is using policy-based targeting and the policy configured has been
removed from the WSUS server.

4. The machine(s) were reimaged, or some other action causing the deletion
of the SusClientID occurred, resulting in the machine obtaining a New
Identity. (Of course, the original existence of the machine would still
exist in this case, as a stale entry, so this is not likely the cause in
this particular instance.)



> Is there any way to restore the xp group back without waiting for all the
> computers to reappear in unassigned computers, and then recreating the xp
> group?

=Recreating= the XP Group? Are you saying the group currently does not
exist?

If the group does exist, then before we can discuss any ways to "restore the
XP group", we first need to find out exactly why the machines are no longer
listed in the group -- but there's certainly no need, or point, in
deleting/recreating the group.

1. If you're using server-based targeting, then the *only* option is to
place them in the correct group.

2. If you're using policy-based targeting, then you need to determine which
group the client *thinks* it's supposed to be a member of, and either repair
the policy so it has the correct (existing) group name, or (if the group
really is missing on the WSUS server) recreate the group so the computer can
actually report itself as a member of an existing group.






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

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

"Lawrence Garvin [MVP]" wrote:

> "zeb2100" <> wrote in message
> news:70ECC588-5302-41E3-84E0-...
>
> > am running wsus 2.0, and I have two problems.
>
> > I have about 20 computers that will not conncet to wsus anymore.
>
> Does this mean they used to connect? If so, what changed?
>
> Yes the computers were connecting just fine and as far as I know nothing significant has changed on the computers.

> > here is the window update log for one of the computers:
> >
> > 2009-08-12 08:08:07:923 1104 2104 PT Server URL =
> > http://spear/SimpleAuthWebService/SimpleAuth.asmx
> > 2009-08-12 08:08:16:966 1104 2104 Misc WARNING: Send failed with hr =
> > 80072ee7.
>
> The =2ee7= error! <g>
>
> 0x80072EE7 -2147012889 ERROR_INTERNET_NAME_NOT_RESOLVED The server name
> could not be resolved.
>
> What is returned from the command 'nslookup spear' on this machine?
>
> Are the machine(s) using DHCP? Have they recently started using a different
> DHCP Server, or has anything been changed in the scope definitions of the
> DHCP Server Scope that would have removed the default domain suffix? or were
> the DNS Server options removed or misconfigured? DNS has not changed. the other computers are still conncting to wsus.
>
> Has anything changed in DNS that would impact the resolution of the hostname
> 'spear' from these systems?
>
>
> > I looked up a few of the errors, and from the information I got, the
> > client
> > does not have the correct name of the wsus server it is supposed to point
> > to.
>
> Well.. no.. that's not necessarily what it says, although that is *one*
> possible cause of this error.
>
> The more common scenario is that the client has the correct name, but the
> name isn't resolvable via the DNS services available to the client.
>
>
> > Is there anything on the server side that could cause this to happen?
>
> No. This is exclusively a relationship between the WUAgent and DNS.
>
>
> > Note this server is also a domain controller running dns.
>
> Well, now, that's certainly interesting.
>
> Okay.. forget the DHCP related questions, as now you've pointed out this
> machine cannot possibly be using DHCP and must, in fact, have a Fixed IP
> Address configured.
>
> Next set of questions then:
> Is the TCP/IP configuration of this machine correctly set to use *itself* as
> the DNS Server? yes
> Is the hostname 'spear' correctly configured in the appropriate zone file on
> this machine? yes
> Is the DNS Service actually running on this Domain Controller?yes
>
>
> > The second problem I had is the computers that do show up on wsus are
> > broken
> > into groups such as lab, w2k, and xp. The xp group disappeared, and all
> > the
> > computers in the group disappeared.
>
> "Disappeared"??? As in -- are no longer visible in the WSUS console at all? yes no longer visible.
>
> There's only two ways for this to happen:
>
> 1. An administrator explicitly deletes them from the console using the
> Delete Computer option. They were not deleted.
>
> 2. The Server Cleanup Wizard.... oh yeah.. you're still using WSUS v2.
>
> Never mind.. only *one* way for that to happen in your case.
>
>
> > some computers are reappearing in the unassigned group.
>
> This can happen for a number of reasons:
>
> 1. WSUS is using server-based targeting and the computer was previously
> deleted from the WSUS console.
>
> 2. WSUS is using policy-based targeting and the policy has been changed to
> identify a target that does not exist on the WSUS server.
>
> 3. WSUS is using policy-based targeting and the policy configured has been
> removed from the WSUS server.
>
> 4. The machine(s) were reimaged, or some other action causing the deletion
> of the SusClientID occurred, resulting in the machine obtaining a New
> Identity. (Of course, the original existence of the machine would still
> exist in this case, as a stale entry, so this is not likely the cause in
> this particular instance.)
>
>
>
> > Is there any way to restore the xp group back without waiting for all the
> > computers to reappear in unassigned computers, and then recreating the xp
> > group?
>
> =Recreating= the XP Group? Are you saying the group currently does not
> exist? yes. the xp group was there, and then it was not there.
>
> If the group does exist, then before we can discuss any ways to "restore the
> XP group", we first need to find out exactly why the machines are no longer
> listed in the group -- but there's certainly no need, or point, in
> deleting/recreating the group.
>
> 1. If you're using server-based targeting, then the *only* option is to
> place them in the correct group.
>
> 2. If you're using policy-based targeting, then you need to determine which
> group the client *thinks* it's supposed to be a member of, and either repair
> the policy so it has the correct (existing) group name, or (if the group
> really is missing on the WSUS server) recreate the group so the computer can
> actually report itself as a member of an existing group.
>
>
>
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"zeb2100" <> wrote in message
news:5DCD734F-25EE-45F9-912C-...
>
> Ran nslookup spear on the computer in question, and the ip address was
> resolved, but spear.calad.sdsu.edu was not resolved.

I would start by remediating this issue. A machine *should* be able to
resolve itself using it's fully qualified domain name.

My suspicion is that the WUAgent is trying to do exactly that -- it's
properly appending the assigned domain suffix (calad.sdsu.edu) to the target
hostname (spear), and that resolution attempt is failing, resulting in the
'2ee7' error.

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

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

The work around I found was to have the computers point to wsus using the ip
address of the wsus server. All the computers in question were using static
ip. Computers using dhcp are working fine.

I would like to upgrade to wsus 3.0 now. Are there any issues I should be
concerned with? Thanks.

"Lawrence Garvin [MVP]" wrote:

> "zeb2100" <> wrote in message
> news:5DCD734F-25EE-45F9-912C-...
> >
> > Ran nslookup spear on the computer in question, and the ip address was
> > resolved, but spear.calad.sdsu.edu was not resolved.
>
> I would start by remediating this issue. A machine *should* be able to
> resolve itself using it's fully qualified domain name.
>
> My suspicion is that the WUAgent is trying to do exactly that -- it's
> properly appending the assigned domain suffix (calad.sdsu.edu) to the target
> hostname (spear), and that resolution attempt is failing, resulting in the
> '2ee7' error.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"zeb2100" <> wrote in message
news:0C90ACE7-CF23-4D9A-AC2C-...
>
> The work around I found was to have the computers point to wsus using the
> ip
> address of the wsus server.

This is a functional workaround, but not the optimal configuration. The fact
that this workaround is successful narrows down the scope of the fault to
your DNS system. You will want to remediate this DNS issue as it's likely to
affect other applications and network connectivity as well, if the clients
are not able to properly resolve hostnames.

> All the computers in question were using static ip.

Aha!.. Then perhaps these computers using Static IP Addressing have either:
[1] Not been properly configured with the DNS Suffix or the DNS Suffix
Search Order options, or
[2] Do not have DNS Servers properly configured to support hostname
resolution.

> I would like to upgrade to wsus 3.0 now. Are there any issues I should be
> concerned with?

I would really suggest fixing the DNS issues before pursuing the upgrade to
WSUS v3.

However, as directly relates to upgrading to WSUS v3, my strongest
recommendation is to read the Release Notes... Cover-To-Cover... TWICE!

And then perform a test upgrade in a TEST environment, based on a system
backup/restore of your existing WSUS v2 server. Once you've successfully
upgraded a TEST machine based on your current environment, then you can be
secure in expecting your production upgrade to perform flawlessly.


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

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