none
WSUS client not reporting

    Question

  • I've just installed WSUS 3.0 SP2 on a Win 2008 R2 Standard server. I used SQL Server Express 2008 SP1 as the database. I saw no errors during the installation. I believe I installed all the necessary prerequisites.

    I pointed a single client to the new WSUS server using registry settings and used wuauclt to try and get it to register with the server but I don't see the client show up in the Update Services Admin Console.

    I can access the default web site from the client and download http:// WSUSServerName /selfupdate/wuident.cab so I think the web site installed ok. But when I run cscript "c:\program files\update services\setup\installselfupdateonport80.vbs" , I get the error:

    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    SetupSelfupdateTree: Finding the index of the Web site on which WUS is installed ...
    SetupSelfupdateTree: Failed to read HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update
     Services\Server\Setup\IISTargetWebSiteIndex. Error(-2147024891) : Invalid root
    in registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Se
    tup\IISTargetWebSiteIndex".
    SetupSelfupdateTree: Error: Unable to locate the index of the WUS website.
    Error: InstallSelfupdateOnPort80 failed.

     

    I ran the WSUS Client Diagnostics Tool on the WSUS server and got an error message but I just read that this is due to it being a 32-bit app and I'm using 64-it OS. 

     

    Does anyone know where I went wrong? TIA.

    BTW, this server also has SQL Server 2008 running on it. I stuck WSUS in a SQL Server 2008 Express instance, if that matters.

     

    • Edited by jim7jim Thursday, April 29, 2010 8:50 PM new info
    Thursday, April 29, 2010 8:38 PM

Answers

  • "jim7jim" wrote in message news:cd515c10-4b3d-4140-891d-15bcfff982a8...
     
    I'm concerned with your comment #1. I'm pasting a section of the WSUS 3.0 SP2 Release Notes (on page 3) below that indicate SQL Server Express is supported:

     You must have one of the following supported databases installed: 
     Microsoft SQL Server 2008 Express, Standard, or Enterprise Edition 

    Is this something that is possible but not recommended? Do you still think I should use the Windows Internal Database? If so, is there an easy way to make this switch or do I just need to reinstall and select the internal database? 

    Yes.. it is *supported*.. but I do not recommend using it.

    SQL Server Express Edition has size limitations and resource throttling. It has a maximum database size of 4GB, which in some WSUS installations is not large enough. It has resource throttling which can only make use of 1GB RAM for buffering and a single logical CPU, which means multi-core systems are leaving idle resources on the table. The Windows Internal Database does not have any of these resource limitations, thus making it the more appropriate (free) database engine for use with WSUS.
     

    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
    • Marked as answer by jim7jim Friday, April 30, 2010 9:07 PM
    Friday, April 30, 2010 4:07 PM

