none
WSUS 3.2, Windows update 80244007 and Server Error in '/ClientWebService' Application.

    Question

  • One new install, one previous install, two different servers (server 2008 r2) full updates, WSUS 3.2.7600.226 

     

    On both servers, WSUS installs and operates properly until I try to have a client update from one of those servers, I am met with Windows update Error code 80244007 which I found to be some SOAP error, so I check the windowsupdate.log and here is the relevant part

    2011-06-08 11:10:21:892 1076 ab0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2011-06-08 11:10:21:892 1076 ab0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://servername:8530/ClientWebService/client.asmx
    2011-06-08 11:10:21:892 1076 ab0 PT WARNING: Cached cookie has expired or new PID is available
    2011-06-08 11:10:21:892 1076 ab0 EP Got WSUS SimpleTargeting URL: "http://servername.com:8530"
    2011-06-08 11:10:21:892 1076 ab0 PT Initializing simple targeting cookie, clientId = 28dc3c16-ed92-49bb-93ed-f9b3cf5a7b23, target group = dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBhdzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26ZqQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlhXXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg, DNS name = computername.domain
    2011-06-08 11:10:21:892 1076 ab0 PT   Server URL = http://servername:8530/SimpleAuthWebService/SimpleAuth.asmx
    2011-06-08 11:10:21:908 1076 ab0 WS WARNING: Nws Failure: errorCode=0x803d0013
    2011-06-08 11:10:21:908 1076 ab0 WS WARNING: The body of the received message contained a fault.
    2011-06-08 11:10:21:908 1076 ab0 WS WARNING: Soap fault info:
    2011-06-08 11:10:21:908 1076 ab0 WS WARNING: reason: Fault occurred
    2011-06-08 11:10:21:908 1076 ab0 WS WARNING: code: Server
    2011-06-08 11:10:21:908 1076 ab0 WS WARNING: detail: <detail><ErrorCode>InternalServerError</ErrorCode><Message></Message><ID>5423d13e-9a9f-4e2d-b60d-d2b33ff91801</ID><Method>"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"</Method></detail>
    2011-06-08 11:10:21:908 1076 ab0 WS FATAL: OnCallFailure(hrCall, m_error) failed with hr=0x80244007
    2011-06-08 11:10:21:908 1076 ab0 WS FATAL: NwsCallWithProxyRetry<Functor>( Functor(_clientId, _targetGroupName, _dnsName, &_result)) failed with hr=0x80244007
    2011-06-08 11:10:21:908 1076 ab0 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244007
    2011-06-08 11:10:21:908 1076 ab0 PT WARNING: PopulateAuthCookies failed: 0x80244007
    2011-06-08 11:10:21:908 1076 ab0 PT WARNING: RefreshCookie failed: 0x80244007
    2011-06-08 11:10:21:908 1076 ab0 PT WARNING: RefreshPTState failed: 0x80244007
    2011-06-08 11:10:21:908 1076 ab0 PT WARNING: Sync of Updates: 0x80244007
    2011-06-08 11:10:21:908 1076 ab0 PT WARNING: SyncServerUpdatesInternal failed: 0x80244007
    2011-06-08 11:10:21:908 1076 ab0 Agent   * WARNING: Failed to synchronize, error = 0x80244007
    2011-06-08 11:10:21:923 1076 ab0 Agent   * WARNING: Exit code = 0x80244007
    2011-06-08 11:10:21:923 1076 ab0 Agent *********
    2011-06-08 11:10:21:923 1076 ab0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2011-06-08 11:10:21:923 1076 ab0 Agent *************
    2011-06-08 11:10:21:923 1076 ab0 Agent WARNING: WU client failed Searching for update with error 0x80244007
    2011-06-08 11:10:21:923 1076 16ac AU >>##  RESUMED  ## AU: Search for updates [CallId = {6EA81C6B-6497-4565-9AFE-C7C7568EBFE7}]
    2011-06-08 11:10:21:923 1076 16ac AU   # WARNING: Search callback failed, result = 0x80244007
    2011-06-08 11:10:21:923 1076 16ac AU   # WARNING: Failed to find updates with error code 80244007
    2011-06-08 11:10:21:923 1076 16ac AU #########
    2011-06-08 11:10:21:923 1076 16ac AU ##  END  ##  AU: Search for updates [CallId = {6EA81C6B-6497-4565-9AFE-C7C7568EBFE7}]
    2011-06-08 11:10:21:923 1076 16ac AU #############
    2011-06-08 11:10:21:923 1076 16ac AU Successfully wrote event for AU health state:0
    2011-06-08 11:10:21:923 1076 16ac AU AU setting next detection timeout to 2011-06-08 23:10:21
    2011-06-08 11:10:21:923 1076 16ac AU Setting AU scheduled install time to 2011-06-08 19:00:00
    2011-06-08 11:10:21:923 1076 16ac AU Successfully wrote event for AU health state:0
    2011-06-08 11:10:21:939 1076 16ac AU Successfully wrote event for AU health state:0
    2011-06-08 11:10:26:930 1076 ab0 Report REPORT EVENT: {5D4CDA63-4097-4A6A-8620-86A0B754461E} 2011-06-08 11:10:21:923-0700 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007.
    2011-06-08 11:10:26:930 1076 ab0 Report CWERReporter finishing event handling. (00000000)

    (removed server names)

    When I try to access

    http://servername:8530/ClientWebService/client.asmx

    I am met with the error seen here

    http://img.photobucket.com/albums/v310/fishy80/NewBitmapImage-2.jpg

     

    Any help would be greatly appreciated

    Wednesday, June 08, 2011 6:07 PM

