none
Clients are downloading updates but not installing and rebooting at set time

    Question

  • I am using WSUS 3.0 SP2 on my domain and a week ago I changed the time on my GPO to update the clients. After that the clients stopped updating and rebooting like they were doing before. I haven't modified anything  else in my GPO other than the time the clients are to install the updates and they worked fine before. The log from one of the clients is below. The icon in the system tray shows up that updates are available and I can see in the event logs that the client downloaded the updates. On this client I tried de-registering the dll's and re-registering them. I checked all my settings in GPO and toggled them but no luck. 

    2013-01-29 13:26:32:661 784 3a8 AU Triggering AU detection through DetectNow API
    2013-01-29 13:26:32:661 784 3a8 AU Triggering Online detection (non-interactive)
    2013-01-29 13:26:32:661 784 30c AU #############
    2013-01-29 13:26:32:661 784 30c AU ## START ##  AU: Search for updates
    2013-01-29 13:26:32:661 784 30c AU #########
    2013-01-29 13:26:32:661 784 30c AU <<## SUBMITTED ## AU: Search for updates [CallId = {411E6EDB-EA3E-49DA-A88F-F35E7618184A}]
    2013-01-29 13:26:32:661 784 a4c Agent *************
    2013-01-29 13:26:32:661 784 a4c Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-01-29 13:26:32:661 784 a4c Agent *********
    2013-01-29 13:26:32:661 784 a4c Agent  * Online = Yes; Ignore download priority = No
    2013-01-29 13:26:32:661 784 a4c Agent  * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    2013-01-29 13:26:32:661 784 a4c Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-01-29 13:26:32:661 784 a4c Agent  * Search Scope = {Machine}
    2013-01-29 13:26:34:414 784 a4c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2013-01-29 13:26:34:424 784 a4c Misc Microsoft signed: Yes
    2013-01-29 13:26:36:938 784 a4c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2013-01-29 13:26:36:948 784 a4c Misc Microsoft signed: Yes
    2013-01-29 13:26:36:958 784 a4c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2013-01-29 13:26:36:958 784 a4c Misc Microsoft signed: Yes
    2013-01-29 13:26:36:968 784 a4c Setup ***********  Setup: Checking whether self-update is required  ***********
    2013-01-29 13:26:36:968 784 a4c Setup  * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2013-01-29 13:26:36:968 784 a4c Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:968 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:968 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:968 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:968 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:968 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2013-01-29 13:26:36:978 784 a4c Setup  * IsUpdateRequired = No
    2013-01-29 13:26:39:171 784 a4c PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-01-29 13:26:39:171 784 a4c PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lab-wsus.pdxlab.net/ClientWebService/client.asmx
    2013-01-29 13:26:39:301 784 a4c PT WARNING: Cached cookie has expired or new PID is available
    2013-01-29 13:26:39:301 784 a4c PT Initializing simple targeting cookie, clientId = cc21168f-b3e7-4739-b24c-dc22b3d5b99a, target group = , DNS name = lab-appscan02.pdxlab.net
    2013-01-29 13:26:39:301 784 a4c PT  Server URL = http://servername/SimpleAuthWebService/SimpleAuth.asmx
    2013-01-29 13:26:40:483 784 a4c PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2013-01-29 13:26:40:483 784 a4c PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lab-wsus.pdxlab.net/ClientWebService/client.asmx
    2013-01-29 13:26:42:897 784 a4c Agent  * Added update {4F26C3BA-B457-410C-B0C7-4481BED14E45}.200 to search result
    2013-01-29 13:26:42:897 784 a4c Agent  * Added update {A5F1C0E5-16A2-4503-9F7A-F54D1AAD38F0}.201 to search result
    2013-01-29 13:26:42:897 784 a4c Agent  * Added update {8BCDF9DC-3C05-4C6D-A9D9-524233E2F7B5}.201 to search result
    2013-01-29 13:26:42:897 784 a4c Agent  * Added update {8B17286C-09B3-42CE-9AED-13222FEE8F25}.203 to search result
    2013-01-29 13:26:42:897 784 a4c Agent  * Added update {5938913D-4468-4E05-A320-EC6EA07AA389}.201 to search result
    2013-01-29 13:26:42:897 784 a4c Agent  * Added update {FDBEF574-459E-4C57-A840-4E66EE7EC9F2}.202 to search result
    2013-01-29 13:26:42:897 784 a4c Agent  * Added update {5D543FC2-04E5-4A4E-AF2B-7F05C1F055F2}.200 to search result
    2013-01-29 13:26:42:897 784 a4c Agent  * Found 7 updates and 66 categories in search; evaluated appl. rules of 775 out of 1589 deployed entities
    2013-01-29 13:26:42:957 784 a4c Agent *********
    2013-01-29 13:26:42:957 784 a4c Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-01-29 13:26:42:957 784 a4c Agent *************
    2013-01-29 13:26:42:967 784 458 AU >>##  RESUMED  ## AU: Search for updates [CallId = {411E6EDB-EA3E-49DA-A88F-F35E7618184A}]
    2013-01-29 13:26:42:967 784 458 AU  # 7 updates detected
    2013-01-29 13:26:42:967 784 458 AU #########
    2013-01-29 13:26:42:967 784 458 AU ##  END  ##  AU: Search for updates [CallId = {411E6EDB-EA3E-49DA-A88F-F35E7618184A}]
    2013-01-29 13:26:42:967 784 458 AU #############
    2013-01-29 13:26:42:967 784 458 AU Featured notifications is disabled.
    2013-01-29 13:26:42:967 784 458 AU AU setting next detection timeout to 2013-01-30 05:02:46
    2013-01-29 13:26:47:964 784 a4c Report REPORT EVENT: {B39BFC90-3BDD-4603-9C22-7A88FF698A52} 2013-01-29 13:26:42:957-0800 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 7 updates.
    2013-01-29 13:26:47:964 784 a4c Report REPORT EVENT: {F9E1179B-8A0A-41CA-94CC-EF2B21C1BA6D} 2013-01-29 13:26:42:957-0800 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2013-01-29 13:29:12:040 784 a4c Report Uploading 2 events using cached cookie, reporting URL = http://lab-servername/ReportingWebService/ReportingWebService.asmx
    2013-01-29 13:29:12:050 784 a4c Report Reporter successfully uploaded 2 events.

    mardi 29 janvier 2013 21:37

