+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 16
Windows Thread, Stations Not Showing In Update Services [WSUS] in Technical; We have recently enabled and started using WSUS [updating station-by-station or at imaging time historically] It all looks very promising ...
  1. #1

    DaveP's Avatar
    Join Date
    Oct 2006
    Location
    Can't talk now: The mother-ship is calling!
    Posts
    8,994
    Thank Post
    352
    Thanked 1,301 Times in 891 Posts
    Blog Entries
    4
    Rep Power
    1131

    Stations Not Showing In Update Services [WSUS]

    We have recently enabled and started using WSUS [updating station-by-station or at imaging time historically]

    It all looks very promising except for the fact that so few of my stations/laptops are showing up in Computers/All Computers [nearly half my computers are not shown!]

    I can't find any way to force a 'missing' station to appear in WSUS. Can anyone help?

    Server O/S: Windows 2003 Standard: SP2.

    Workstion/Laptop O/S: Windows XP Pro: SP 2 or SP3.

    XP Firewall is turned off by Group Policy.

    Thanks.

  2. #2
    jmcdermott's Avatar
    Join Date
    Feb 2008
    Location
    Cornwall
    Posts
    173
    Thank Post
    16
    Thanked 43 Times in 35 Posts
    Rep Power
    21
    we had the same issue, thinking back i think it was due to the workstations needing windows update software installed on them, this software is installed first time you try to upgrade using the web.

    On a machine that is not being seen, run windows update, allow it to update the update software (Windows installer 3.1 or something like that.) no need to install any other updates then restart the workstation.

    Hope this helps.

  3. #3

    Join Date
    Apr 2008
    Location
    Bournemouth
    Posts
    472
    Thank Post
    34
    Thanked 28 Times in 26 Posts
    Rep Power
    27
    Try this? Works for us.

    REGEDIT /s wsus.reg

    c:\windows\system32\wuauclt.exe /detectnow

    gpupdate /force /boot

    Plus download the latest WSUS client version - 3.0 I think?

    Had to delete/re register the susclientI.D. in registry and also that helped as well.
    Last edited by Jiser; 18th May 2009 at 01:39 PM.

  4. #4

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,803
    Thank Post
    110
    Thanked 583 Times in 504 Posts
    Blog Entries
    1
    Rep Power
    224
    Also the log file, C:\Windows\Windows Update.log might tell you why it's not working.

  5. #5
    Crispin's Avatar
    Join Date
    Dec 2008
    Location
    Essex
    Posts
    361
    Thank Post
    76
    Thanked 28 Times in 25 Posts
    Rep Power
    20
    Also, you can run the WSUS client diagnostic tool found here:

    Microsoft Windows Server Update Services Tools and Utilities

  6. #6
    mrforgetful's Avatar
    Join Date
    May 2006
    Posts
    1,639
    Thank Post
    7
    Thanked 15 Times in 15 Posts
    Rep Power
    22
    I used WSUS for a week.

    It applied an update to all 600 machines one weekend, an update which stopped them logging into the network. I had to go around and uninstall it from all 600.

    I'm just glad it let me, if I remember correctly some updates aren't removeable at all.

    Now I don't bother, would rather image them with all updates checked.

  7. #7

    Join Date
    Apr 2008
    Location
    Bloomsburg
    Posts
    51
    Thank Post
    14
    Thanked 14 Times in 9 Posts
    Rep Power
    15
    I had an issue with WSUS where all my SID's were the same from imaging machines, and looked like most of my machines weren't showing up on the server, but were still locked down by GP and getting updates. I used this in a batch file, and set it to run on logon, and most of my machines came back...

    Code:
    @echo on
    net stop wuauserv
    REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    net start wuauserv
    wuauclt /resetauthorization /detectnow
    The latest version is 3.0SP1. There is SP2 out, but I think it's still in the beta/RC stage.

  8. #8

    DaveP's Avatar
    Join Date
    Oct 2006
    Location
    Can't talk now: The mother-ship is calling!
    Posts
    8,994
    Thank Post
    352
    Thanked 1,301 Times in 891 Posts
    Blog Entries
    4
    Rep Power
    1131
    Hi,

    None of the suggestions above worked for me. However I have found a solution that seems to do the job [We are using Server 2008]

    1. Goto Group Policy and create a new policy or edit existing [depedning on your preference] Goto Computer Configuration/Policies/Admin Templates and right click. Here select Add/Remove Templates and locate wuau.adm [I downloaded this template a little while ago: Can't remember where from but I will attach a copy of it to this post: Extension changed from .ADM to .TXT to allow for attaching] Click OK to accept the import.

    2. Goto Computer Configuration/Policies/Admin Templates/Windows Components/Windows Update and set your Windows Update Policy as needed/desired.

    3. Again in Group Policy go to the OU/OUs you want to enforce the WSUS find for [I did this right at the top of my domain because there were so many stations missing from WSUS] Goto Computer Configuration/Policies/Windows Settings/Startup. Create a batch file which will run when the station logs on.

    Contents of the batch file:

    @echo on
    net stop wuauserv
    REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\Wi ndowsUpdate" /v PingID /f
    REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\Wi ndowsUpdate" /v AccountDomainSid /f
    REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\Wi ndowsUpdate" /v SusClientId /f
    net start wuauserv
    wuauclt /resetauthorization /detectnow


    4. To hurry things along you might want to 'gpupdate /force'

    Just be aware that my stations seemed to take forever after restarting with this new policy in place so you might want to experiment before rolling this out acroos the network. Once all of the stations are in WSUS I will stop enforcing the policy and I will have my WSUS deploying all of the critical updates to all my stations [hopefully]

    Contents of wuau.adm [Attached]

    Hope this helps [sure solved the issue for me ]
    Attached Files Attached Files

  9. #9
    OverWorked's Avatar
    Join Date
    Jul 2005
    Location
    N. Yorks
    Posts
    1,014
    Thank Post
    198
    Thanked 42 Times in 34 Posts
    Rep Power
    30
    I've just come across the same problem with one machine here.

    I deleted the reg keys (ces973's post above) and ran
    Code:
    wuauclt /resetauthorization /detectnow
    but just got DCOM 10005 errors in the system log.

    Then I found this.

    I ran the script below to stop the service (it wasn't running anyway) and re-register all the dll's.

    Code:
    net stop wuauserv
    regsvr32 /s wuapi.dll
    regsvr32 /s wups.dll
    regsvr32 /s wuaueng.dll
    regsvr32 /s wuaueng1.dll
    regsvr32 /s wucltui.dll
    regsvr32 /s wuweb.dll
    regsvr32 /s jscript.dll
    regsvr32 /s atl.dll
    regsvr32 /s softpub.dll
    regsvr32 /s msxml3.dll
    net start wuauserv
    Then I ran
    Code:
    wuauclt /resetauthorization /detectnow
    and it's all working! Two weeks of hair ripping over!

    I don't know if this'll help you, but I hope it does. I'm posting it here for reference anyway.

  10. #10
    OverWorked's Avatar
    Join Date
    Jul 2005
    Location
    N. Yorks
    Posts
    1,014
    Thank Post
    198
    Thanked 42 Times in 34 Posts
    Rep Power
    30
    I've just found another neat trick when all the above failed.

    Open IE and go to update.microsoft.com on each affected client and let it install the latest Windows Update client. You don't need to actually install any other updates.

    Run wuaulclt /detectnow (or leave it to do it itself) and the machine will register with the WSUS server and download and install updates like it should.

    I found this this week with a room full of newly ghosted machines (all XP SP3) in one of the schools I look after. None of them were registering with WSUS or downloading updates. The WSUS client diagnostic tool showed no problems on the clients, though.

    This probably won't work in every case; but it worked here, and is worth a try.

  11. #11
    p858snake's Avatar
    Join Date
    Dec 2008
    Location
    Queensland
    Posts
    1,490
    Thank Post
    37
    Thanked 175 Times in 151 Posts
    Blog Entries
    2
    Rep Power
    51
    Quote Originally Posted by OverWorked View Post
    I've just found another neat trick when all the above failed.

    Open IE and go to update.microsoft.com on each affected client and let it install the latest Windows Update client. You don't need to actually install any other updates.

    Run wuaulclt /detectnow (or leave it to do it itself) and the machine will register with the WSUS server and download and install updates like it should.

    I found this this week with a room full of newly ghosted machines (all XP SP3) in one of the schools I look after. None of them were registering with WSUS or downloading updates. The WSUS client diagnostic tool showed no problems on the clients, though.

    This probably won't work in every case; but it worked here, and is worth a try.
    Where the images sysprep'ed before deployment or newsid'ed after deployment?

  12. #12
    OverWorked's Avatar
    Join Date
    Jul 2005
    Location
    N. Yorks
    Posts
    1,014
    Thank Post
    198
    Thanked 42 Times in 34 Posts
    Rep Power
    30
    Quote Originally Posted by p858snake View Post
    Where the images sysprep'ed before deployment or newsid'ed after deployment?
    I don't know. The supplier did them before I worked there. I think they were syspreped before deployment.

    I tried newsid on a few (and all of the above suggestions) but it wouldn't get them going.

    I'd given up on WSUS for these machines and I just decided to manually update them from the MS update site as a last resort. I was surprised when they immediately registered themselves with the WSUS server and began downloading.

  13. #13
    p858snake's Avatar
    Join Date
    Dec 2008
    Location
    Queensland
    Posts
    1,490
    Thank Post
    37
    Thanked 175 Times in 151 Posts
    Blog Entries
    2
    Rep Power
    51
    Quote Originally Posted by OverWorked View Post
    I don't know. The supplier did them before I worked there. I think they were syspreped before deployment.

    I tried newsid on a few (and all of the above suggestions) but it wouldn't get them going.

    I'd given up on WSUS for these machines and I just decided to manually update them from the MS update site as a last resort. I was surprised when they immediately registered themselves with the WSUS server and began downloading.
    NewSID won't do it because it only does certain infromation, where as sysprep does everything to make it's think it's a new install (You can tell if its sysprep because on the first boot of the image it should come up with a "mini" setup that may not have any options depending on the answer file).

  14. #14

    Dos_Box's Avatar
    Join Date
    Jun 2005
    Location
    Preston, Lancashire
    Posts
    9,014
    Thank Post
    614
    Thanked 2,194 Times in 1,006 Posts
    Blog Entries
    23
    Rep Power
    632
    WSUS Is one of those wonderful services that either has you tearing your hair out or singing its praises from the rooftops!
    I have always found it to be a wonderful time saving tool when working, but by God when it goes belly up it's always a day job to set right again!

  15. #15

    john's Avatar
    Join Date
    Sep 2005
    Location
    London
    Posts
    10,362
    Thank Post
    1,499
    Thanked 1,053 Times in 922 Posts
    Rep Power
    303
    Must admit I agree with DB, before the summer our WSUS setup was not that good, it showed some machines but around 80% of them never were up to date, major fails on updates, dropping in and out but now we have reinstalled near enough everything, its really much improved.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Server 2008 box not showing in WSUS
    By FN-GM in forum Windows Server 2008
    Replies: 10
    Last Post: 23rd May 2009, 08:19 PM
  2. recent MS update knackered WSUS?
    By Oops_my_bad in forum Windows
    Replies: 6
    Last Post: 16th October 2007, 10:08 PM
  3. Server 2003 stalls after wsus update
    By pooley in forum Windows
    Replies: 2
    Last Post: 13th July 2007, 01:56 PM
  4. Replies: 5
    Last Post: 10th November 2006, 08:46 AM
  5. Replies: 5
    Last Post: 16th October 2006, 10:02 PM

Thread Information

Users Browsing this Thread

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

Tags for this Thread

Posting Permissions

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