locked
Clients Failing to Update from WSUS RRS feed

  • Question

  • Hi Folks,

    Not certain if this is a WSUS issue (clients do appear to be patching fine), or perhaps an MDT 2013 Update 2 + WSUS issue, or more of an issue patching from the state of almost-unpatched Windows 7 SP1. The following KBs are implemented via packages (so, injected offline):

    * KB2670838
    * KB917607
    * KB2639308
    * KB2728738
    * KB2729094
    * KB2731771
    * KB2834140
    * KB2878378
    * KB2882822
    * KB2888049
    * KB3020369 - April 2015 Windows Servicing Stack
    * KB3138612 - Windows 7 March 2016 Windows Update Client. Although I don't think this should be needed, as I believe the July 2016 Update Rollup contains the latest update agent within it. 

    A later step in my task sequence (that precedes any attempt to update via WSUS) is to install the Windows 7 SP1 x64 July 2016 Update Rollup.

    I currently have <ProtectYourPC> set to 3 in Unattend.xml as suggested in this guide. This shouldn't impact the ability for MDT to action Windows Updates. CustomSettings.ini is configured with the correct WSUS URL, and the logs show that it is attempting communication to the correct place.

    Our WSUS server has hardening update.

    From ZTIWindowsUpdate.log

    <![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Begin Windows Update. Reboot=[]  Retry=[]  Count = 0]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property MSIT_WU_Count is now = 1]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring client to use WSUS server http://windowsupdate.topsecret.com]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Archive NoAUtoUpdate State: Was [<empty>].]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property NoAutoUpdate_Previous is now = <empty>]LOG]!><time="15:59:15.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="15:59:17.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.23453]LOG]!><time="15:59:17.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="15:59:17.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software']]LOG]!><time="15:59:17.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="15:59:17.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Error searching for updates: ERROR_INTERNET_TIMEOUT: Retry! (-2147012894)]LOG]!><time="16:00:18.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="16:00:18.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="16:00:18.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Restore NoAutoUpdateKey to <empty>.]LOG]!><time="16:00:18.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="16:00:18.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Begin Windows Update. Reboot=[true]  Retry=[true]  Count = 1]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property MSIT_WU_Count is now = 2]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = ]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = ]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring client to use WSUS server http://windowsupdate.topsecret.com]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="16:01:24.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="16:01:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.23453]LOG]!><time="16:01:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="16:01:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software']]LOG]!><time="16:01:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="16:01:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Error searching for updates: ERROR_INTERNET_TIMEOUT: Retry! (-2147012894)]LOG]!><time="16:03:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="16:03:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="16:03:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Restore NoAutoUpdateKey to <empty>.]LOG]!><time="16:03:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="16:03:26.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Begin Windows Update. Reboot=[true]  Retry=[true]  Count = 2]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property MSIT_WU_Count is now = 3]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = ]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = ]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring client to use WSUS server http://windowsupdate.topsecret.com]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="16:18:42.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="16:18:46.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.23453]LOG]!><time="16:18:46.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="16:18:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software']]LOG]!><time="16:18:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="16:18:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Error searching for updates: ERROR_INTERNET_TIMEOUT: Retry! (-2147012894)]LOG]!><time="16:19:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="16:19:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="16:19:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Restore NoAutoUpdateKey to <empty>.]LOG]!><time="16:19:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="16:19:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Begin Windows Update. Reboot=[true]  Retry=[true]  Count = 3]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property MSIT_WU_Count is now = 4]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = ]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = ]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring client to use WSUS server http://windowsupdate.topsecret.com]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="16:24:49.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="16:25:46.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.23453]LOG]!><time="16:25:46.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="16:25:46.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software']]LOG]!><time="16:25:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="16:25:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Error searching for updates: ERROR_INTERNET_TIMEOUT: Retry! (-2147012894)]LOG]!><time="16:27:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="16:27:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="16:27:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Restore NoAutoUpdateKey to <empty>.]LOG]!><time="16:27:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="16:27:47.000+000" date="07-26-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">

    From WindowsUpdate.log

    2016-07-26	16:30:56:423	 880	318	Misc	===========  Logging initialized (build: 7.6.7601.23453, tz: +0100)  ===========
    2016-07-26	16:30:56:423	 880	318	Misc	  = Process: C:\windows\system32\svchost.exe
    2016-07-26	16:30:56:423	 880	318	Misc	  = Module: c:\windows\system32\wuaueng.dll
    2016-07-26	16:30:56:423	 880	318	Service	*************
    2016-07-26	16:30:56:423	 880	318	Service	** START **  Service: Service startup
    2016-07-26	16:30:56:423	 880	318	Service	*********
    2016-07-26	16:30:56:501	 880	318	Agent	  * WU client version 7.6.7601.23453
    2016-07-26	16:30:56:516	 880	318	Agent	  * Base directory: C:\windows\SoftwareDistribution
    2016-07-26	16:30:56:516	 880	318	Agent	  * Access type: No proxy
    2016-07-26	16:30:56:516	 880	318	Agent	  * Network state: Connected
    2016-07-26	16:31:42:552	 880	318	Report	CWERReporter::Init succeeded
    2016-07-26	16:31:42:552	 880	318	Agent	***********  Agent: Initializing Windows Update Agent  ***********
    2016-07-26	16:31:42:552	 880	318	Agent	  * Prerequisite roots succeeded.
    2016-07-26	16:31:42:552	 880	318	Agent	***********  Agent: Initializing global settings cache  ***********
    2016-07-26	16:31:42:552	 880	318	Agent	  * WSUS server: http://windowsupdate.topsecret.com
    2016-07-26	16:31:42:552	 880	318	Agent	  * WSUS status server: http://windowsupdate.topsecret.com
    2016-07-26	16:31:42:552	 880	318	Agent	  * Target group: (Unassigned Computers)
    2016-07-26	16:31:42:552	 880	318	Agent	  * Windows Update access disabled: No
    2016-07-26	16:31:42:552	 880	318	DnldMgr	Download manager restoring 0 downloads
    2016-07-26	16:31:42:567	 880	318	AU	###########  AU: Initializing Automatic Updates  ###########
    2016-07-26	16:31:42:567	 880	318	AU	  # AU is not configured yet
    2016-07-26	16:31:42:567	 880	318	AU	  # Will interact with non-admins (Non-admins are elevated (User preference))
    2016-07-26	16:31:42:567	 880	318	AU	AU is not configured yet, generating timeout to launch setup wizard
    2016-07-26	16:31:42:567	 880	318	AU	Initializing featured updates
    2016-07-26	16:31:42:567	 880	318	AU	Found 0 cached featured updates
    2016-07-26	16:31:42:630	 880	318	Report	***********  Report: Initializing static reporting data  ***********
    2016-07-26	16:31:42:630	 880	318	Report	  * OS Version = 6.1.7601.1.0.65792
    2016-07-26	16:31:42:630	 880	318	Report	  * OS Product Type = 0x00000004
    2016-07-26	16:31:42:645	 880	318	Report	  * Computer Brand = VMware, Inc.
    2016-07-26	16:31:42:645	 880	318	Report	  * Computer Model = VMware Virtual Platform
    2016-07-26	16:31:42:645	 880	318	Report	  * Bios Revision = 6.00
    2016-07-26	16:31:42:645	 880	318	Report	  * Bios Name = PhoenixBIOS 4.0 Release 6.0     
    2016-07-26	16:31:42:645	 880	318	Report	  * Bios Release Date = 2013-10-22T00:00:00
    2016-07-26	16:31:42:645	 880	318	Report	  * Locale ID = 2057
    2016-07-26	16:31:42:770	 880	318	AU	Successfully wrote event for AU health state:0
    2016-07-26	16:31:42:770	 880	318	AU	Successfully wrote event for AU health state:0
    2016-07-26	16:31:42:770	 880	318	AU	AU finished delayed initialization
    2016-07-26	16:32:42:518	 880	7bc	Misc	WARNING: Send failed with hr = 80072ee2.
    2016-07-26	16:32:42:518	 880	7bc	Misc	WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-07-26	16:32:42:518	 880	7bc	Misc	FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-07-26	16:32:42:518	 880	7bc	PT	  + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-07-26	16:32:42:518	 880	7bc	PT	  + Caller provided credentials = No
    2016-07-26	16:32:42:518	 880	7bc	PT	  + Impersonate flags = 0
    2016-07-26	16:32:42:518	 880	7bc	PT	  + Possible authorization schemes used = 
    2016-07-26	16:32:42:518	 880	7bc	PT	WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-07-26	16:32:42:518	 880	7bc	PT	WARNING: PTError: 0x80072ee2
    2016-07-26	16:32:42:518	 880	7bc	PT	WARNING: GetConfig_WithRecovery failed: 0x80072ee2
    2016-07-26	16:32:42:518	 880	7bc	PT	WARNING: RefreshConfig failed: 0x80072ee2
    2016-07-26	16:32:42:518	 880	7bc	PT	WARNING: RefreshPTState failed: 0x80072ee2
    2016-07-26	16:32:42:518	 880	7bc	PT	WARNING: PTError: 0x80072ee2
    2016-07-26	16:32:42:518	 880	7bc	Report	WARNING: Reporter failed to upload events with hr = 80072ee2.
    2016-07-26	16:33:42:532	 880	7bc	Misc	WARNING: Send failed with hr = 80072ee2.
    2016-07-26	16:33:42:532	 880	7bc	Misc	WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-07-26	16:33:42:532	 880	7bc	Misc	FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-07-26	16:33:42:532	 880	7bc	PT	  + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-07-26	16:33:42:532	 880	7bc	PT	  + Caller provided credentials = No
    2016-07-26	16:33:42:532	 880	7bc	PT	  + Impersonate flags = 0
    2016-07-26	16:33:42:532	 880	7bc	PT	  + Possible authorization schemes used = 
    2016-07-26	16:33:42:532	 880	7bc	PT	WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-07-26	16:33:42:532	 880	7bc	PT	WARNING: PTError: 0x80072ee2
    2016-07-26	16:33:42:532	 880	7bc	PT	WARNING: GetConfig_WithRecovery failed: 0x80072ee2
    2016-07-26	16:33:42:532	 880	7bc	PT	WARNING: RefreshConfig failed: 0x80072ee2
    2016-07-26	16:33:42:532	 880	7bc	PT	WARNING: RefreshPTState failed: 0x80072ee2
    2016-07-26	16:33:42:532	 880	7bc	PT	WARNING: PTError: 0x80072ee2
    2016-07-26	16:33:42:532	 880	7bc	Report	WARNING: Reporter failed to upload events with hr = 80072ee2.
    2016-07-26	16:34:42:529	 880	7bc	Misc	WARNING: Send failed with hr = 80072ee2.
    2016-07-26	16:34:42:529	 880	7bc	Misc	WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-07-26	16:34:42:529	 880	7bc	Misc	FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-07-26	16:34:42:529	 880	7bc	PT	  + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-07-26	16:34:42:529	 880	7bc	PT	  + Caller provided credentials = No
    2016-07-26	16:34:42:529	 880	7bc	PT	  + Impersonate flags = 0
    2016-07-26	16:34:42:529	 880	7bc	PT	  + Possible authorization schemes used = 
    2016-07-26	16:34:42:529	 880	7bc	PT	WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-07-26	16:34:42:529	 880	7bc	PT	WARNING: PTError: 0x80072ee2
    2016-07-26	16:34:42:529	 880	7bc	PT	WARNING: GetConfig_WithRecovery failed: 0x80072ee2
    2016-07-26	16:34:42:529	 880	7bc	PT	WARNING: RefreshConfig failed: 0x80072ee2
    2016-07-26	16:34:42:529	 880	7bc	PT	WARNING: RefreshPTState failed: 0x80072ee2
    2016-07-26	16:34:42:529	 880	7bc	PT	WARNING: PTError: 0x80072ee2
    2016-07-26	16:34:42:529	 880	7bc	Report	WARNING: Reporter failed to upload events with hr = 80072ee2.
    2016-07-26	16:52:21:693	 880	640	PT	WARNING: Cached cookie has expired or new PID is available
    2016-07-26	16:52:21:693	 880	640	PT	Initializing simple targeting cookie, clientId = 2801ae6c-94ea-45a9-b2d9-01afa7a0f211, target group = , DNS name = computi-1hk80nn
    2016-07-26	16:52:21:693	 880	640	PT	  Server URL = http://windowsupdate.topsecret.com/SimpleAuthWebService/SimpleAuth.asmx
    2016-07-26	16:52:21:849	 880	640	Report	Uploading 1 events using cached cookie, reporting URL = http://windowsupdate.topsecret.com/ReportingWebService/ReportingWebService.asmx
    2016-07-26	16:52:21:864	 880	640	Report	Reporter successfully uploaded 1 events.



    • Edited by Kirk Watts Tuesday, July 26, 2016 4:29 PM
    Tuesday, July 26, 2016 4:13 PM

All replies

  • 0x80072ee2 is an internet timeout error. You might be better off posting to the Windows Server>WSUS forum
    Wednesday, July 27, 2016 2:29 PM
  • Not wanting to be chastised for cross-posting, I hedged my bets and posted here as currently devices not in this scenario appear to be updating without issue. My conclusion was it is more likely to be a MDT + WSUS issue versus WSUS itself.
    • Edited by Kirk Watts Wednesday, July 27, 2016 3:53 PM
    Wednesday, July 27, 2016 3:52 PM
  • The cumulative update doesn't come from WSUS so in the case where you run Windows update by itself you don't see this?  You will need to install the servicing stack update then reboot (Servicing stack update).  Then install the cumulative update then reboot (Cumulative Win 7 update).

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    Wednesday, July 27, 2016 4:12 PM
  • Hi Ty,

    I offline inject the servicing stack update from 'packages'. Other than those listed in my 'injected' list (which includes the servicing stack update), I am installing them when the OS is live, via task sequence, and then rebooting after each one. Due to an issue highlighted by Johan Ardwidmark, I'm not currently using the convenience update (although when I have, the issue remains). I am however using the July update rollup. 

    I am in essence, building as per this guide: http://deploymentresearch.com/Research/Post/521/Back-to-Basics-Building-a-Windows-7-SP1-Reference-Image-using-MDT-2013-Update-2

    So as far as I'm aware, I should have the requisite patches in place for this to work.


    • Edited by Kirk Watts Wednesday, July 27, 2016 4:32 PM
    Wednesday, July 27, 2016 4:31 PM
  • The other thing... MDT is run in the system context so not really routeable.  Is your WSUS local?  If it isn't that is why there is a timeout.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    Wednesday, July 27, 2016 4:37 PM
  • It's hosted on the same VMware infrastructure this VM is hosted on and other VMs also update from it without issue. Just unfortunately not ones updating via MDT. That said, I was always under the impression the task sequence runs as local admin: http://deploymentresearch.com/Research/Post/524/Running-the-MDT-2013-Update-2-Task-Sequence-as-a-Different-User
    • Edited by Kirk Watts Wednesday, July 27, 2016 5:04 PM
    Wednesday, July 27, 2016 4:40 PM
  • So things we know... When ran in MDT you timeout when trying to access the WSUS.

    Reasons why you might not be able to access the WSUS in MDT.

    WSUSServer is set to http://windowsupdate.topsecret.com

    Is the port correct?

    Have you tried just setting it to http://windowsupdate?

    Have you tried setting WSUSServer to nothing and just using the public WSUS?

    I know you have had success using WU outside of MDT and that is great in that it validates your WSUS can work.

    Can you provide a link to the windows setup logs so we can see what state the update packages are in?


    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.



    • Edited by Ty Glander Wednesday, July 27, 2016 5:43 PM clarification and I missed something
    Wednesday, July 27, 2016 5:34 PM
  • Another thing... In Johan's post he has you install as an application (Step 5)(and KB3125574 if you ignore it being crossed out).

    Install - Install - Windows 7 SP1 June 2016 Rollup (KB3161608): wusa.exe Windows6.1-KB3161608-x64.msu /quiet /norestart

    Have you followed the blog exactly and see if that helps?


    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.


    • Edited by Ty Glander Wednesday, July 27, 2016 5:50 PM
    Wednesday, July 27, 2016 5:49 PM
  • Hi Ty,

    I appreciate your feedback.

    Whilst not literally topsecret.com (I’ve anonymised for security), yes the WSUS is set to the correct address and port.

    Unfortunately the VM doesn’t have access to the wider internet, as we also use this pool of VMs for Win 10 reference image creation and to our knowledge the bug (described here) isn't fixed where sys prep fails if the machine is allowed to update some of the built-in applications.

    I’ll seek out the windows setup logs.

    I can confirm that the update rollup is being installed in the way Johan prescribes, however I am using the July update as I understand this supersedes the June rollup in the same way Windows 10 CUs do (i.e. it includes everything that was in June, rather than something you install in addition to June).

    Many thanks.


    • Edited by Kirk Watts Wednesday, July 27, 2016 7:11 PM
    Wednesday, July 27, 2016 7:08 PM
  • Ever figure this out?
    Saturday, February 18, 2017 7:06 PM