Clients not reporting status after upgrading from 2.0 to 3.0

Discussion in 'Update Services' started by kcramman, Jul 5, 2007.

  1. kcramman

    kcramman Guest

    My server clients and XP clients are not reporting in after upgrade. Should
    the SUS web site be stopped after the upgrade? Is it needed anymore? It runs
    on port 80 and the WSUS administration is running on 8530. Do you need any
    logs to look at?
    kcramman, Jul 5, 2007
    1. Advertisements

  2. Winfried Sonntag [MVP], Jul 5, 2007
    1. Advertisements

  3. kcramman

    kcramman Guest

    If I run both links they both go to a download page.
    kcramman, Jul 5, 2007
  4. kcramman

    kcramman Guest

    Here is the log file from the client tool run
    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 not running. PASS
    Wuaueng.dll version 7.0.6000.374. . . . . . . . . . . . PASS
    This version is WSUS 2.0

    Checking AU Settings
    AU Option is 3 : Notify Prior to 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://xxxxx:8530
    WUStatusServer = http://xxxxxxx:8530
    UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS

    VerifyWUServerURL() failed with hr=0x800710dd

    The operation identifier is not valid.

    Press Enter to Complete
    kcramman, Jul 5, 2007
  5. kcramman

    John Guest


    After my upgrade I had a similar or same issue. I discovered the upgrade
    created a new WsusContent share under the install directory. We have ours
    under Data E. I had to recreate the share under E and then point the Content
    Virtual Directory back to E. Until I did this, the clients were checking in,
    but not downloading because they could find the Content. After I did this,
    the clients obtained the download successfully.

    This was the only thing in our upgrade that did not hold original settings.

    Hope this helps,
    John, Jul 5, 2007
  6. [a] WSUS 3 cannot be installed on a machine with SUS 1.0 still installed, so
    probably we should first confirm that SUS is, or is not, still installed.

    If SUS is still installed, and the Default Web Site is *stopped*, and
    you were running WSUS 2.0 on port 80, and the upgrade forced WSUS 3.0 back
    to port 8530 -- and the DWS is still *stopped* -- this will be problematic
    for downlevel machines that have never used WSUS 2.0. It will be irrelevant
    for active WSUS 2.0 clients.
    It's still "needed" in the sense that the WSUS 3.0 Health Monitoring
    software expects to see a functional selfupdate site on port 80. If it's not
    there the server complains.
    Lawrence Garvin \(MVP\), Jul 6, 2007
  7. kcramman

    kcramman Guest

    Looks like most of my problems are due to the anonymous access issue on the
    virtual directories. Most clients are now reporting connections to the wsus
    server and I have turned the SUS site back on. I still have a few
    workstations and one server that is stating it has not communicated yet, not
    sure why but will try to figure it out.
    Have you guys ever ran the WSUS server cleanup wizard before to remove old
    updates and such, does it work?

    Thanks for the respones

    kcramman, Jul 6, 2007
  8. kcramman

    John Guest


    I ran the cleanup wizard after my upgrade. I had approx 1100 something
    updates, selected all cleanup options, and it cleaned 106. Took about 45
    minutes. I plan to do it each month. I didn't see the size of the SUSDB
    decrease, so I'd assume it only cleans Content. If there is a way to size
    down the SUSDB, I'd certainly like to know.


    John, Jul 6, 2007
  9. I would *strongly* encourage the use of the Server Cleanup Wizard as part of
    the upgrade process, especially if you've never performed any file
    maintenance previously on your WSUS2 server.
    Actually, one of the enhancements of the SCW in WSUS3, over the utilities
    provided in WSUS2, is that it does clean up the database; however, deleting
    records from the database won't affect the filesize of the MDF file. That
    requires that you execute a database shrink command via SQL Server. The
    percentage of space reclaimed by the deleted content will be almost
    immediately reused by new metadata and/or new client reporting data, so
    there's really no point in trying to physically shrink the filesize -- but
    it will delay an autogrow event on the database file.

    Lawrence Garvin, M.S., MCTS, MCP
    Independent WSUS Evangelist
    MVP-Software Distribution (2005-2007)

    Everything you need for WSUS is at

    And, almost everything else is at
    Lawrence Garvin \(MVP\), Jul 7, 2007
  10. kcramman

    John Guest


    Thank you for the reply. Very helpful again.

    Hope this helps you too kcramman.

    John, Jul 7, 2007
  11. Would you recommend cleanup before or after the upgrade? Or both? (We're
    looking at upgrading in the near to middle future.)

    Harry Johnston, Jul 8, 2007
  12. Only after the upgrade. Everything you might do manually in WSUS 2.0 using
    the "Mowing The Grass" procedures, will be done automatically for you with
    the Server Cleanup Wizard, plus additional options never before available.

    There's no real impact on the upgrade process by having the 'junk' laying
    around during the upgrade.

    Plus, using the SCW as an automated tool ensures that you'll get everything.

    For example, the SCW allows you to clean each, any, or all of these type of
    * Unused updates and update revisions - DELETE updates that are
    expired and haven't been approved ... and DELETE old revisions of updates
    that haven't been approved for 30 days.

    In WSUS2, you needed to run the WSUSDebugTool with the
    "DeleteUnneededRevisions" option to accomplish this; in addition, in WSUS2
    the purge applied to *all* updates in this status, whereas WSUS3 excludes
    those updates that are still less than 30 days old.

    * Computers not contacting the server - DELETE computers that have
    not contacted the server in 30 days or more.

    In WSUS2, you had to use the unsupported CleanStaleComputers tool from the
    API Samples and Tools Kit.

    * Superseded updates - DECLINE updates that are superceded by an
    approved update, are not approved, and haven't been needed by computers for
    [30 days] or more.

    In WSUS2, you had to manually identify these "unneeded" updates and
    individually mark them as declined, Hopefully you got all of them. Note that
    in WSUS3, an *approved* superceded update will not be affected by this
    cleanup task. Also, if any computer has reported one of these superceded
    updates as "Needed" in the past 30 days, it will not be cleaned out. This is
    a very important consideration -- because if you've not declined known
    superceded/unneeded updates at the time you approved the latest update, an
    unpatched system will still report the superceded update as "Needed", thus
    resetting this 30 day clock.

    * Unneeded update files - DELETE update files that aren't needed by
    updates or downstream servers.

    This is an expansion of the features available in WSUS2. In WSUS2, you had
    to find and mark these updates as "Declined", in order to purge the file
    content using the WSUSDebugTool with the "PurgeUnneededFiles" option. Now,
    the only requirement is that there are no resources reporting the content as
    "Needed". The documentation does not specify what happens to an "Approved"
    update that has the content yanked out from under it. It could also be that
    the interpretation of "needed" is different for this functionality. I'll see
    if I can get some clarification on how exactly this particular feature

    * Expired updates - DECLINE updates that aren't approved and have
    been expired by Microsoft.

    I don't really know of any updates that fit into this classification --
    usually content expired are revisions in the same update. The one example I
    do know of is when the WUA svchost.exe patch was renumbered under a new KB.
    The original update was then 'expired', but many systems still had the
    update in the "Approved" list. This feature would automatically move such
    updates to "Declined" status, which would then

    Lawrence Garvin, M.S., MCTS, MCP
    Independent WSUS Evangelist
    MVP-Software Distribution (2005-2007)

    Everything you need for WSUS is at

    And, almost everything else is at
    Lawrence Garvin \(MVP\), Jul 8, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.