locked
No clients connected to WSUS Server RRS feed

  • Question

  • I have just installed a WSUS onto my Microsoft Server 2008 R2 Enterprise, but no clients seems detecting. I installed WSUS using the add role feature under Server Manager.

    Previously, i installed WSUS 3.0 onto MS Server 2003 Std & it worked just fine.

    Is there any firewall settings that i need to do in my Windows 2008 R2? My clients are all at the same LAN, same IP Segment, same domain as the WSUS Server. Even new clients couldn't be detected.

    Thanks.

    Tuesday, September 14, 2010 9:51 AM

Answers

  • Please can anyone help. Approval Status - Install (1/20) what does this mean
    This means that the update is approved for ONE of your TWENTY Target Groups.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Proposed as answer by Olufis Thursday, September 23, 2010 8:08 AM
    • Marked as answer by Lawrence Garvin Thursday, September 23, 2010 3:55 PM
    Monday, September 20, 2010 3:43 PM
  • Thanks, I got it fixed already.

    I modified Domain & Local GPO and all clients were detected/got an updates

     

    Thanks


    Fiss
    • Marked as answer by Eric Zhang CHN Thursday, September 23, 2010 7:09 AM
    Monday, September 20, 2010 9:02 PM

All replies

  • Have you configured the clients to use the WSUS server? take a look at this article: http://technet.microsoft.com/en-us/library/cc720539(WS.10).aspx
    Tuesday, September 14, 2010 1:31 PM
  • Dear Jeff,

    I noticed only Clients with Windows Vista & Above & Server 2008 are joining to my WSUS 3.0. However, none of my Windows XP Clients are joining. My active directory was installed on a Windows Server 2008 Enterprise R2. I have add the wuau.adm at the group policy template, but still doesn't work.

     

    Wednesday, September 15, 2010 2:24 AM
  • Now this is getting interresting...
    Can you logon to such a workstation and try to ping (and connect) to the WSUS server manually?
    What is your domain/forest functional level?
    Wednesday, September 15, 2010 5:10 AM
  • I can logon to the workstation & successfully ping to the WSUS server. Both workstation & WSUS Server are connected to the same switch, & they share the same IP Segment 199.2.1.x. They are connected to the same level of the domain, e.g. xxxx.domain.com.

    Could it be wuau.adm is used in Windows XP while wuau.admx is used in Windows Server 2008 R2, thats why there is incompatability?

    Any software to check whether my workstation's policy for Windows Update is correct?

     

    Wednesday, September 15, 2010 7:55 AM
  • You can check the following registry keys on the XP machine to check wether the policy is set: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

    Connecting to the WSUS server manually.. what I mean is to connect to the website of WSUS from the XP workstation...
    Wednesday, September 15, 2010 8:02 AM
  • I have changed the user account for this machine to domain_admins.

    When i run regedit, surprisingly, i could only see HKLM\SOFTWARE\POLICIES\MICROSOFT\WINDOWS\ . There is no WindowsUpdate folder.

    But when i log into local instead of domain, i could see WindowsUpdate folder when i run regedit.

    Wednesday, September 15, 2010 8:23 AM
  • I should say both local machine & domain account also does not have HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

    Could it be group policy could not apply settings to my XP Clients? But other settings like Control Panel & Lock Taskbars has already been applied succesfully using Group Policy. It's getting a bit weird.

    Wednesday, September 15, 2010 9:34 AM
  • ...only Clients with Windows Vista & Above & Server 2008 are joining to my WSUS 3.0. However, none of my Windows XP Clients are joining.

    What version of Windows XP are you using?

    The client requirements listed on page 63 of the Deployment Guide specify XP Pro SP2 or later. 

    Deployment Guide can be found here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=113d4d0c-5649-4343-8244-e09e102f9706&displaylang=en

    Also, if those clients were set up by using an image, you may need to clear the SUSClientID.  Instructions for clearing the SUSClientID can also be found in that Deployment Guide, you can refer to KB903262 for step-by-step instructions.

    KB article 903262 can be found here: http://support.microsoft.com/kb/903262/en-us

    Wednesday, September 15, 2010 2:25 PM
  • How you would like to deploy WSUS on to the clients, thru GPO or manually adding thru registry, if thru GPO, can you make please check that particular GPO is applied to the clients are not.
    Thursday, September 16, 2010 6:56 AM
  • All my clients are minimum XP Pro SP2. My clients are all installed using the original disc from the manufacturer. I didn't use any image or Norton Ghost to install them.
    Friday, September 17, 2010 12:56 AM
  • I need to deploy WSUS through GPO. The GPO has other items, e.g. Controlling of taskbars & control panel items. All restrictions i put into the GPO works, except for WSUS. However, this WSUS gpo works on my Windows Server 2008 R2 Ent clients. It doesn't apply on XP Pro SP2 machines.
    Friday, September 17, 2010 12:58 AM
  • All my clients are minimum XP Pro SP2.

    The documentation was written in 2007 and minor updates were made last year to account for the release of WSUS v3 SP2.

    However, a significant point to be noted here is that Microsoft quit issuing updates for XP SP2 systems in July, 2010, and this was widely publicized and discussed. If you are trying to detect *new* updates with Windows XP Service Pack 2 systems, the detections will not occur. At a minimum you will need to have Windows XP Service Pack 3 installed in order to detect any update released after July 13, 2010.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, September 17, 2010 7:13 PM
  • Hello

    I'm having similar problem with my client detection, this time I'm deploying via SCCM. Created an update list, start new deploy software update from this list, selected the newly created templates and test collection (with only 5 different clients - XP/Vista/Win7). I use GPO to deploy wsus, wsus is installed on same server as sccm, after pushing the updates, the update not installed.

    1. One laptop with XP Sp3 not coming up at all on WSUS All computers list. Did rsop and only servername was showing in specified server name as to full fqdn specified in the gpo

    2. The one coming up says, This computer has not reported staus for 55 days or more

    3. I checked the registry and under windowsupdate WUServer and WUStatusServe were both pointing to a server name which is my wsus/sccm server but as specified in GPO. Full FQDN was specified in GPO but netbios name only showing

     

    Any advise please on how to correct this

     

    Thanks


    Fiss
    Monday, September 20, 2010 11:12 AM
  • Please can anyone help. Approval Status - Install (1/20) what does this mean

     

    Thanks


    Fiss
    Monday, September 20, 2010 1:49 PM
  • I'm having similar problem with my client detection, this time I'm deploying via SCCM.
    Please seek assistance in the SCCM Software Updates Forum for this question.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Proposed as answer by Olufis Thursday, September 23, 2010 8:08 AM
    • Unproposed as answer by Lawrence Garvin Thursday, September 23, 2010 3:55 PM
    Monday, September 20, 2010 3:42 PM
  • Please can anyone help. Approval Status - Install (1/20) what does this mean
    This means that the update is approved for ONE of your TWENTY Target Groups.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Proposed as answer by Olufis Thursday, September 23, 2010 8:08 AM
    • Marked as answer by Lawrence Garvin Thursday, September 23, 2010 3:55 PM
    Monday, September 20, 2010 3:43 PM
  • Thanks, I got it fixed already.

    I modified Domain & Local GPO and all clients were detected/got an updates

     

    Thanks


    Fiss
    • Marked as answer by Eric Zhang CHN Thursday, September 23, 2010 7:09 AM
    Monday, September 20, 2010 9:02 PM
  • Many thanks

    Fiss
    Thursday, September 23, 2010 8:09 AM