Windows Updates via ConfigMgr not showing because a proxy is set

We’ve had some instances where a small number of our servers weren’t receiving the Windows updates icon in the taskbar. After checking the logs we had all the below errors:
Windows Update.log (located at %windir%)
2010-02-01 09:42:02:687 908 880 Agent * Access type: Named proxy
2010-02-01 09:42:02:687 908 880 Agent * Default proxy:
2010-02-01 09:42:02:687 908 880 Agent * Default proxy bypass: 192.168.178.15;;ldckvssrv;ldckvssrv.global.XXX.com;ldckvs1;ldckvs1.global.XXX.com;ldckvs2;ldckvs2.global.XXX.com;eurkvs1;eurkvs1.global.XXX.com;eurev01;eurev01.global.XXX.com;eurev02;eurev02.global.XXX.com;eurev03;eurev03.global.XXX.com

2010-02-05 19:35:31:065 8312 19a4 COMAPI ————-
2010-02-05 19:35:31:065 8312 19a4 COMAPI — START — COMAPI: Search [ClientId = CcmExec]
2010-02-05 19:35:31:065 8312 19a4 COMAPI ———
2010-02-05 19:35:31:080 8312 19a4 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = CcmExec] 2010-02-05 19:35:31:080 908 a80 Agent ************* 2010-02-05 19:35:31:080 908 a80 Agent ** START ** Agent: Finding updates [CallerId = CcmExec] 2010-02-05 19:35:31:080 908 a80 Agent ********* 2010-02-05 19:35:31:080 908 a80 Agent * Include potentially superseded updates 2010-02-05 19:35:31:080 908 a80 Agent * Online = Yes; Ignore download priority = Yes 2010-02-05 19:35:31:080 908 a80 Agent * Criteria = “(DeploymentAction=* AND Type=’Software’) OR (DeploymentAction=* AND Type=’Driver’)” 2010-02-05 19:35:31:080 908 a80 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2010-02-05 19:35:31:080 908 a80 Agent * Search Scope = {Machine} 2010-02-05 19:35:32:002 908 a80 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2010-02-05 19:35:32:002 908 a80 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://GLOSCCM03.global.XXX.com:8530/ClientWebService/client.asmx 2010-02-05 19:35:36:565 908 a80 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <> Bypass List used : <192.168.178.15;;ldckvssrv;ldckvssrv.global.XXX.com;ldckvs1;ldckvs1.global.XXX.com;ldckvs2;ldckvs2.global.XXX.com;eurkvs1;eurkvs1.global.XXX.com;eurev01;eurev01.global.XXX.com;eurev02;eurev02.global.XXX.com;eurev03;eurev03.global.XXX.com> Auth Schemes used : <>
2010-02-05 19:35:36:565 908 a80 PT + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
2010-02-05 19:35:36:565 908 a80 PT + Caller provided proxy = No
2010-02-05 19:35:36:565 908 a80 PT + Proxy list used =
2010-02-05 19:35:36:565 908 a80 PT + Bypass list used = 192.168.178.15;;ldckvssrv;ldckvssrv.global.XXX.com;ldckvs1;ldckvs1.global.XXX.com;ldckvs2;ldckvs2.global.XXX.com;eurkvs1;eurkvs1.global.XXX.com;eurev01;eurev01.global.XXX.com;eurev02;eurev02.global.XXX.com;eurev03;eurev03.global.XXX.com
2010-02-05 19:35:36:565 908 a80 PT + Caller provided credentials = No
2010-02-05 19:35:36:565 908 a80 PT + Impersonate flags = 0
2010-02-05 19:35:36:565 908 a80 PT + Possible authorization schemes used =
2010-02-05 19:35:36:565 908 a80 PT WARNING: GetConfig failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
2010-02-05 19:35:36:565 908 a80 PT WARNING: PTError: 0x8024402c
2010-02-05 19:35:36:565 908 a80 PT WARNING: GetConfig_WithRecovery failed: 0x8024402c
2010-02-05 19:35:36:565 908 a80 PT WARNING: RefreshConfig failed: 0x8024402c
2010-02-05 19:35:36:565 908 a80 PT WARNING: RefreshPTState failed: 0x8024402c
2010-02-05 19:35:36:565 908 a80 PT WARNING: Sync of Updates: 0x8024402c
2010-02-05 19:35:36:565 908 a80 PT WARNING: SyncServerUpdatesInternal failed: 0x8024402c
2010-02-05 19:35:36:565 908 a80 Agent * WARNING: Failed to synchronize, error = 0x8024402C
2010-02-05 19:35:36:580 908 a80 Agent * WARNING: Exit code = 0x8024402C
2010-02-05 19:35:36:580 908 a80 Agent *********
2010-02-05 19:35:36:580 908 a80 Agent ** END ** Agent: Finding updates [CallerId = CcmExec]
2010-02-05 19:35:36:580 908 a80 Agent *************
2010-02-05 19:35:36:580 908 a80 Agent WARNING: WU client failed Searching for update with error 0x8024402c
2010-02-05 19:35:36:596 8312 19a4 COMAPI >>– RESUMED — COMAPI: Search [ClientId = CcmExec]
2010-02-05 19:35:36:596 8312 19a4 COMAPI – Updates found = 0
2010-02-05 19:35:36:596 8312 19a4 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024402C
2010-02-05 19:35:36:596 8312 19a4 COMAPI ———
2010-02-05 19:35:36:596 8312 19a4 COMAPI — END — COMAPI: Search [ClientId = CcmExec]
2010-02-05 19:35:36:596 8312 19a4 COMAPI ————-
2010-02-05 19:35:36:596 8312 19a4 COMAPI WARNING: Operation failed due to earlier error, hr=8024402C
2010-02-05 19:35:36:596 8312 19a4 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024402C)