All replies

  • "jim7jim" wrote in message news:3ffc0c8a-0fce-44be-8af5-32bab4875946...

    I've just installed WSUS 3.0 SP2 on a Win 2008 R2 Standard server. I used SQL Server Express 2008 SP1 as the database. I saw no errors during the installation. I believe I installed all the necessary prerequisites.

    I pointed a single client to the new WSUS server using registry settings and used wuauclt to try and get it to register with the server but I don't see the client show up in the Update Services Admin Console.

    I can access the default web site from the client and download http:// WSUSServerName /selfupdate/wuident.cab so I think the web site installed ok. But when I run cscript "c:\program files\update services\setup\installselfupdateonport80.vbs" , I get the error:

    Also, if I run the WSUS Client Diagnostics Tool on the WSUS server, I get this (had to right click and runas admin):

    WSUS Client Diagnostics Tool

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    BTW, this server also has SQL Server 2008 running on it, but I stuck WSUS in an instance using SQL Server 2008 Express, if that matters.

     

    A number of comments:
     
    1. SQL Server Express Edition is not an appropriate database engine to use for WSUS . You should use the default Windows Internal Database, or since you already have an instance of SQL Server 2008 installed, it would be appropriate to use the existing instance.
     
    2. Configuring a client via registry is not sufficient to get the client to communicate, you must also then restart the Automatic Updates service (net stop wuauserv; net start wuauserv). The registry is read by the service at service startup, or when a policy change event is identified. This is one reason why using Local Policy is a preferable solution to directly editing the registry.
     
    3. Accessing the URL on the Default Web Site is a validation that the server is functional; however, the installselfupdateonport80.vbs script is a remediation script and serves no functional purpose in a properly installed server, In addition, that script was written for use on WIn2003/IIS6, and it may not even be functional on Win2008/IIS7.
     
    4. Finally, the Client Diagnostic Tool is 32-bit only, and the error you received is a natural manifestation of running this 32-bit only tool on a 64-bit system.

     

    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
    Thursday, April 29, 2010 8:59 PM
  • Lawrence,

    Thanks for your response. The client did report after restarting the Auto updates service as you mentioned. Thanks.

    I'm concerned with your comment #1. I'm pasting a section of the WSUS 3.0 SP2 Release Notes (on page 3) below that indicate SQL Server Express is supported:

     

     You must have one of the following supported databases installed: 
     Microsoft SQL Server 2008 Express, Standard, or Enterprise Edition
     SQL Server 2005 SP2
     Windows Internal Database
    If one of the supported versions of SQL Server is not installed, the WSUS 3.0 SP2 Setup
    Wizard will install Windows Internal Database.

     

    Is this something that is possible but not recommended? Do you still think I should use the Windows Internal Database? If so, is there an easy way to make this switch or do I just need to reinstall and select the internal database?

    Thanks in advance for your help.

     

    Friday, April 30, 2010 1:01 PM
  • "jim7jim" wrote in message news:cd515c10-4b3d-4140-891d-15bcfff982a8...
     
    I'm concerned with your comment #1. I'm pasting a section of the WSUS 3.0 SP2 Release Notes (on page 3) below that indicate SQL Server Express is supported:

     You must have one of the following supported databases installed: 
     Microsoft SQL Server 2008 Express, Standard, or Enterprise Edition 

    Is this something that is possible but not recommended? Do you still think I should use the Windows Internal Database? If so, is there an easy way to make this switch or do I just need to reinstall and select the internal database? 

    Yes.. it is *supported*.. but I do not recommend using it.

    SQL Server Express Edition has size limitations and resource throttling. It has a maximum database size of 4GB, which in some WSUS installations is not large enough. It has resource throttling which can only make use of 1GB RAM for buffering and a single logical CPU, which means multi-core systems are leaving idle resources on the table. The Windows Internal Database does not have any of these resource limitations, thus making it the more appropriate (free) database engine for use with WSUS.
     

    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
    • Marked as answer by jim7jim Friday, April 30, 2010 9:07 PM
    Friday, April 30, 2010 4:07 PM
  • Thanks again for the help. I can't believe I spent hours reading the WSUS deployment manual and it never mentions any of those limitations. Unless I just missed it.

    I've managed to mess up my SQL installation now by trying to uninstall the SQL Express. I think I'll try and get that sorted out before reinstalling WSUS with the Windows internal db.

    Cheers!

    Friday, April 30, 2010 9:10 PM
  • "jim7jim" wrote in message news:ab7f4a84-045e-4b7b-acd7-456cff023bb5...

    Thanks again for the help. I can't believe I spent hours reading the WSUS deployment manual and it never mentions any of those limitations. Unless I just missed it.


    The Deployment Guide does not mention those limitations.   Unfortunately. :-/

    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
    Saturday, May 01, 2010 3:18 PM
  • I am having the same issue where clients are not receiving updates from Wsus 2008 R2

    Sunday, June 16, 2013 8:36 AM
  • I am having the same issue where clients are not receiving updates from Wsus 2008 R2

    Please post to a *NEW* thread with your specific symptoms and exact details.

    Aside from posting to a three-year old resolved thread, your information provides nothing that can contribute to helping you.

    You might start by reviewing How to ask a question efficiently in a TechNet forum, posted at the top of this message list.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sunday, June 16, 2013 9:13 PM