|
| |||||||||
| Tags: clients, reporting, wsus |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| WSUS 3.0 SP1: Vista Clients not reporting
Setup is a Windows 2003 running WSUS 3.0 with SP1 and client computers running Vista with SP1. The client computers are not being picked up by the WSUS server. From the Windowsuplog on one of the clients, here is an example: ***** <<## SUBMITTED ## AU: Search for updates [CallId = {1AB5FAE3-D963-4D97-92D4-2C8C4853D07A}] ************* ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] ********* * Online = Yes; Ignore download priority = No * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1" * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} * Search Scope = {Machine} Checking for agent SelfUpdate Client version: Core: 7.2.6001.784 Aux: 7.2.6001.784 Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab: Microsoft signed: Yes Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab: Microsoft signed: Yes Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab: Microsoft signed: Yes Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab: Microsoft signed: Yes Determining whether a new setup handler needs to be downloaded SelfUpdate handler is not found. It will be downloaded Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.1.6001.65" Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.1.6001.65" is not applicable Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" is not applicable Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" is not applicable SelfUpdate check completed. SelfUpdate is NOT required. +++++++++++ PT: Synchronizing server updates +++++++++++ + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://FQDN/ClientWebService/client.asmx WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404 WARNING: PTError: 0x80244019 WARNING: GetConfig_WithRecovery failed: 0x80244019 WARNING: RefreshConfig failed: 0x80244019 WARNING: RefreshPTState failed: 0x80244019 WARNING: Sync of Updates: 0x80244019 WARNING: SyncServerUpdatesInternal failed: 0x80244019 * WARNING: Failed to synchronize, error = 0x80244019 * WARNING: Exit code = 0x80244019 ********* ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] ************* WARNING: WU client failed Searching for update with error 0x80244019 >>## RESUMED ## AU: Search for updates [CallId = {1AB5FAE3-D963-4D97-92D4-2C8C4853D07A}] # WARNING: Search callback failed, result = 0x80244019 # WARNING: Failed to find updates with error code 80244019 ######### ## END ## AU: Search for updates [CallId = {1AB5FAE3-D963-4D97-92D4-2C8C4853D07A}] ############# Need to show Unable to Detect notification AU setting next detection timeout to 2008-11-19 18:58:17 Setting AU scheduled install time to 2008-11-20 02:00:00 REPORT EVENT: {E14338BC-1169-491C-B8F0-0F46D480D99B} 2008-11-19 08:58:17:544-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019. ***** using the clientdiag.exe C:\WSUSTools>clientdiag.exe 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.784. . . . . . . . . . . . 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://FQDN WUStatusServer = http://FQDN UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS Client is pointed to SUS 1.0 Server Connection to server. . . . . . . . . . . . . . . . . . PASS SelfUpdate folder is present. . . . . . . . . . . . . . PASS Press Enter to Complete Any help would be appreciated. Thanks Terru |
|
#2
| |||
| |||
| Re: WSUS 3.0 SP1: Vista Clients not reporting
[[Right pew, wrong church. Forwarded to WSUS newsgroup (microsoft.public.windows.server.update_services) via crosspost as a convenience to OP. On the web: http://www.microsoft.com/communities...pdate_services In your newsreader: news://msnews.microsoft.com/microsof...ate_services]] Terry wrote: > Setup is a Windows 2003 running WSUS 3.0 with SP1 and client computers > running Vista with SP1. > > The client computers are not being picked up by the WSUS server. > > > From the Windowsuplog on one of the clients, here is an example: > > ***** > <<## SUBMITTED ## AU: Search for updates [CallId = > {1AB5FAE3-D963-4D97-92D4-2C8C4853D07A}] > ************* > ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] > ********* > * Online = Yes; Ignore download priority = No > * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or > IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and > DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and > DeploymentAction='Uninstallation' and RebootRequired=1" > * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} > * Search Scope = {Machine} > Checking for agent SelfUpdate > Client version: Core: 7.2.6001.784 Aux: 7.2.6001.784 > Validating signature for > C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab: > Microsoft signed: Yes > Validating signature for > C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab: > Microsoft signed: Yes > Validating signature for > C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab: > Microsoft signed: Yes > Validating signature for > C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab: > Microsoft signed: Yes > Determining whether a new setup handler needs to be downloaded > SelfUpdate handler is not found. It will be downloaded > Evaluating applicability of setup package > "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.1.6001.65" > Setup package > "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.1.6001.65" is not > applicable > Evaluating applicability of setup package > "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" > Setup package > "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" is > not > applicable > Evaluating applicability of setup package > "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" > Setup package > "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.1.6001.65" is > not > applicable > SelfUpdate check completed. SelfUpdate is NOT required. > +++++++++++ PT: Synchronizing server updates +++++++++++ > + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = > http://FQDN/ClientWebService/client.asmx > WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, > soap > error code = 0, HTTP status code = 404 > WARNING: PTError: 0x80244019 > WARNING: GetConfig_WithRecovery failed: 0x80244019 > WARNING: RefreshConfig failed: 0x80244019 > WARNING: RefreshPTState failed: 0x80244019 > WARNING: Sync of Updates: 0x80244019 > WARNING: SyncServerUpdatesInternal failed: 0x80244019 > * WARNING: Failed to synchronize, error = 0x80244019 > * WARNING: Exit code = 0x80244019 > ********* > ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] > ************* > WARNING: WU client failed Searching for update with error 0x80244019 >>> ## RESUMED ## AU: Search for updates [CallId = >>> {1AB5FAE3-D963-4D97-92D4-2C8C4853D07A}] > # WARNING: Search callback failed, result = 0x80244019 > # WARNING: Failed to find updates with error code 80244019 > ######### > ## END ## AU: Search for updates [CallId = > {1AB5FAE3-D963-4D97-92D4-2C8C4853D07A}] > ############# > Need to show Unable to Detect notification > AU setting next detection timeout to 2008-11-19 18:58:17 > Setting AU scheduled install time to 2008-11-20 02:00:00 > REPORT EVENT: {E14338BC-1169-491C-B8F0-0F46D480D99B} 2008-11-19 > 08:58:17:544-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 > 80244019 AutomaticUpdates Failure Software Synchronization Windows Update > Client failed to detect with error 0x80244019. ***** > > using the clientdiag.exe > > C:\WSUSTools>clientdiag.exe > > 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.784. . . . . . . . . . . . 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://FQDN > WUStatusServer = http://FQDN > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS > Client is pointed to SUS 1.0 Server > Connection to server. . . . . . . . . . . . . . . . . . PASS > SelfUpdate folder is present. . . . . . . . . . . . . . PASS > > Press Enter to Complete > > Any help would be appreciated. > > > Thanks > > Terru |
|
#3
| |||
| |||
| Re: WSUS 3.0 SP1: Vista Clients not reporting
> Terry wrote: >> Setup is a Windows 2003 running WSUS 3.0 with SP1 and client computers >> running Vista with SP1. >> >> The client computers are not being picked up by the WSUS server. >> + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = >> http://FQDN/ClientWebService/client.asmx >> WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, >> Checking Connection to WSUS/SUS Server >> WUServer = http://FQDN >> WUStatusServer = http://FQDN >> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS >> Client is pointed to SUS 1.0 Server >> Connection to server. . . . . . . . . . . . . . . . . . PASS >> SelfUpdate folder is present. . . . . . . . . . . . . . PASS You've misconfigured the URL for your WSUS Server. Given historical observations of these symptoms, [a] A '404' error trying to access /clientwebservice/client.asmx on port 80 [b] The CDT reporting that the port 80 server is a "SUS 1.0 Server" (which simply means that there is no WSUS Server installed on port 80) [c] The confirmed presence of /selfupdate on the port 80 server I'd make a solid bet that your WSUS server is actually installed on the alternate virtual server, and thus the correct URL should be http://hostname:8530 -- Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009) MS WSUS Website: http://www.microsoft.com/wsus My Websites: http://www.onsitechsolutions.com; http://wsusinfo.onsitechsolutions.com My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin |
|
#4
| |||
| |||
| Re: WSUS 3.0 SP1: Vista Clients not reporting
Lawrence You are correct and I added the port to the address through GP and everything appears to be responding properly now. Thanks "Lawrence Garvin (MVP)" wrote: > > Terry wrote: > >> Setup is a Windows 2003 running WSUS 3.0 with SP1 and client computers > >> running Vista with SP1. > >> > >> The client computers are not being picked up by the WSUS server. > > >> + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = > >> http://FQDN/ClientWebService/client.asmx > >> WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, > > >> Checking Connection to WSUS/SUS Server > >> WUServer = http://FQDN > >> WUStatusServer = http://FQDN > >> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS > >> Client is pointed to SUS 1.0 Server > >> Connection to server. . . . . . . . . . . . . . . . . . PASS > >> SelfUpdate folder is present. . . . . . . . . . . . . . PASS > > You've misconfigured the URL for your WSUS Server. > > Given historical observations of these symptoms, > [a] A '404' error trying to access /clientwebservice/client.asmx on port > 80 > [b] The CDT reporting that the port 80 server is a "SUS 1.0 Server" > (which simply means that there is no WSUS Server installed on > port 80) > [c] The confirmed presence of /selfupdate on the port 80 server > > I'd make a solid bet that your WSUS server is actually installed on the > alternate virtual server, > and thus the correct URL should be http://hostname:8530 > > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus > My Websites: http://www.onsitechsolutions.com; > http://wsusinfo.onsitechsolutions.com > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin > > |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "WSUS 3.0 SP1: Vista Clients not reporting" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Clients not reporting to WSUS server | Andrew Story | Server Update Service | 10 | 10-11-2009 09:35 PM |
| 1 Out Of 30+ Clients Not Reporting In WSUS - Error 8007007a | Gramps98 | Server Update Service | 6 | 08-07-2009 01:23 AM |
| WSUS upgrade from 2.0 - 3.0 and now only some clients reporting | crazdt | Server Update Service | 21 | 16-08-2008 02:55 AM |
| clients not reporting status after updating WSUS 2 to WSUS 3.0 | Veronika | Server Update Service | 5 | 17-07-2007 10:37 PM |
| After WSUS 3.0 Install Clients Not Reporting In - Another Issue | gdwanderson@gmail.com | Server Update Service | 1 | 23-05-2007 09:44 PM |