Question : WSUS clients not reporting

I recently deployed new Windows 7 machines and configured them to report to a new WSUS server.  Shortly after deployment, for some reason, WSUS was not showing as installed on the server - maybe another admin here removed it.  In order to remedy the situation short term, I thought I should put the clients back on the original server, a Windows 2003 R2 Service pack 2 box.  It has WSUS 3.0 SP1 (I think SP2 requires a 2008 server).

All I have done so far is modify the clients' reg key  HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WuServer and HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WuStatusServer values to reflect the IP address of the Windows update server (they now just say http://10.1.1.28).  
My clients now show up in the server, but show as not yet reported, as well as showing the OS as Windows 0.0.  

The client utility output looks ok - and a reg query returns the following output:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    ElevateNonAdmins    REG_DWORD    0x1
    AcceptTrustedPublisherCerts    REG_DWORD    0x1
    WUServer    REG_SZ    http://10.1.1.28
    WUStatusServer    REG_SZ    http://10.1.1.28

If I bring up 10.1.1.28 in a browser, I get an Under Construction page (which is correct, I believe) and if I do a http://10.1.1.28/selfupdate/wuident.cab it asks me to save the file so that's working correctly.

Will Windows 7 work with anything less than SP2 on WSUS?

Output of the client diagnostic tool is:
WSUS Client Diagnostics Tool

Checking Machine State
        Checking for admin rights to run tool . . . . . . . . . PASS
        Automatic Updates Service is running. . . . . . . . . . PASS
        Background Intelligent Transfer Service is running. . . PASS
        Wuaueng.dll version 7.4.7600.226. . . . . . . . . . . . PASS
                This version is WSUS 2.0

Checking AU Settings
        AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
                Option is from Policy settings

Checking Proxy Configuration
        Checking for winhttp local machine Proxy settings . . . PASS
                Winhttp local machine access type
                        <Direct Connection>
                Winhttp local machine Proxy. . . . . . . . . .  NONE
                Winhttp local machine ProxyBypass. . . . . . .  NONE
        Checking User IE Proxy settings . . . . . . . . . . . . PASS
                User IE Proxy. . . . . . . . . . . . . . . . .  NONE
                User IE ProxyByPass. . . . . . . . . . . . . .  NONE
                User IE AutoConfig URL Proxy . . . . . . . . .  NONE
                User IE AutoDetect
                AutoDetect not in use

Checking Connection to WSUS/SUS Server
                WUServer = http://10.1.1.28
                WUStatusServer = http://10.1.1.28
        UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
                Client is pointed to SUS 1.0 Server
        Connection to server. . . . . . . . . . . . . . . . . . PASS
        SelfUpdate folder is present. . . . . . . . . . . . . . PASS

Answer : WSUS clients not reporting

If you're server is 64bit get the 64bit, if it's 32bit get the 32bit.


As well as other stuff the following that you mention should be installed for WSUS to work.
ASP.net
.net extensibility
isapi filters
windows authentication
Request Filtering

Here's a great walk through to get it up and running.  Print it off and read it over.
http://www.microsoft.com/downloads/details.aspx?FamilyID=df628245-8449-4b93-948c-0926deb1197a&displaylang=en

If you have more questions/issues feel free to ask, no problem.

-Jeff