locked
Clients not reporting after a move in computer groups RRS feed

  • Question

  • Hi all

    I have a 2012R2 Win. server with WSUS installed. Clients in environment are Win. 7 x64. i've configured the WSUS and everything went fine, until i moved the clients the second time in other computer groups.

    All clients that i move in another computer group suddenly stopped reporting to my WSUS and don't receive patches...

    When i kick'em out of the WSUS and clean up the client, the GPO get them in again in "Unassigned Computers". They are doing fine there, until i want to move them again in a group.

    Somebody has that issue aswell? Or does somebody have a solution?

    i'd be glad for any response!

    Wednesday, December 13, 2017 12:54 PM

Answers

All replies

  • Am 13.12.2017 schrieb Chraebeli:

    I have a 2012R2 Win. server with WSUS installed. Clients in environment are Win. 7 x64. i've configured the WSUS and everything went fine, until i moved the clients the second time in other computer groups.

    All clients that i move in another computer group suddenly stopped reporting to my WSUS and don't receive patches...

    They never receive Patches, they picked up Patches from WSUS. Did you
    restart the Clients after you move them in WSUS?

    When i kick'em out of the WSUS and clean up the client, the GPO get them in again in "Unassigned Computers". They are doing fine there, until i want to move them again in a group.

    What is the name of the Group? Did you find errormessages in
    %windir%\WindowsUpdate.log on the clients?

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Wednesday, December 13, 2017 4:57 PM
  • Hello,

    In addition, please create a new computer group for this computer.  And after move to the new computer group, you may run commands as below:

       net stop wuauserv
       REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /va /f
       rmdir /s /q %windir%\softwaredistribution
       net start wuauserv
       wuauclt.exe /resetauthorization /detectnow

    And if above issue still exist, to work around the issue, please use group policy setting named "Client side targeting" to change the computer group.

    Regards,

    Yan Li



    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    • Edited by Yan Li_ Thursday, December 14, 2017 3:09 AM
    Thursday, December 14, 2017 2:57 AM
  • "They never receive Patches, they picked up Patches from WSUS. Did you
    restart the Clients after you move them in WSUS?"

    Yap. Clients are getting restarted on a regular basis. (VMware view environment)

    "What is the name of the Group? Did you find errormessages in
    %windir%\WindowsUpdate.log on the clients?"

    Name is "Testclients Hüller". Could this be a problem? In the WindowsUpdate.log isn't an issue. Looks pretty equal to the ones, that are working. But it seems like that the "not working"-Clients getting stuck while searching for updates.

    Monday, December 18, 2017 9:05 AM
  • Hi Yan

    i'll test this in the next few days. I'll write you a feedback. Thanks for your advice.

    Monday, December 18, 2017 9:08 AM
  • Am 18.12.2017 schrieb Chraebeli:

    "They never receive Patches, they picked up Patches from WSUS. Did you
    restart the Clients after you move them in WSUS?"


    Yap. Clients are getting restarted on a regular basis. (VMware view environment)

    Try following AFTER moving in other group:

    net stop wuauserv
    rd /s /q %windir%\Softwaredistribution
    net start wuauserv

    "What is the name of the Group? Did you find errormessages in
    %windir%\WindowsUpdate.log on the clients?"



    Name is "Testclients Hüller". Could this be a problem? In the WindowsUpdate.log isn't an issue. Looks pretty equal to the ones, that are working. But it seems like that the "not working"-Clients getting stuck while searching for updates.

    Normally not, but you can try to rename in Testclients_Hueller. Did
    you configure WSUS for using Windows Registry Settings?

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Monday, December 18, 2017 8:29 PM
  • Try following AFTER moving in other group:

    net stop wuauserv
    rd /s /q %windir%\Softwaredistribution
    net start wuauserv

    I'll give that one a try tonight.

    Normally not, but you can try to rename in Testclients_Hueller. Did you configure WSUS for using Windows Registry Settings?

    i deployed the WSUS settings with a GPO, which should modify the registry of the clients if i'm not totally wrong. What other possibilities exist?

    Thanks in advance for your support.

    Tuesday, December 19, 2017 1:24 PM
  • Am 19.12.2017 schrieb Chraebeli:

    Normally not, but you can try to rename in Testclients_Hueller. Did you configure WSUS for using Windows Registry Settings?

    i deployed the WSUS settings with a GPO, which should modify the registry of the clients if i'm not totally wrong. What other possibilities exist?

    WSUS can move Clients in Groups automatically. This setting call
    Client Side Targeting:
    https://technet.microsoft.com/en-us/library/cc708574(v=ws.10).aspx

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Tuesday, December 19, 2017 8:05 PM
  • Because we have a lot of updates to distribute and the virtualization hosts are pretty loaded, i need to load balance by myself without using client side targeting. Would I be more succesfull with client side targeting?
    Wednesday, December 20, 2017 2:14 PM
  • UPDATE: i tried both of your suggestions yesterday at 10 pm. i have problems with 4 Clients, so i did 2x2.

    Until now, none of the clients reported to the WSUS Server, so the problem still exists and no updates could have been installed.

    I moved some other clients from another group in same the group as the "bad" ones are and the keep working properly. So i needs to be a client issue in my opinion...

    Any further ideas?

    Wednesday, December 20, 2017 2:17 PM
  • Am 20.12.2017 schrieb Chraebeli:

    Because we have a lot of updates to distribute and the virtualization hosts are pretty loaded, i need to load balance by myself without using client side targeting. Would I be more succesfull with client side targeting?

    If Client side targeting or not, your clients must connect to WSUS and
    download offered updates.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Wednesday, December 20, 2017 5:14 PM
  • Hello,

    If the issue only occur to 4 clients, please troubleshoot this issue from the client side. Please check whether the client is reported to your WSUS server, and check Windowsupdate.log on those clients. 

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, December 21, 2017 6:32 AM
  • On all 4 clients i receive the following error in the WindowsUpdate.log:

     WARNING: Failed to filter search results, error = 0x8024000B

    I had this one before. Windows Update Troubleshooter and various scripts couldn't have fixed it... The only way until now was to delete the client out of the WSUS server and do a /resetauthorization.

    Any further ideas?

    On one client, i have some additional errors:

    2017-12-20 04:52:19:823 940 cdc PT WARNING: GetCookie_WithRecovery failed : 0x8024000b
    2017-12-20 04:52:19:823 940 cdc PT WARNING: RefreshCookie failed: 0x8024000b
    2017-12-20 04:52:19:823 940 cdc PT WARNING: RefreshPTState failed: 0x8024000b
    2017-12-20 04:52:19:823 940 cdc PT WARNING: PTError: 0x8024000b
    2017-12-20 04:52:19:823 940 cdc Report WARNING: Reporter failed to upload events with hr = 8024000b.
    2017-12-20 04:52:19:855 940 1290 Report CWERReporter finishing event handling. (00000000)
    2017-12-20 04:52:20:261 940 1290 Service *********
    2017-12-20 04:52:20:261 940 1290 Service **  END  **  Service: Service exit [Exit code = 0x240001]

    Could this eventually be an issue with the Windows Update Agent? Would i be a good idea to reinstall it?

    Thursday, December 21, 2017 9:15 AM
  • Am 21.12.2017 schrieb Chraebeli:

    Could this eventually be an issue with the Windows Update Agent? Would i be a good idea to reinstall it?

    Download the latest WU Agent:
    https://support.microsoft.com/en-us/help/949104/how-to-update-the-windows-update-agent-to-the-latest-version
    After Download install, reboot and try again.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    • Marked as answer by Chraebeli Tuesday, January 9, 2018 8:30 AM
    Thursday, December 21, 2017 5:07 PM
  • Hi Winfried

    After Reinstalling, everything works as expected.

    Thank you for your help and sorry for the late response!

    Tuesday, January 9, 2018 9:01 AM
  • Am 09.01.2018 schrieb Chraebeli:

    After Reinstalling, everything works as expected.

    Thank you for your help and sorry for the late response!

    Great! Thanks for response. :)

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Tuesday, January 9, 2018 6:15 PM