Answers

  • 2011-06-08 11:10:21:892 1076 ab0 PT Initializing simple targeting cookie, clientId = 28dc3c16-ed92-49bb-93ed-f9b3cf5a7b23,
    target group = dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1
    uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBh
    dzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26Z
    qQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0
    GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlh
    XXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg,
    DNS name = computername.domain

    Talk to me about how you created your WSUS Target Groups, how you configured the server to manage groups, and how you configured the machines to be assigned to a target group.

    The fundamental problem here is your Target Group name is invalid.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Thursday, June 09, 2011 6:47 PM
    Moderator

All replies

  • 2011-06-08 11:10:21:892 1076 ab0 PT Initializing simple targeting cookie, clientId = 28dc3c16-ed92-49bb-93ed-f9b3cf5a7b23,
    target group = dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1
    uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBh
    dzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26Z
    qQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0
    GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlh
    XXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg,
    DNS name = computername.domain

    Talk to me about how you created your WSUS Target Groups, how you configured the server to manage groups, and how you configured the machines to be assigned to a target group.

    The fundamental problem here is your Target Group name is invalid.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Thursday, June 09, 2011 6:47 PM
    Moderator
  • One server was already set up, and most of the computers have not responded to the server in hundreds of days

    I would suggest that this information, combined with the log entry above, presents a pretty strong indication that the database for this WSUS server is corrupted beyond the point of recovery.

    I would suggest stripping this machine and reinstalling a fresh instance of WSUS.

    but I fail to see how the group membership causes the client to be unable to update

    The INVALID group membership name is what is causing the detection error. Being able to identify the actual group membership(s) is core requirement of being able to successfully evaluate update approvals from the WSUS server. If the group structure is corrupted or invalid, detections will fail, as they are doing here. If the detection event is failing, the client cannot possibly have a hope of downloading or installing any updates.

    Btw... the client log you posted . . . what OS and what version of the WUAgent is on that client system?

     

     


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, June 10, 2011 9:31 PM
    Moderator
  • The Client log was from a windows 7 machine, and I'm not able to find the WUAgent version.

     

    one thing to keep in mind though, same error on both servers, and one is a fresh install, with no groups set up, its all unassigned... I doubt its corrupted since its a new install. Possibly the older one is corrupted... but that wouldn't explain the problem with the new one.

     

     

    ----------------------------------

     

    Update - I ran the WSUS Client Diagnostic, and it shows my WUAgent version as: Wuaueng.dll version 7.7.7600.16385 and then it says "This version is wsus 2.0" although when I download the newest Wuagent installer from MS download center it says its already installed and will not install. and I have tried the "fix it" which resets windows updates, using the aggressive option, nothing has changed.

    Monday, June 13, 2011 8:29 PM
  • The Client log was from a windows 7 machine, and I'm not able to find the WUAgent version.

    Restart the Windows Update service, wait 15 minutes, and post the resulting log entries from the WindowsUpdate.log.

     


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, June 14, 2011 4:07 PM
    Moderator
  • You guys should allow code boxes on this forum
    It does.
    2011-06-15 17:17:48:537 1136 744 Agent   * Target group: dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBhdzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26ZqQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlhXXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg

    Looks like either the GPO that is assigning the target group is corrupted, or the targeting cooking on the client is corrupted.

    Please export the registry key at HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate and post.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, June 17, 2011 1:14 AM
    Moderator
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    "TargetGroup"="dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBhdzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26ZqQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlhXXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg"
    "TargetGroupEnabled"=dword:00000001
    "WUServer"="http://servername.com:8530"
    "WUStatusServer"="http://servername.com:8530"
    "ElevateNonAdmins"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    "UseWUServer"=dword:00000001
    "NoAutoRebootWithLoggedOnUsers"=dword:00000001
    "AutoInstallMinorUpdates"=dword:00000001
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000004
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:0000000c
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000008
    "RebootRelaunchTimeoutEnabled"=dword:00000001
    "RebootRelaunchTimeout"=dword:0000001e
    "AUPowerManagement"=dword:00000001

    Oh oops lol, thought the html button was the same button as that code box button. XD

     

    Thats the registry entry from the client computer



    Friday, June 17, 2011 3:55 PM
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    
    "TargetGroup"="dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBhdzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26ZqQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlhXXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg"
    
    "TargetGroupEnabled"=dword:00000001
    
    

    Please inspect the Group Policy Object that is being used to apply this policy and explain how this value for "TargetGroup" has been defined!?

    If you cannot identify a reasonable explanation, then DELETE the GPO and create it new, from scratch.

    As I've said *THREE* times now.. it is an INVALID VALUE -- and when you FIX this value, your errors will likely go away.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Saturday, June 18, 2011 4:32 PM
    Moderator
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    
    "TargetGroup"="dmr4b8tLrnovu1owj9YyRpZ4ox82AFiejGKms3020GKT4GPjngHG0mjh5d8dp/tSuTXyvMitkTWjMa4Yu6tWNhWKVaBe1uOEFBTc72pCEezQqV0yAeTVbq4CNtU/qb/GFIWFUc7qMDp7IV2pAyoTuySg/w2DPNA4BYDx3u+qRL0vFTPCxMfK2iCEvMPqIdQBGBhdzbTWjg7rijiXZ5jhd/E2s5ndPOvlDLeWZw8Xdbgycd7glSOzkkLpjvAkcOi4l24dGIPGoXE6mVp+6zIMTIuM6cGsHP9VwaSinhau2Dg26ZqQXmE6/neCmaFmqGZmoi+Fur3RC3xcx3xb/4OEGgFWBO13lUZ9VB0z0yZdB9xbpgkwxSKTKiJ2tpsSPz9K8rW+BCNvVYuyIyyDxo0GDsFl/CjkcMT3MmwFQ+2CbXJA1kP6NcvyvkHZqzZguONSN8uxk+IHFKU/bPDW0Os87wTnIwt+8XGBqWqJWaQgZLmbtN8ipGg3hlhXXb36CkFRY2XDrWUshbjn81SGb0FHIS98tHvXnZgtch8EszFW7o7Gau443R5QMCFkIeo9b3aurj2RQEq1pEN1hoBbZ353cjy86aRBrNpg"
    
    "TargetGroupEnabled"=dword:00000001
    
    

    Please inspect the Group Policy Object that is being used to apply this policy and explain how this value for "TargetGroup" has been defined!?

    If you cannot identify a reasonable explanation, then DELETE the GPO and create it new, from scratch.

    As I've said *THREE* times now.. it is an INVALID VALUE -- and when you FIX this value, your errors will likely go away.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com


    I was just responding doing what you said, I can understand that being the issue, however I'm not the person who created the GPO, that server and the GPO's associated with it were both already set up.

     

    I have checked RSOP.msc Gpedit.msc and editing the GPO for wsus directly, but every setting for "enable client-side targeting" is "Not configured"  Also, I removed my computer from the target group on the wsus server itself, and found no change in behavior on this pc.

    I then finally had the chance to check another system and it appears to be working fine connected to the same server. also without client-side targeting configured



    Monday, June 20, 2011 8:55 PM
  • Deleted the registry values associated with that target group. re-detected wsus server, all working fine on this computer now.
    Tuesday, June 21, 2011 12:38 AM
  •  but every setting for "enable client-side targeting" is "Not configured" 

    That may well be the case.

    Perhaps at one time the policy was enabled and had a bad value configured in it. Those settings were applied to this (and perhaps other) clients.

    Merely setting the option back to "Not Configured" will not reset the registry values originally created by such a GPO, so perhaps what you have here is an orphaned configuration.

    If you are not using Client-Side Targeting, then the proper setting for that option is DISABLED. Please set all of your WSUS GPOs to DISABLED for Enable client-side targeting and perform a policiy refresh, which should clear the bad values from the registry and restore normal functioning for this client.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, June 21, 2011 5:47 PM
    Moderator
  • Deleted the registry values associated with that target group. re-detected wsus server, all working fine on this computer now.


    This is another way to fix the problem . . . but without confirming that there was no GPO source for this setting, it might have been an interim/temporary 'fix' at best.

    Now that you have confimed that there is no source GPO for that setting, deleting the registry values is an appropriate action; however, you should still set the GPOs to DISABLED for Enable client-side targeting if your intent is to use server-side targeting.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, June 21, 2011 5:49 PM
    Moderator
  • I found that my target group would not update.. I was recieving this:

    F4VUTr7RrZC9JsOoNGIQ/9x9qyi1OI3Tfqg8a0DXrhsgfmnsR7opmIE2IwVrsBbG3hl0vl35WZbBonYwEqf8n5sXyCqYLP3xrOgz2QGU0Wi2RnY2NvkePe1IEfZR7GsrjYkrvDPFMg7xXRGElNVlcyBWXen31UWgQt64fT5snvV93dbAyqjfXJEu45YxLK9r+BQu3bmJPRhIcpiA5gMfnIAzx7lQsyNgUv0b1rsdAzQOoSf/toOnoXnIKP9YZyAQ2ixzCrd1Vt/10Bjw39wEIYdfXqhrPop75tPkbE0JuWnazuu8jKdXUAPoZpsnFhDAihUfGIUA4+P+Zo0kXbjB5G1A/9nJQtjWbr0XGqLiM4M938+/mOGJTAqs8XJvAA3ShmBCYI42bK7S1p1GKJ8N3G4MxQ9HZ6tgLjRno9ygKHFc0aXeFbtMSoO6ccGaQBNuAB5cn24WnPdxJtRvx3bL1ZDePPsmgnt55Kz+SKujEHKtTRW6WrTXUeo7mFnhQiXZWXYgxDz1+g1HEjkJwA5bUiuRdqmjCJEB7esV34YxueGnKs6AaM4mAaRoyMIaaAgk2lT7jdRj9FxnKD0DlfP1e1K/xCBTmaAC

     

    I tried a gpupdate /force and it failed on both the user and computer.  Looking at the IPstack I noticed I had the IP for my DNS off.  I corrected it on the DC and reran a gpupdate on the client.  I saw in the registry that the group updated and in the windowsupdate.log the target group has now changed to Target group: (Unassigned Computers) as I expected.

     

    Prior history:

    small learning network

    ran beta of Intune for ease of management and ability to patch multiple machines both localy and remotly.

     


    ** UPDATE ***

    afteR CONFIGURING dns i DID THE FOLLOWING.

    1.) released and renewed the IPstack (ipconfig /release  ... ipconfig /renew)

    2.) net stop wuauserv

    3.) deleted windowsupdate.log file located at %windir%\windowsupdate.log

    4.) net start wuauserv

    5.) wuauclt.exe /reauthorization /detectnow

    and all of this worked for me.

    Friday, August 19, 2011 3:50 AM