Toutes les réponses

  • Hi,

    Pls run the RSOP or gpresult on the client machine to check whether the policy has been actually applied.If possible,post your WSUS setting here for further troubleshooting.

    Regards,

    Clarence

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    mercredi 30 janvier 2013 02:44
  • I just implemented a new default domain GPO a few months back. I didn't realize it had windows update settings in it that were applying to the clients. 

    This is from the client

    Configure Automatic Updates Enabled Default Domain Policy - New
    Specify intranet Microsoft update service location Enabled z_WSUS Patching
    Reschedule Automatic Updates scheduled installations Enabled z_WSUS Patching
    No auto-restart with logged on users for scheduled automatic updates installations Disabled z_WSUS Patching
    Automatic Updates detection frequency Enabled z_WSUS Patching
    Allow Automatic Updates immediate installation Enabled z_WSUS Patching
    Delay Restart for scheduled installations Enabled z_WSUS Patching
    Re-prompt for restart with scheduled installations Enabled zWSUS Patching
    Allow non-administrators to receive update notifications Enabled z_WSUS Patching
    Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box Disabled Default Domain Policy - New

    This is the WSUS Patching GPO

    Setting State Comment
    Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box Not configured No
    Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box Not configured No
    Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates Not configured No
    Configure Automatic Updates Enabled No
    Specify intranet Microsoft update service location Enabled No
    Automatic Updates detection frequency Enabled No
    Allow non-administrators to receive update notifications Enabled No
    Turn on Software Notifications Not configured No
    Allow Automatic Updates immediate installation Enabled No
    Turn on recommended updates via Automatic Updates Not configured No
    No auto-restart with logged on users for scheduled automatic updates installations Disabled No
    Re-prompt for restart with scheduled installations Enabled No
    Delay Restart for scheduled installations Enabled No
    Reschedule Automatic Updates scheduled installations Enabled No
    Enable client-side targeting Not configured No
    Allow signed updates from an intranet Microsoft update service location Not configured No

    This is whats in the default domain policy

    Setting State Comment
    Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box Disabled No
    Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box Not configured No
    Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates Not configured No
    Configure Automatic Updates Enabled No
    Specify intranet Microsoft update service location Not configured No
    Automatic Updates detection frequency Not configured No
    Allow non-administrators to receive update notifications Not configured No
    Turn on Software Notifications Not configured No
    Allow Automatic Updates immediate installation Not configured No
    Turn on recommended updates via Automatic Updates Not configured No
    No auto-restart with logged on users for scheduled automatic updates installations Not configured No
    Re-prompt for restart with scheduled installations Not configured No
    Delay Restart for scheduled installations Not configured No
    Reschedule Automatic Updates scheduled installations Not configured No
    Enable client-side targeting Not configured No
    Allow signed updates from an intranet Microsoft update service location Not configured No

    mercredi 30 janvier 2013 03:50
  • Last night I removed the settings from the default domain policy for windows updates and let the WSUS policy handle the update setting and got a different error in the windowsupdate.log file. 

    FATAL: CAUClient::Launch failed, error = 0x80070057

    mercredi 30 janvier 2013 16:25
  • Last night I removed the settings from the default domain policy for windows updates and let the WSUS policy handle the update setting and got a different error in the windowsupdate.log file. 

    FATAL: CAUClient::Launch failed, error = 0x80070057

    From http://inetexplorer.mvps.org/archive/windows_update_codes.htm

    One or more arguments are not valid error - Invalid proxy server name was specified in the user’s IE settings and hence WinhttpSetProxySettings call fails with E_INVALIDARG error. BITS puts the job in TRANSIENT_ERROR with the same error code. For ex, if the proxy server is set to http://foo/bar/proxy.pac, this error will be seen. This error is also seen when credentials are supplied such that scheme is not NTLM/Negotiate, but username/password is NULL, since that is not valid (WinhttpSetCredentials fails with E_INVALIDARG. BITS 1.5 puts the job into ERROR state with BG_E_INVALID_RESPONSE in the above 2 cases, because of error code mapping E_INVALIDARG is always mapped to (BG_E_INVALID_SERVER_RESPONSE)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    samedi 25 mai 2013 15:46
  • I am using WSUS 3.0 SP2 on my domain and a week ago I changed the time on my GPO to update the clients. After that the clients stopped updating and rebooting like they were doing before.

    2013-01-29 13:26:36:968 784 a4c Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226

    2013-01-29 13:26:39:171 784 a4c PT +++++++++++ PT: Synchronizing server updates +++++++++++

    2013-01-29 13:26:39:171 784 a4c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lab-wsus.pdxlab.net/ClientWebService/client.asmx

    2013-01-29 13:26:39:301 784 a4c PT Server URL = http://servername/SimpleAuthWebService/SimpleAuth.asmx

    2013-01-29 13:26:42:897 784 a4c Agent  * Found 7 updates and 66 categories in search; evaluated appl. rules of 775 out of 1589 deployed entities

    2013-01-29 13:29:12:040 784 a4c Report Uploading 2 events using cached cookie, reporting URL = http://lab-servername/ReportingWebService/ReportingWebService.asmx
    2013-01-29 13:29:12:050 784 a4c Report Reporter successfully uploaded 2 events.

    This client is working perfectly ... although I do note that it's running the v7.4 WUAgent, which also tells me that the latest patches have not been applied to the WSUS Server at (OOPS!)... which is the WSUS server... the client detected 7 available updates from lab-wsus.pdxlab.net, but then tried to report to lab-servername. And in looking further I then found a third reference to a different servername -- servername. Now, in reality, the v7.4 WUAgent cannot actually have a separate reporting server from an update server, so I do find this most curious.

    As far as updating and rebooting.... I note that the WUAgent did not do anything with those seven update detected, so there's nothing that can be evaluated on that question.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    samedi 25 mai 2013 15:56
  • I just implemented a new default domain GPO a few months back. I didn't realize it had windows update settings in it that were applying to the clients.

    Which is exactly the reason why the Default Domain Policy should never be used for customized settings. Separate GPOs should always be created.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    samedi 25 mai 2013 15:59