locked
Client Computers not showing up RRS feed

  • Question

  • Hey All,

    I have gone through the process of configuring WSUS but I am unable to see any computers. I have tried getting one up and running as a test buy running these commands on it...

    ::gpresult /r
    ::Wuauclt.exe /reportnow /detectnow
    ::Wuauclt.exe /detectnow

    but It doesn't show up. 

    GPO is compete with;

    Configure auto updates, Specify Intranet, and Enable Client-side targeting all enabled.

    Any thoughts on where I should start with this?

    Thanks

    Wednesday, May 24, 2017 7:17 PM

Answers

  • WSUS is not instant, it's not abnormal for 48+ hour wait times on clients as WSUS is just a repository. It's up to the client to check in. GPOs have the ability to change the timing, but the default is every 22 hours give or take 20% for randomization so that bandwidth is not saturated.

    Think of WSUS as a POP3 server. It's up to the client to ask for email - same with WSUS and Windows Update Clients.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    • Marked as answer by TimHirt_1 Thursday, May 25, 2017 1:55 PM
    Thursday, May 25, 2017 12:10 PM

All replies

  • Are the groups in WSUS Console actually created? They must be created before targeting will work.

    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Thursday, May 25, 2017 3:48 AM
  • ya I made a group in the console... I just came in this morning and it is showing up... Is their a reason it would wait for something before showing up? none the less it seems to be working now, I will add more computers and see if they all work.
    Thursday, May 25, 2017 11:02 AM
  • WSUS is not instant, it's not abnormal for 48+ hour wait times on clients as WSUS is just a repository. It's up to the client to check in. GPOs have the ability to change the timing, but the default is every 22 hours give or take 20% for randomization so that bandwidth is not saturated.

    Think of WSUS as a POP3 server. It's up to the client to ask for email - same with WSUS and Windows Update Clients.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    • Marked as answer by TimHirt_1 Thursday, May 25, 2017 1:55 PM
    Thursday, May 25, 2017 12:10 PM
  • Also, for WSUS Maintenance, have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Thursday, May 25, 2017 12:11 PM