none
WSUS updates not going to Clients " Windows 7".

    Question

  • Recently I have noticed my updates are not going out to my windows 7 clients.

    They have been working fine up until August.

    When pushing them from WSUS it shows successfully went however they are not going.

    I have tried stripping my susclientID and "re-pushing" the updates however to no success.

    I have also run the diags client in which it would show me "pass" or "none" and there seem to be no problems reaching the server.

    I am able to ping the client from the server and vice versa.

    At this point I am completely at a loss.

    Any help would be appreciated.

    Below is the windowsupdate.log file in which i have updated just this morning.

    Thanks.

    vendredi 23 novembre 2012 12:45

Réponses

  • Recently I have noticed my updates are not going out to my windows 7 clients.

    I'm not quite grasping why you deleted all of your responses from the original thread, and started a new one...

    I have tried stripping my susclientID and "re-pushing" the updates however to no success.

    My guess is that whatever you're doing to achieve this objective ... the logon script deleted from the previous thread??? ... it's not working. Most likely the 'IDDelete' marker is in the client's registry from a previous execution of the logon script, so the values are not being deleted.

    Another possibility is that the logged on user doesn't have registry write permissions --- such is the flaw in running this as a LOGON script -- it should be executed as a STARTUP script.

    Or, as I noted in the original thread.. it ought not be run in either startup or logon scripts, but rather the defective business process that is allowing the duplicates to be created in the first place should be identified and fixed.

    Below is the windowsupdate.log file in which i have updated just this morning.

    2012-11-23 08:13:52:924 1032 1a58 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2012-11-23 08:13:52:924 1032 1a58 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusServer/ClientWebService/client.asmx

    2012-11-23 08:13:52:956 1032 1a58 PT WARNING: Cached cookie has expired or new PID is available

    2012-11-23 08:13:52:956 1032 1a58 PT Initializing simple targeting cookie, clientId = 91cf4317-e10b-4c68-8ee8-684776435f1e, target group = , DNS name = pcname.domain.local

    2012-11-23 08:13:52:956 1032 1a58 PT Server URL = http://wsusServer/SimpleAuthWebService/SimpleAuth.asmx

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: SOAP Fault: 0x00012c

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: faultstring:Fault occurred

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: ErrorCode:ConfigChanged(2)

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: Message:(null)

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: ID:94d74e99-e1e7-4f67-8aae-25e416ab60b7 2012-11-23 08:13:53:019 1032 1a58 PT WARNING: Cached cookie has expired or new PID is available

    2012-11-23 08:13:53:019 1032 1a58 PT Initializing simple targeting cookie, clientId = 91cf4317-e10b-4c68-8ee8-684776435f1e, target group = , DNS name = pcname.domain.local

    This log snippet shows very clear evidence of an issue that is most commonly caused by a duplicate SusClientID.

    So rather than rely on the script , just go the client, delete the SusClientID and SusClientIDValidation registry values and then run wuauclt /resetauthorization /detectnow from the command line of the client and observe the results.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin


    vendredi 23 novembre 2012 18:07
    Modérateur

Toutes les réponses

  • Recently I have noticed my updates are not going out to my windows 7 clients.

    I'm not quite grasping why you deleted all of your responses from the original thread, and started a new one...

    I have tried stripping my susclientID and "re-pushing" the updates however to no success.

    My guess is that whatever you're doing to achieve this objective ... the logon script deleted from the previous thread??? ... it's not working. Most likely the 'IDDelete' marker is in the client's registry from a previous execution of the logon script, so the values are not being deleted.

    Another possibility is that the logged on user doesn't have registry write permissions --- such is the flaw in running this as a LOGON script -- it should be executed as a STARTUP script.

    Or, as I noted in the original thread.. it ought not be run in either startup or logon scripts, but rather the defective business process that is allowing the duplicates to be created in the first place should be identified and fixed.

    Below is the windowsupdate.log file in which i have updated just this morning.

    2012-11-23 08:13:52:924 1032 1a58 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2012-11-23 08:13:52:924 1032 1a58 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusServer/ClientWebService/client.asmx

    2012-11-23 08:13:52:956 1032 1a58 PT WARNING: Cached cookie has expired or new PID is available

    2012-11-23 08:13:52:956 1032 1a58 PT Initializing simple targeting cookie, clientId = 91cf4317-e10b-4c68-8ee8-684776435f1e, target group = , DNS name = pcname.domain.local

    2012-11-23 08:13:52:956 1032 1a58 PT Server URL = http://wsusServer/SimpleAuthWebService/SimpleAuth.asmx

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: SOAP Fault: 0x00012c

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: faultstring:Fault occurred

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: ErrorCode:ConfigChanged(2)

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: Message:(null)

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"

    2012-11-23 08:13:52:987 1032 1a58 PT WARNING: ID:94d74e99-e1e7-4f67-8aae-25e416ab60b7 2012-11-23 08:13:53:019 1032 1a58 PT WARNING: Cached cookie has expired or new PID is available

    2012-11-23 08:13:53:019 1032 1a58 PT Initializing simple targeting cookie, clientId = 91cf4317-e10b-4c68-8ee8-684776435f1e, target group = , DNS name = pcname.domain.local

    This log snippet shows very clear evidence of an issue that is most commonly caused by a duplicate SusClientID.

    So rather than rely on the script , just go the client, delete the SusClientID and SusClientIDValidation registry values and then run wuauclt /resetauthorization /detectnow from the command line of the client and observe the results.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin


    vendredi 23 novembre 2012 18:07
    Modérateur
  • Can you please please please remove the server name and the <deleted> dns name please.

    please "asterix" out in case this will help people. I just been informed I cannot have our name associated outside of our company for business.

    Please and thanks.  I will now delete this post as I understand you can read them and again, thank you for your help. Your solution DID in fact work.

    I will be happy to obfuscate the identifiers of your systems. :)

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    vendredi 23 novembre 2012 22:08
    Modérateur