ScanAgent.log
*****WSUSLocationUpdate received for location request guid={AF6E1FF4-D889-415D-94C2-C664C7DBC52C} ScanAgent 05/02/2010 19:34:47 7724 (0x1E2C)
CScanTool::OnLocationUpdate- Ignoring the UpdateSource Location Update for UpdateSourceID={9CEB6DAB-6599-4149-9F23-531CF2D12C91}, Location=http://GLOSCCM03.global.XXX.com:8530 (Using Location=http://GLOSCCM03.global.XXX.com:8530), Version=0x000001c6 (Using Version=0x000001c6) ScanAgent 05/02/2010 19:34:47 7724 (0x1E2C)
CScanTool::OnScanRetry- Requesting scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} ScanAgent 05/02/2010 19:35:30 2180 (0x0884)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SMS_SUMScanAgentError_ScanFailed
{
ClientID = “GUID:7092B310-415C-41F9-8CE3-256772E3BBE5”;
DateTime = “20100205193536.627000+000”;
ExitCode = 16428;
MachineName = “EURXMB05”;
ProcessID = 8312;
SiteCode = “0GL”;
ThreadID = 2180;
UpdateSourceUniqueID = “{9CEB6DAB-6599-4149-9F23-531CF2D12C91}”;
UpdateType = “Microsoft Update”;
};
ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
Successfully submitted event to the Status Agent. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
– – – – – -Scan Failed for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91}, with Error=0x8024402c ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanTool::ScheduleScanRetry- ScanRetry Timer task successfully scheduled. Will wake up in next 1794 seconds ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
– – – – – -Scan Retry successfully scheduled for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanJobManager::ProcessScanToolComplete- Scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} has failed, scan request will be pending for scan retry cycle. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanJobManager::ProcessScanToolComplete- Scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} has failed, scan request will be pending for scan retry cycle. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanJobManager::ProcessScanToolComplete- Scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} has failed, scan request will be pending for scan retry cycle. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanJobManager::ProcessScanToolComplete- Scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} has failed, scan request will be pending for scan retry cycle. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanJobManager::ProcessScanToolComplete- Scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} has failed, scan request will be pending for scan retry cycle. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanJobManager::ProcessScanToolComplete- Scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} has failed, scan request will be pending for scan retry cycle. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)
CScanJobManager::ProcessScanToolComplete- Scan for ToolUniqueID={9CEB6DAB-6599-4149-9F23-531CF2D12C91} has failed, scan request will be pending for scan retry cycle. ScanAgent 05/02/2010 19:35:36 2180 (0x0884)

WUAHandler.log
Its a WSUS Update Source type ({9CEB6DAB-6599-4149-9F23-531CF2D12C91}), adding it. WUAHandler 05/02/2010 19:35:30 6564 (0x19A4)
Existing WUA Managed server was already set (http://glosccm03.global.xxx.com:8530/), skipping Group Policy registration. WUAHandler 05/02/2010 19:35:31 6564 (0x19A4)
Added Update Source ({9CEB6DAB-6599-4149-9F23-531CF2D12C91}) of content type: 2 WUAHandler 05/02/2010 19:35:31 6564 (0x19A4)
Async searching of updates using WUAgent started. WUAHandler 05/02/2010 19:35:31 6564 (0x19A4)
Async searching completed. WUAHandler 05/02/2010 19:35:36 2892 (0x0B4C)
OnSearchComplete – Failed to end search job. Error = 0x8024402c. WUAHandler 05/02/2010 19:35:36 6564 (0x19A4)
Scan failed with error = 0x8024402c. WUAHandler 05/02/2010 19:35:36 6564 (0x19A4)

This issue is to do with Windows Update rather than ConfigMgr itself.

The WindowsUpdate.log are showing lots of errors to do with the proxy used and the bypass list for Automatic Updates:
Access type: Named proxy
WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <> Bypass List used : <192.168.178.15;;ldckvssrv;ldckvssrv.global.XXX.com;ldckvs1;ldckvs1.global.XXX.com;ldckvs2;ldckvs2.global.XXX.com;eurkvs1;eurkvs1.global.XXX.com;eurev01;eurev01.global.XXX.com;eurev02;eurev02.global.XXX.com;eurev03;eurev03.global.XXX.com> Auth Schemes used : <>

What you normally see in this log is:
Access type: No proxy

It turned out that someone had set these proxys using the proxycfg.exe command. I ran the command on the servers that had issues and it came back with the same list of servers as are in the log.

More info on proxycfg.exe can be found here – http://support.microsoft.com/kb/900935.

The fix is a fairly simple one, you just need to run proxycfg –D which will remove the proxy and bypass list.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: