none
MDT and WSUS TS not actually installing updates RRS feed

  • Question

  • In my TS I specify the WSUS server. I enable to install updates before applications and after applications.

    I can watch the TS during the image deployment show its running the updates, but its quick, like it doesn't find any. 

    Even the BDD log shows its set the WSUS server properly and the client is configure hit it.

    The ZTIWindowsudpate logs show the following: I'm not sure why its trying to hit the internet when the WSUS server is specified??? After the image is laid down I can go to HKLM:Software\Policies\Microsoft\windows\windowsUpdates and see that the two values point to my WSUS server (WUServer, WUStatusServer).  I'm stuck.  Any help would be appreciated.  This used to work fine. 

    Right after the image is down I can run a update manually using MS site and it pulls a couple dozen updates....

    <![LOG[Begin Windows Update. Reboot=[true]  Retry=[true]  Count = 2]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property MSIT_WU_Count is now = 3]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRebootRequested is now = ]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property SMSTSRetryRequested is now = ]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring client to use WSUS server <a href="http://mywsusserver.fqdn:8530]LOG]!><time="15:04:34.000+000">http://mywsusserver.fqdn:8530]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 8 found, OK to continue]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.9.9600.18094]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Error searching for updates: Not Connected to Internet? (-2145107924)]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Restore NoAutoUpdateKey to <empty>.]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Event 41001 sent: ZTIWindowsUpdate processing completed successfully.]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">


    • Edited by Slade1040 Saturday, January 30, 2016 9:23 PM
    Saturday, January 30, 2016 9:22 PM

Answers

  • The error above, 0x80072ee7, means "The server name or address could not be resolved".  So the machine is having issues resolving the WSUS server name that you specified.



    Thanks,
    -Michael Niehaus
    Director of Product Marketing, Windows Deployment, Management, and Store
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com

    • Marked as answer by Slade1040 Wednesday, April 19, 2017 3:25 PM
    Sunday, January 31, 2016 6:37 PM

All replies

  • The error (‭8024402C‬, or -2145107924) means that it was having issues talking to the server.

    The WindowsUpdate.log should provide some more details on the issue.  It's possible the host name or port are wrong.


    Thanks,
    -Michael Niehaus
    Director of Product Marketing, Windows Deployment, Management, and Store
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com

    Sunday, January 31, 2016 12:00 AM
  • Michael,

    Thanks for the reply.  I've checked the update log on the machine that was imaged and noticed this section. I'm not sure if its directly related to being able to resolve the wsus server, as once the machine is finished with its TS and comes up I have no problems resolving or pathing to the WSUS server.  any ideas?

    Agent	** START **  Agent: Finding updates [CallerId = <<PROCESS>>: cscript.exe  Id = 1]
    2016-01-30	15:03:15:434	 280	afc	Agent	*********
    2016-01-30	15:03:15:434	 280	afc	Agent	  * Online = Yes; Ignore download priority = No
    2016-01-30	15:03:15:434	 280	afc	Agent	  * Criteria = "IsInstalled = 0 and IsHidden = 0"
    2016-01-30	15:03:15:434	 280	afc	Agent	  * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2016-01-30	15:03:15:434	 280	afc	Agent	  * Search Scope = {Machine}
    2016-01-30	15:03:15:434	 280	afc	Agent	  * Caller SID for Applicability: S-1-5-21-2165963734-1558764139-802513695-500
    2016-01-30	15:03:15:434	 280	afc	Agent	  * RegisterService is set
    2016-01-30	15:03:15:434	 280	afc	EP	Got WSUS Client/Server URL: "http://mywsus.fqdn:8530/ClientWebService/client.asmx"
    2016-01-30	15:03:15:528	 280	afc	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-01-30	15:03:15:528	 280	afc	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mywsus.fqdn:8530/ClientWebService/client.asmx
    2016-01-30	15:03:15:528	 280	afc	IdleTmr	WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 11; does use network; is at background priority
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: Nws Failure: errorCode=0x803d0010
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: Original error code: 0x80072ee7
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: There was an error communicating with the endpoint at 'http://mywsus.fqdn:8530/ClientWebService/client.asmx'.
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: There was an error sending the HTTP request.
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: The remote endpoint was not reachable.
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: The server name or address could not be resolved
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: MapToSusHResult mapped Nws error 0x803d0010 to 0x8024402c
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: Web service call failed with hr = 8024402c.
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: Current service auth scheme='None'.
    2016-01-30	15:03:15:606	 280	afc	WS	WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
    2016-01-30	15:03:15:606	 280	afc	WS	FATAL: OnCallFailure failed with hr=0X8024402C
    2016-01-30	15:03:15:606	 280	afc	IdleTmr	WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 11) stopped; does use network; is at background priority
    2016-01-30	15:03:15:606	 280	afc	PT	WARNING: PTError: 0x8024402c
    2016-01-30	15:03:15:606	 280	afc	PT	WARNING: GetConfig_WithRecovery failed: 0x8024402c
    2016-01-30	15:03:15:606	 280	afc	PT	WARNING: RefreshConfig failed: 0x8024402c
    2016-01-30	15:03:15:606	 280	afc	PT	WARNING: RefreshPTState failed: 0x8024402c
    2016-01-30	15:03:15:606	 280	afc	PT	  + SyncUpdates round trips: 0
    2016-01-30	15:03:15:606	 280	afc	PT	WARNING: Sync of Updates: 0x8024402c
    2016-01-30	15:03:15:606	 280	afc	PT	WARNING: SyncServerUpdatesInternal failed: 0x8024402c
    2016-01-30	15:03:15:606	 280	afc	Agent	  * WARNING: Failed to synchronize, error = 0x8024402C
    2016-01-30	15:03:15:606	 280	afc	Agent	  * WARNING: Exit code = 0x8024402C
    2016-01-30	15:03:15:606	 280	afc	Agent	*********
    2016-01-30	15:03:15:606	 280	afc	Agent	**  END  **  Agent: Finding updates [CallerId = <<PROCESS>>: cscript.exe  Id = 1]
    2016-01-30	15:03:15:622	 280	afc	Agent	*************
    2016-01-30	15:03:15:622	 280	afc	Agent	WARNING: WU client failed Searching for update with error 0x8024402c
    2016-01-30	15:03:15:622	 280	afc	IdleTmr	WU operation (CSearchCall::Init ID 1, operation # 10) stopped; does use network; is not at background priority
    2016-01-30	15:03:15:622	 280	afc	IdleTmr	Decremented idle timer priority operation counter to 0
    2016-01-30	15:03:15:622	2672	a88	COMAPI	>>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
    2016-01-30	15:03:15:622	2672	a88	COMAPI	  - Updates found = 0
    2016-01-30	15:03:15:622	2672	a88	COMAPI	  - WARNING: Exit code = 0x00000000, Result code = 0x8024402C
    2016-01-30	15:03:15:622	2672	a88	COMAPI	---------
    2016-01-30	15:03:15:622	2672	a88	COMAPI	--  END  

    Sunday, January 31, 2016 6:25 PM
  • The error above, 0x80072ee7, means "The server name or address could not be resolved".  So the machine is having issues resolving the WSUS server name that you specified.



    Thanks,
    -Michael Niehaus
    Director of Product Marketing, Windows Deployment, Management, and Store
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com

    • Marked as answer by Slade1040 Wednesday, April 19, 2017 3:25 PM
    Sunday, January 31, 2016 6:37 PM