+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 21 of 21
Windows Server 2000/2003 Thread, WSUS 3.1 - Computers not reporting in Technical; Originally Posted by CHR1S Great minds think alike, I just tried that - the PC is now picking up updates ...
  1. #16
    ajs
    ajs is offline

    Join Date
    Jun 2008
    Location
    Wigton, Cumbria
    Posts
    226
    Thank Post
    2
    Thanked 35 Times in 35 Posts
    Rep Power
    23
    Quote Originally Posted by CHR1S View Post
    Great minds think alike, I just tried that - the PC is now picking up updates and prompting me to install, but still showing as not reporting back... were close now
    Twice in one week that someone thinks I have a great mind. Something weird must be happening in the world.

    Anyway, in situations where PCs don't report back I've often taken a slightly brutal approach and deleted the PC from WSUS, renamed its C:\Windows\Softwaredistribution folder and then forced an update to get it to reregister with WSUS. More often that not it's shown up in the console pretty quickly and after a few reboot cycles as it does its updates, it reports back that all is well.

    Of course, as long as it's picking up updates then the reporting issue can just be added to the infamous TODO list I guess :-)

  2. Thanks to ajs from:

    CHR1S (10th June 2010)

  3. #17

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,486
    Thank Post
    1,570
    Thanked 459 Times in 300 Posts
    Rep Power
    212
    And its now reported back!! Woooo!

    Last question, will the clients all automatically update on its next scheduled cycle or will they all have to be forced?

  4. #18
    ajs
    ajs is offline

    Join Date
    Jun 2008
    Location
    Wigton, Cumbria
    Posts
    226
    Thank Post
    2
    Thanked 35 Times in 35 Posts
    Rep Power
    23
    I would suspect that if they have the same problem as the PC that's now working, things will just fall into place as they can now access the files they need :-)

    Possibly wouldn't hurt to add "wuauclt /detectnow" to a startup script to try and coax them along but I don't think it's necessary.

  5. Thanks to ajs from:

    CHR1S (10th June 2010)

  6. #19
    danrhodes's Avatar
    Join Date
    Sep 2008
    Location
    Wath Upon Dearne
    Posts
    1,513
    Thank Post
    157
    Thanked 181 Times in 150 Posts
    Rep Power
    67
    I knew this would be IIS it just sounded right! The machines should report back on their next schedule I don't think a force will be needed.

    Glad the issue is sorted Chris!

    D

  7. Thanks to danrhodes from:

    CHR1S (10th June 2010)

  8. #20

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,486
    Thank Post
    1,570
    Thanked 459 Times in 300 Posts
    Rep Power
    212
    Big Thanks to you all for your help, its most appreciated

  9. #21
    danrhodes's Avatar
    Join Date
    Sep 2008
    Location
    Wath Upon Dearne
    Posts
    1,513
    Thank Post
    157
    Thanked 181 Times in 150 Posts
    Rep Power
    67
    No problem mate thats what were here for :-)

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. WSUS - Computers
    By BatchFile in forum Windows Server 2000/2003
    Replies: 12
    Last Post: 26th January 2010, 02:41 PM
  2. Replies: 7
    Last Post: 9th June 2008, 03:55 PM
  3. Replies: 3
    Last Post: 21st February 2008, 08:50 AM
  4. Replies: 1
    Last Post: 8th November 2006, 09:57 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •