locked
Delete client computer from wsus when wsus showing up error node RRS feed

  • Question

  • Hi everyone. I got problem with my wsus (win2012R2) wsus version 6.3.9600.18838 I noticed few days ago that when i click all computers in my wsus, console start crush and gets error node reset...

    But when i use "search" .Then These computers are visible except one. When i serch for this one computer console always crush.

    The problem is that i cannot remove this problematic computer from wsus because of crush. Any sugesstions?

    How to solve this case? Or maybe a way to remove this computer from wsus DB ?

    Thursday, May 30, 2019 8:15 AM

All replies

  • Hi,
      

    Please try the following Powershell script for client computer removal:
      

    (Get-WsusServer).GetComputerTargetByName('SYSTEM FQDN').Delete()

       
    Hope the above can help you.
       

    Regards,
    Yic


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

    Thursday, May 30, 2019 9:39 AM
  • should i change 'SYSTEM FQDN' and put there computer name which i want delete?
    Thursday, May 30, 2019 10:13 AM
  • Am 30.05.2019 schrieb g-podlecki:

    Hi everyone. I got problem with my wsus (win2012R2) wsus version 6.3.9600.18838 I noticed few days ago that when i click all computers in my wsus, console start crush and gets error node reset...

    Pls read this Article and follow.
    https://www.404techsupport.com/2016/03/21/iis-wsus-private-memory/
    After you have set this settings, reboot the WSUS. If it is working
    now, pls use Server Cleanup Wizard.

    Winfried


    WSUS Package Publisher:
    https://github.com/DCourtel/Wsus_Package_Publisher
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home
    GP-PACK - PRIVACY AND TELEMETRIE: http://www.gp-pack.com/

    Thursday, May 30, 2019 4:56 PM
  • should i change 'SYSTEM FQDN' and put there computer name which i want delete?

    Yes, please replace the SYSTEM FQDN with the FQDN of the WSUS client.
      

    Regards,
    Yic


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

    Friday, May 31, 2019 1:28 AM
  • Hi again

    Unfortunately it doesn't solve my problem. When i use this command i get:

    Exception calling "GetComputerTargetByName" with "1" argument(s): "The specified item could not be found in the
    database."
    At line:1 char:1
    + (Get-WsusServer).GetComputerTargetByName('lappl022').Delete()
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : WsusObjectNotFoundException

    but this object 'lappl022' still is there

    Friday, May 31, 2019 10:25 AM
  • is not working... :(

    cant allocate whole memory cause i have another service on this server

    Friday, May 31, 2019 10:26 AM
  • Exception calling "GetComputerTargetByName" with "1" argument(s): "The specified item could not be found in the

    database."
    At line:1 char:1
    + (Get-WsusServer).GetComputerTargetByName('lappl022').Delete()
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : WsusObjectNotFoundException

    but this object 'lappl022' still is there

    Try changing "lappl022" to the FQDN of lappl022, or refer to the computer name shown in the console.
      


       

    Hope the above can help you.
      

    Regards,
    Yic

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

    Monday, June 3, 2019 6:03 AM
  • It doesnt help. i cannot delete this machine from wsus but i removed it from active directory group

    This group belongs to GPO wsus. I hope after 30days if i use cleanup tools from wsus console it remove and solve my case

    Thursday, June 13, 2019 12:35 PM