Results 1 to 9 of 9

Thread: Computers not reporting to the server

  1. #1
    Join Date
    Jun 2009
    Posts
    4

    Computers not reporting to the server

    I have a problem with WSUS.

    Some computers are not reporting to the server.

    3 Windows Server 2003 sp2 are not reporting, it has a status of "this computer has not reported yet", and the computer details specified is windows 0.0

    On those 3 computers, the WSUS server itself is unable to report to the WSUS.

    I've verified that I can access the ff:
    http://<servername>/iuident.cab
    http://<servername>/selfupdate/iuident.cab
    http://<servername>/clientwebservice/wusserverversion.xml

    I've verified that selfupdate is accessible (all other computers are getting updates and reporting to the server)

    I've applied KB's from MS regarding WSUS (sorry i can't remember the exact
    update)
    -one has something to do with IIS compression
    -one has something to do with Office 2003 sp1

    I've reinstalled Automatic updates (regsvr2 wuaueng.dll)
    and deleted softwaredistribution folder

    I've reinstalled WSUS and IIS

    No proxy is in place

    Tried the steps in deleting the WBEM folder

    My problem is close to the one mentioned here:
    http://www.wsuswiki.com/AgentFailedDetecting0x8024400d

    I've verified that all passed in the clientdiag tool

    I've ran wuauclt.exe /resetauthorization /detectnow numerous times

    Please, can someone take a look in the logs below to see what seems to be the problem

    Appreciate you guys for taking a look on my post...

    2009-06-26 13:02:04:628 940 10c4 PT +++++++++++ PT: Synchronizing server updates +++++++++++
    2009-06-26 13:02:04:628 940 10c4 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://phkgensrv700:8530/ClientWebService/client.asmx
    2009-06-26 13:02:04:706 940 10c4 PT Initializing simple targeting cookie, clientId = 89fc56e8-39a4-413f-8de9-4db9432817c2, target group = Windows 2003 Server Computers, DNS name = phkgensrv700.smi.local
    2009-06-26 13:02:04:706 940 10c4 PT Server URL = http://phkgensrv700:8530/SimpleAuthW...impleAuth.asmx
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: SOAP Fault: 0x00012c
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
    at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, String message, String[] clientIds)
    at Microsoft.UpdateServices.Internal.Authorization.AuthorizationManager.GetCookie(AuthorizationCookie[] authCookies, Cookie oldCookie, DateTime lastChange, DateTime currentClientTime, String clientProtocolVersion)
    at Microsoft.UpdateServices.Internal.ClientImplementation.GetCookie(AuthorizationCookie[] authCookies, Cookie oldCookie, DateTime lastChange, DateTime currentClientTime, String protocolVersion)
    at Microsoft.UpdateServices.Internal.Client.GetCookie(AuthorizationCookie[] authCookies, Cookie oldCookie, DateTime lastChange, DateTime currentTime, String protocolVersion)
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: ErrorCode:ServerChanged(4)
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: Message:Server rolled back since last call to GetCookie
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: ID:591d34f3-43a6-4fbc-ba4c-7c87f80f3342
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: PTError: 0x80244015
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: GetCookie_WithRecovery failed : 0x80244015
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: RefreshCookie failed: 0x80244015
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: RefreshPTState failed: 0x80244015
    2009-06-26 13:02:04:721 940 10c4 PT WARNING: Sync of Updates: 0x80244015
    2009-06-26 13:02:04:784 940 10c4 PT WARNING: Cached cookie has expired or new PID is available
    2009-06-26 13:02:04:784 940 10c4 PT Initializing simple targeting cookie, clientId = 89fc56e8-39a4-413f-8de9-4db9432817c2, target group = Windows 2003 Server Computers, DNS name = phkgensrv700.smi.local
    2009-06-26 13:02:04:784 940 10c4 PT Server URL = http://phkgensrv700:8530/SimpleAuthW...impleAuth.asmx
    2009-06-26 13:02:04:784 940 10c4 PT WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
    2009-06-26 13:02:04:784 940 10c4 PT WARNING: PTError: 0x80244016
    2009-06-26 13:02:04:784 940 10c4 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
    2009-06-26 13:02:05:034 940 10c4 Agent * WARNING: Failed to synchronize, error = 0x80244015
    2009-06-26 13:02:05:034 940 10c4 DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
    2009-06-26 13:02:05:034 940 10c4 Agent Server changed and need resyncing with server
    2009-06-26 13:02:05:128 940 10c4 PT +++++++++++ PT: Synchronizing server updates +++++++++++
    2009-06-26 13:02:05:128 940 10c4 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://phkgensrv700:8530/ClientWebService/client.asmx
    2009-06-26 13:02:05:174 940 10c4 PT WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
    2009-06-26 13:02:05:174 940 10c4 PT WARNING: PTError: 0x80244016
    2009-06-26 13:02:05:174 940 10c4 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
    2009-06-26 13:02:05:221 940 10c4 Agent WARNING: Failed to evaluate Installed rule, updateId = {A901C1BD-989C-45C6-8DA0-8DDE8DBB69E0}.103, hr = 8024E001
    2009-06-26 13:02:05:331 940 10c4 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2009-06-26 13:02:05:331 940 10c4 PT WARNING: SOAP Fault: 0x00012c
    2009-06-26 13:02:05:331 940 10c4 PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
    at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, String message, String[] clientIds)
    at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    2009-06-26 13:02:05:331 940 10c4 PT WARNING: ErrorCode:RegistrationRequired(3)
    2009-06-26 13:02:05:331 940 10c4 PT WARNING: Message:need to call RegisterComputer.
    2009-06-26 13:02:05:331 940 10c4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2009-06-26 13:02:05:331 940 10c4 PT WARNING: ID:72f25f66-e06d-4f91-9f5f-7b16d776613a
    2009-06-26 13:02:05:393 940 10c4 PT Initializing simple targeting cookie, clientId = 89fc56e8-39a4-413f-8de9-4db9432817c2, target group = Windows 2003 Server Computers, DNS name = phkgensrv700.smi.local
    2009-06-26 13:02:05:393 940 10c4 PT Server URL = http://phkgensrv700:8530/SimpleAuthW...impleAuth.asmx
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: PTError: 0x80244016
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: SOAP Fault: 0x00012c
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
    at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, String message, String[] clientIds)
    at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: ErrorCode:RegistrationRequired(3)
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: Message:need to call RegisterComputer.
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2009-06-26 13:02:05:409 940 10c4 PT WARNING: ID:e36403da-a578-4c8b-b1b2-9f53ad8005d4
    2009-06-26 13:02:05:471 940 10c4 PT Initializing simple targeting cookie, clientId = 89fc56e8-39a4-413f-8de9-4db9432817c2, target group = Windows 2003 Server Computers, DNS name = phkgensrv700.smi.local
    2009-06-26 13:02:05:471 940 10c4 PT Server URL = http://phkgensrv700:8530/SimpleAuthW...impleAuth.asmx
    2009-06-26 13:02:05:471 940 10c4 PT WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
    2009-06-26 13:02:05:471 940 10c4 PT WARNING: PTError: 0x80244016
    2009-06-26 13:02:05:471 940 10c4 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
    2009-06-26 13:02:05:471 940 10c4 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2009-06-26 13:02:05:471 940 10c4 PT WARNING: SOAP Fault: 0x00012c
    2009-06-26 13:02:05:471 940 10c4 PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
    at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, String message, String[] clientIds)
    at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    2009-06-26 13:02:05:487 940 10c4 PT WARNING: ErrorCode:RegistrationRequired(3)
    2009-06-26 13:02:05:487 940 10c4 PT WARNING: Message:need to call RegisterComputer.
    2009-06-26 13:02:05:487 940 10c4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2009-06-26 13:02:05:487 940 10c4 PT WARNING: ID:6622fcdd-8cd8-4c84-8e32-f544cbb1a66c
    2009-06-26 13:02:05:534 940 10c4 PT Initializing simple targeting cookie, clientId = 89fc56e8-39a4-413f-8de9-4db9432817c2, target group = Windows 2003 Server Computers, DNS name = phkgensrv700.smi.local
    2009-06-26 13:02:05:534 940 10c4 PT Server URL = http://phkgensrv700:8530/SimpleAuthW...impleAuth.asmx
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: PTError: 0x80244016
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: SOAP Fault: 0x00012c
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
    at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, String message, String[] clientIds)
    at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: ErrorCode:RegistrationRequired(3)
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: Message:need to call RegisterComputer.
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2009-06-26 13:02:05:549 940 10c4 PT WARNING: ID:52866d01-a907-4696-ae5b-e1ad493206c8
    2009-06-26 13:02:05:612 940 10c4 PT Initializing simple targeting cookie, clientId = 89fc56e8-39a4-413f-8de9-4db9432817c2, target group = Windows 2003 Server Computers, DNS name = phkgensrv700.smi.local
    2009-06-26 13:02:05:612 940 10c4 PT Server URL = http://phkgensrv700:8530/SimpleAuthW...impleAuth.asmx
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: RegisterComputer failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: PTError: 0x80244016
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80244016, Not Fatal
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: SOAP Fault: 0x00012c
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
    at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, String message, String[] clientIds)
    at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: ErrorCode:RegistrationRequired(3)
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: Message:need to call RegisterComputer.
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: ID:3765a549-e715-4d80-82f5-1930a365413b
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: PTError: 0x8024400d
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: Sync of Updates: 0x8024400d
    2009-06-26 13:02:05:628 940 10c4 PT WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2009-06-26 13:02:05:628 940 10c4 Agent * WARNING: Failed to synchronize, error = 0x8024400D
    2009-06-26 13:02:05:628 940 10c4 Agent * WARNING: Exit code = 0x8024400D
    2009-06-26 13:02:05:628 940 10c4 Agent *********
    2009-06-26 13:02:05:628 940 10c4 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-06-26 13:02:05:628 940 10c4 Agent *************
    2009-06-26 13:02:05:628 940 10c4 Agent WARNING: WU client failed Searching for update with error 0x8024400d
    2009-06-26 13:02:05:628 940 ac0 AU >>## RESUMED ## AU: Search for updates [CallId = {04106DDA-B6C2-4FA3-A18D-23AA349B84E0}]
    2009-06-26 13:02:05:628 940 ac0 AU # WARNING: Search callback failed, result = 0x8024400D
    2009-06-26 13:02:05:628 940 ac0 AU # WARNING: Failed to find updates with error code 8024400D
    2009-06-26 13:02:05:628 940 ac0 AU #########
    2009-06-26 13:02:05:628 940 ac0 AU ## END ## AU: Search for updates [CallId = {04106DDA-B6C2-4FA3-A18D-23AA349B84E0}]
    2009-06-26 13:02:05:628 940 ac0 AU #############
    2009-06-26 13:02:05:628 940 ac0 AU AU setting next detection timeout to 2009-06-26 10:02:05
    2009-06-26 13:02:10:628 940 10c4 Report REPORT EVENT: {312AA66F-F544-4042-994A-8985847C1021} 2009-06-26 13:02:05:628+0800 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400d AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400d.

  2. #2
    Lawrence Garvin [MVP] Guest

    Re: Computers not reporting to the server

    Actually, your issue is identical to the one described in this blog post
    http://blogs.technet.com/sus/archive...0d-errors.aspx

    but since you don't appear to have a load balancing scenario...

    the next most likely situation is one that emulates the situation described
    in the blog post, and that's when the machines have duplicate
    SusClientIDs -- which would likely be the case if these four machines were
    cloned from the same image.

    Try this:
    On each of these four Windows Server 2003 machines,
    Delete the registry values "SusClientID" and "SusClientIDValidation" from
    the key
    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
    and then restart the Automatic Updates service and observe the results.

  3. #3
    Join Date
    Jun 2009
    Posts
    4
    I did what you said but the problem still exists...

    BTW, my machines weren't cloned

    Next step is to start from scratch.

    I've tried reinstalling IIS and WSUS 8 times, the three servers are still unable to report

    First question: What is unique about these three servers from all other
    systems in your enterprise? What is common between these three servers?

    One server is the WSUS server itself, a member server without any other roles
    Second server is a DC and a file server
    Third server is a DC and a exchange server

    Because the issue only affects these three servers, the best course of
    action is to first consider what is common amongst them, or what is
    different about them, from the systems that do work.
    Of particular note, for me, would be this target group name "Windows 2003
    Server Computers". Are there other machines successfully working that are
    members of this group?

    Yes, 7 other servers are able to report to the WSUS server and get the updates

    Second item is to confirm that this is the only WSUS Server, and has been
    the only WSUS Server in your environment: phkgensrv700. Has the name of this
    server ever been changed? Has the database sitting behind this server ever
    been changed? Have any of the three machines with errors ever been changed
    (i.e. machine name, permissions, installed software, policies)?

    Nothing has been changed. This is the only WSUS server. The SQL server is on another machine, the database was also deleted when I uninstalled the WSUS server several times. I reinstalled WSUS because the servers/workstations are not able to get the updates but they were reporting to the server. When I reinstalled WSUS the three servers are showing up with not yet reported status and a unusual report (windows 0.0)

    I'm unable to paste the log here (maximum number of characters had exceeded)

    I've attached the log for your review.

    apologies for the wrong term I used, what I meant was the text file I've attached contains everything you asked for.

    If you said that the sum total won't be more that fifty lines, then there's definitely something wrong with my registry...

    I'll post the clientdiag result and the registry keys from the WSUS server itself

    Please take note that the clientdiag results and registry keys for HKLM\Software\Polices\Microsoft\Windows\WindowsUpdate on all the servers are the same

    The only difference is in the HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate registry key (which is more than 50 lines I suppose)

    can someone help me on this?

  4. #4
    Lawrence Garvin [MVP] Guest

    Re: Computers not reporting to the server

    Not immediately, as we've now eliminated all *known* scenarios that might
    cause this combination of errors.

    Next step is to start from scratch.

    First question: What is unique about these three servers from all other
    systems in your enterprise? What is common between these three servers?

    Because the issue only affects these three servers, the best course of
    action is to first consider what is common amongst them, or what is
    different about them, from the systems that do work.

    Of particular note, for me, would be this target group name "Windows 2003
    Server Computers". Are there other machines successfully working that are
    members of this group?

    Second item is to confirm that this is the only WSUS Server, and has been
    the only WSUS Server in your environment: phkgensrv700. Has the name of this
    server ever been changed? Has the database sitting behind this server ever
    been changed? Have any of the three machines with errors ever been changed
    (i.e. machine name, permissions, installed software, policies)?

  5. #5
    Lawrence Garvin [MVP] Guest
    Okay, let's run the Client Diagnostic Tool on all three machines, and post
    the results for analysis.

    Also, please export the registry key at
    HKLM\Software\Polices\Microsoft\Windows\WindowsUpdate
    and the registry key at
    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

    We'll take a look at that information, and then proceed from there.

    and there's no attachment.

    The sum total of what I asked you for isn't more than fifty lines of text.

    * run the Client Diagnostic Tool on all three machines, and post
    the results for analysis.

    * please export the registry key at
    HKLM\Software\Polices\Microsoft\Windows\WindowsUpdate
    and the registry key at
    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

    Not without providing the requested information.

    If it makes you feel better, you can exclude the Reporting subkey from the
    CurrentVersion\WindowsUpdate key.

    The key point, though, was that I needed to see the output from all *three*
    machines that are not reporting.

  6. #6
    Join Date
    Jun 2009
    Posts
    4

    Re: Computers not reporting to the server

    Client Diagnostic result for Server 1:

    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.2.6001.788. . . . . . . . . . . . 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://phkgensrv700:8530
    WUStatusServer = http://phkgensrv700:8530
    UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
    Connection to server. . . . . . . . . . . . . . . . . . PASS
    SelfUpdate folder is present. . . . . . . . . . . . . . PASS
    Press Enter to Complete

    Client Diagnostic result for Server 2:
    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.2.6001.788. . . . . . . . . . . . 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://phkgensrv700:8530
    WUStatusServer = http://phkgensrv700:8530
    UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
    Connection to server. . . . . . . . . . . . . . . . . . PASS
    SelfUpdate folder is present. . . . . . . . . . . . . . PASS
    Press Enter to Complete

    Client Diagnostic result for Server 3:
    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.2.6001.788. . . . . . . . . . . . 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://phkgensrv700:8530
    WUStatusServer = http://phkgensrv700:8530
    UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
    Connection to server. . . . . . . . . . . . . . . . . . PASS
    SelfUpdate folder is present. . . . . . . . . . . . . . PASS
    Press Enter to Complete

    Registry for Server 1:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate]
    "SusClientId"="5d1a2af9-ec62-498d-becc-184465e77aeb"
    "SusClientIdValidation"=hex:04,01,10,01,42,00,41,00,39,00,34,00,44,00,43,00,39,\
    00,35,00,06,00,1e,68,57,74,b9

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
    "NextDetectionTime"="2009-06-28 15:41:21"
    "UnableToDetectTime"="2009-06-28 08:06:11"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Detect]
    "LastError"=dword:8024400d

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting]
    "BatchFlushAge"=dword:000072ac
    "SamplingValue2"=dword:0000020b

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\EventCache]

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\RebootWatch]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\7971f918-a847-4430-9279-4a52d1efe18d]
    "AuthorizationCab"="authcab.cab"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending]
    "ValidatedPreWsus3RegistrationRequests"=dword:00000001


    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate]
    "WUServer"="http://phkgensrv700:8530"
    "WUStatusServer"="http://phkgensrv700:8530"
    "TargetGroupEnabled"=dword:00000001
    "TargetGroup"="Windows 2003 Server Computers"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\AU]
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000003
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:00000003
    "AutoInstallMinorUpdates"=dword:00000001
    "UseWUServer"=dword:00000001
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000008

    Registry for Server 2:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate]
    "SusClientIdValidation"=hex:04,01,10,01,36,00,32,00,33,00,39,00,41,00,41,00,36,\
    00,35,00,06,00,1e,68,57,78,13
    "SusClientId"="d8926466-fc2f-4a5f-b5c6-2915badb4056"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
    "AUOptions"=dword:00000001
    "NextDetectionTime"="2009-06-28 15:41:40"
    "BalloonTime"="2009-06-26 06:21:33"
    "BalloonType"=dword:00000005
    "ConfigVer"=dword:00000001
    "UnableToDetectTime"="2009-06-26 13:57:58"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Detect]
    "LastSuccessTime"="2009-06-26 06:21:18"
    "LastError"=dword:8024400d

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Download]
    "LastSuccessTime"="2009-06-26 06:21:28"
    "LastError"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Install]
    "LastSuccessTime"="2009-05-31 12:16:51"
    "LastError"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting]
    "BatchFlushAge"=dword:00008b68
    "SamplingValue2"=dword:00000333

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\EventCache]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\RebootWatch]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services]
    "DefaultService"="7971f918-a847-4430-9279-4a52d1efe18d"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\7971f918-a847-4430-9279-4a52d1efe18d]
    "AuthorizationCab"="authcab.cab"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending]
    "ValidatedPreWsus3RegistrationRequests"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup\ServiceStartup]


    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate]
    "WUServer"="http://phkgensrv700:8530"
    "WUStatusServer"="http://phkgensrv700:8530"
    "TargetGroupEnabled"=dword:00000001
    "TargetGroup"="Windows 2003 Server Computers"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\AU]
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000003
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:00000003
    "AutoInstallMinorUpdates"=dword:00000001
    "UseWUServer"=dword:00000001
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000008

    Registry for Server 3:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate]
    "SusClientIdValidation"=hex:04,01,10,01,45,00,31,00,44,00,46,00,33,00,44,00,46,\
    00,35,00,06,00,1b,24,e0,40,57
    "SusClientId"="df2dd88c-3f23-4787-8635-9eba9ee4f456"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
    "AUOptions"=dword:00000001
    "NextDetectionTime"="2009-06-28 15:41:23"
    "BalloonTime"="2009-04-29 01:05:23"
    "BalloonType"=dword:00000005
    "ConfigVer"=dword:00000001
    "UnableToDetectTime"="2009-06-27 11:21:53"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Detect]
    "LastSuccessTime"="2009-06-15 10:25:36"
    "LastError"=dword:8024400d

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Download]
    "LastSuccessTime"="2009-05-31 03:38:59"
    "LastError"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Install]
    "LastSuccessTime"="2009-05-31 03:39:07"
    "LastError"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting]
    "BatchFlushAge"=dword:0000138d
    "SamplingValue2"=dword:00000168

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\EventCache]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\RebootWatch]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services]
    "DefaultService"="7971f918-a847-4430-9279-4a52d1efe18d"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\7971f918-a847-4430-9279-4a52d1efe18d]
    "AuthorizationCab"="authcab.cab"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending]
    "ValidatedPreWsus3RegistrationRequests"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup\ServiceStartup]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate]
    "WUServer"="http://phkgensrv700:8530"
    "WUStatusServer"="http://phkgensrv700:8530"
    "TargetGroupEnabled"=dword:00000001
    "TargetGroup"="Windows 2003 Server Computers"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\AU]
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000003
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:00000003
    "AutoInstallMinorUpdates"=dword:00000001
    "UseWUServer"=dword:00000001
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000008

  7. #7
    Lawrence Garvin [MVP] Guest

    Re: Computers not reporting to the server

    It seems the first failure was Server #2 early in the afternoon on June
    26th.

    What else was going on with your WSUS Server or NETWORK on June 26th?

    I also noted a couple other anomalous items...

    Server #1 has failed, but has not recorded a "Last Success Time". Has Server
    #1 ever successfully registered/detected with this WSUS Server?

    Server #2 shows a LastSuccessTime at 6:21am on June 26th, so that helps us
    narrow down the time frame in which "something changed" to a very concise
    7.5 hour window (6:20am - 2:00pm).

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\Results\Detect]
    "LastSuccessTime"="2009-06-26 06:21:18"

    Server #3 shows a LastSuccessTime of June 15th, so either this was the first
    server to be subject to whatever changed -- or it's an entirely different
    cause.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
    Update\Results\Detect]
    "LastSuccessTime"="2009-06-15 10:25:36"

    Which of those three machines is which?
    Which is the WSUS Server?
    Which is the DC with Exchange?
    Which is the DC/File Server?

  8. #8
    Join Date
    Jun 2009
    Posts
    4

    Re: Computers not reporting to the server

    It seems the first failure was Server #2 early in the afternoon on June
    26th.

    What else was going on with your WSUS Server or NETWORK on June 26th?

    I also noted a couple other anomalous items...

  9. #9
    Join Date
    Aug 2010
    Posts
    2

    Re: Computers not reporting to the server

    Hi Lawrence Garvin,

    On behalf of oohdeck. i will take his place on troubleshooting the wsus.

    please let me know what info you need.

    for you last post.

    #########

    It seems the first failure was Server #2 early in the afternoon on June
    26th.

    What else was going on with your WSUS Server or NETWORK on June 26th?
    -if I'm not mistaken last year we tried to upgrade the wsus from sp1 to sp2. however, we encounter problem during upgrade.
    therefore we roll back the installation, but again a problem occurred upon roll back. For one week or two the wsus is not working properly
    by then we decided to reinstalled the wsus.

    after the re-installation, it seems all clients were reporting back to the server including the 3 servers, so it still working until end of year 2009.
    Upon reviewing all wsus report the problem start on January this year and some servers were not reporting back.

    That's the story behind.

    I also noted a couple other anomalous items...

    Server #1 has failed, but has not recorded a "Last Success Time".
    Has Server #1 ever successfully registered/detected with this WSUS Server?

    Server #2 shows a LastSuccessTime at 6:21am on June 26th, so that helps us
    narrow down the time frame in which "something changed" to a very concise
    7.5 hour window (6:20am - 2:00pm).

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\Auto
    Update\Results\Detect]
    "LastSuccessTime"="2009-06-26 06:21:18"

    Server #3 shows a LastSuccessTime of June 15th, so either this was the first
    server to be subject to whatever changed -- or it's an entirely different
    cause.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\Auto
    Update\Results\Detect]
    "LastSuccessTime"="2009-06-15 10:25:36"

    Which of those three machines is which?
    Which is the WSUS Server?
    Which is the DC with Exchange?
    Which is the DC/File Server?
    -I cannot determine which of them is the wsus server and the dc.
    Last edited by water pei; 06-08-2010 at 11:46 AM.

Similar Threads

  1. Replies: 5
    Last Post: 03-09-2011, 10:59 PM
  2. Clients not reporting to WSUS server
    By Leland in forum Server Update Service
    Replies: 10
    Last Post: 10-11-2009, 09:35 PM
  3. No computers reporting and LOTS of 80244019
    By Donnell in forum Server Update Service
    Replies: 6
    Last Post: 19-10-2009, 03:34 PM
  4. How to sum groups of data sql server reporting services
    By joel84 in forum Operating Systems
    Replies: 3
    Last Post: 14-08-2009, 02:12 PM
  5. Congfigure SQL Server Reporting Services
    By Laler in forum Networking & Security
    Replies: 3
    Last Post: 22-04-2009, 11:40 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,855,189.51132 seconds with 17 queries