Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > WSUS Client Failed to detect Approved Updates

Reply
Thread Tools Display Modes

WSUS Client Failed to detect Approved Updates

 
 
SAFairfax
Guest
Posts: n/a

 
      12-02-2007
I saw the previous posting and replies from Lawrence Garvin. I tried the 7
steps solutions but the client still detects 0 updates. Since I am not
targeting specific user accounts, I disabled User Configuraiton section in
the GPO.

The client received and installed the first few patches and then failed to
detect further patches.

Please help.

Here is ReportingEvents.log
{38CCA97E-FAD8-4A43-8E51-FC62D45176AC} 2007-12-02
18:18:23:381-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
{2065DEE6-92E1-4557-B302-D0628B41C6BC} 2007-12-02
18:18:23:381-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.


Here is the content of WindowsUpdates.log since last creation of new SUS id:
updates +++++++++++
2007-12-02 18:15:52:704 908 62c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://op-s-su-1/ClientWebService/client.asmx
2007-12-02 18:15:52:767 908 62c Agent Switching to hardware-verified
ClientId.
2007-12-02 18:15:52:799 908 62c PT WARNING: Cached cookie has expired or
new PID is available
2007-12-02 18:15:53:069 908 62c Agent Created new random SusClientId
df4e0235-b4c8-45f8-aebf-4ac049901628. Old Id:
4340fc8f-9653-4947-92fc-c4c3836d487c.
2007-12-02 18:15:53:069 908 62c PT Initializing simple targeting cookie,
clientId = df4e0235-b4c8-45f8-aebf-4ac049901628, target group = Pilot1, DNS
name = cl-d-sus2.stanleyassociates.com
2007-12-02 18:15:53:069 908 62c PT Server URL =
http://op-s-su-1/SimpleAuthWebService/SimpleAuth.asmx
2007-12-02 18:18:18:113 908 62c PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2007-12-02 18:18:18:113 908 62c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://op-s-su-1/ClientWebService/client.asmx
2007-12-02 18:18:23:381 908 62c Agent * Found 0 updates and 33 categories
in search; evaluated appl. rules of 820 out of 1190 deployed entities
2007-12-02 18:18:23:381 908 62c Agent *********
2007-12-02 18:18:23:381 908 62c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-12-02 18:18:23:381 908 62c Agent *************
2007-12-02 18:18:23:381 908 158 AU >>## RESUMED ## AU: Search for updates
[CallId = {BB9BA4CC-6FB1-4CC0-A6D8-5715E85528F9}]
2007-12-02 18:18:23:381 908 158 AU # 0 updates detected
2007-12-02 18:18:23:381 908 158 AU #########
2007-12-02 18:18:23:381 908 158 AU ## END ## AU: Search for updates
[CallId = {BB9BA4CC-6FB1-4CC0-A6D8-5715E85528F9}]
2007-12-02 18:18:23:381 908 158 AU #############
2007-12-02 18:18:23:397 908 158 AU AU setting next detection timeout to
2007-12-03 00:17:56
2007-12-02 18:18:23:397 908 158 AU Setting AU scheduled install time to
2007-12-03 00:00:00
2007-12-02 18:18:28:459 908 62c Report REPORT EVENT:
{38CCA97E-FAD8-4A43-8E51-FC62D45176AC} 2007-12-02
18:18:23:381-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2007-12-02 18:18:28:459 908 62c Report REPORT EVENT:
{2065DEE6-92E1-4557-B302-D0628B41C6BC} 2007-12-02
18:18:23:381-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2007-12-02 18:24:04:268 908 62c Report Uploading 2 events using cached
cookie, reporting URL =
http://op-s-su-1/ReportingWebService...ebService.asmx
2007-12-02 18:24:04:300 908 62c Report Reporter successfully uploaded 2
events.
2007-12-02 18:26:22:341 908 4c4 AU Windows Update is disabled by policy for
user

 
Reply With Quote
 
 
 
 
PA Bear
Guest
Posts: n/a

 
      12-02-2007
Forwarded to WSUS newsgroup via crosspost:
microsoft.public.windows.server.update_services as a convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L.ORG http://66.39.69.143/


SAFairfax wrote:
> I saw the previous posting and replies from Lawrence Garvin. I tried the
> 7
> steps solutions but the client still detects 0 updates. Since I am not
> targeting specific user accounts, I disabled User Configuraiton section in
> the GPO.
>
> The client received and installed the first few patches and then failed to
> detect further patches.
>
> Please help.
>
> Here is ReportingEvents.log
> {38CCA97E-FAD8-4A43-8E51-FC62D45176AC} 2007-12-02
> 18:18:23:381-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
> AutomaticUpdates Success Software
> Synchronization Windows Update Client successfully detected 0 updates.
> {2065DEE6-92E1-4557-B302-D0628B41C6BC} 2007-12-02
> 18:18:23:381-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0
> AutomaticUpdates Success Pre-Deployment Check Reporting client status.
>
>
> Here is the content of WindowsUpdates.log since last creation of new SUS
> id:
> updates +++++++++++
> 2007-12-02 18:15:52:704 908 62c PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://op-s-su-1/ClientWebService/client.asmx
> 2007-12-02 18:15:52:767 908 62c Agent Switching to hardware-verified
> ClientId.
> 2007-12-02 18:15:52:799 908 62c PT WARNING: Cached cookie has expired or
> new PID is available
> 2007-12-02 18:15:53:069 908 62c Agent Created new random SusClientId
> df4e0235-b4c8-45f8-aebf-4ac049901628. Old Id:
> 4340fc8f-9653-4947-92fc-c4c3836d487c.
> 2007-12-02 18:15:53:069 908 62c PT Initializing simple targeting cookie,
> clientId = df4e0235-b4c8-45f8-aebf-4ac049901628, target group = Pilot1,
> DNS
> name = cl-d-sus2.stanleyassociates.com
> 2007-12-02 18:15:53:069 908 62c PT Server URL =
> http://op-s-su-1/SimpleAuthWebService/SimpleAuth.asmx
> 2007-12-02 18:18:18:113 908 62c PT +++++++++++ PT: Synchronizing extended
> update info +++++++++++
> 2007-12-02 18:18:18:113 908 62c PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://op-s-su-1/ClientWebService/client.asmx
> 2007-12-02 18:18:23:381 908 62c Agent * Found 0 updates and 33
> categories
> in search; evaluated appl. rules of 820 out of 1190 deployed entities
> 2007-12-02 18:18:23:381 908 62c Agent *********
> 2007-12-02 18:18:23:381 908 62c Agent ** END ** Agent: Finding updates
> [CallerId = AutomaticUpdates]
> 2007-12-02 18:18:23:381 908 62c Agent *************
> 2007-12-02 18:18:23:381 908 158 AU >>## RESUMED ## AU: Search for
> updates
> [CallId = {BB9BA4CC-6FB1-4CC0-A6D8-5715E85528F9}]
> 2007-12-02 18:18:23:381 908 158 AU # 0 updates detected
> 2007-12-02 18:18:23:381 908 158 AU #########
> 2007-12-02 18:18:23:381 908 158 AU ## END ## AU: Search for updates
> [CallId = {BB9BA4CC-6FB1-4CC0-A6D8-5715E85528F9}]
> 2007-12-02 18:18:23:381 908 158 AU #############
> 2007-12-02 18:18:23:397 908 158 AU AU setting next detection timeout to
> 2007-12-03 00:17:56
> 2007-12-02 18:18:23:397 908 158 AU Setting AU scheduled install time to
> 2007-12-03 00:00:00
> 2007-12-02 18:18:28:459 908 62c Report REPORT EVENT:
> {38CCA97E-FAD8-4A43-8E51-FC62D45176AC} 2007-12-02
> 18:18:23:381-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
> AutomaticUpdates Success Software
> Synchronization Windows Update Client successfully detected 0 updates.
> 2007-12-02 18:18:28:459 908 62c Report REPORT EVENT:
> {2065DEE6-92E1-4557-B302-D0628B41C6BC} 2007-12-02
> 18:18:23:381-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0
> AutomaticUpdates Success Pre-Deployment Check Reporting client status.
> 2007-12-02 18:24:04:268 908 62c Report Uploading 2 events using cached
> cookie, reporting URL =
> http://op-s-su-1/ReportingWebService...ebService.asmx
> 2007-12-02 18:24:04:300 908 62c Report Reporter successfully uploaded 2
> events.
> 2007-12-02 18:26:22:341 908 4c4 AU Windows Update is disabled by policy
> for
> user


 
Reply With Quote
 
Lawrence Garvin [MVP]
Guest
Posts: n/a

 
      12-04-2007
> SAFairfax wrote:

>> 2007-12-02 18:15:53:069 908 62c PT Initializing simple targeting cookie,
>> clientId = df4e0235-b4c8-45f8-aebf-4ac049901628, target group = Pilot1,
>> DNS name = cl-d-sus2.stanleyassociates.com


>> 2007-12-02 18:18:23:381 908 62c Agent * Found 0 updates and 33
>> categories
>> in search; evaluated appl. rules of 820 out of 1190 deployed entities


It does seem, quite simply, as the log indicates -- that the updates have
not been approved for the "Pilot1" target group.




--
Lawrence Garvin, M.S., MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
MVP - Software Distribution (2005-2007)

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

 
Reply With Quote
 
SAFairfax
Guest
Posts: n/a

 
      12-05-2007
75 patches were approved, 5 were pushed down and installed, and the rest were
not detected.

I can send you the screenshots to show that they were approved for Pilot1.

Also, those patches seems to always have the status of "downloading".

I duplicated this in my test lab and it is exhibiting a different - majority
of the patches were downloaded but only the same patches were applied.

Your help is very much appreciated!

"Lawrence Garvin [MVP]" wrote:

> > SAFairfax wrote:

>
> >> 2007-12-02 18:15:53:069 908 62c PT Initializing simple targeting cookie,
> >> clientId = df4e0235-b4c8-45f8-aebf-4ac049901628, target group = Pilot1,
> >> DNS name = cl-d-sus2.stanleyassociates.com

>
> >> 2007-12-02 18:18:23:381 908 62c Agent * Found 0 updates and 33
> >> categories
> >> in search; evaluated appl. rules of 820 out of 1190 deployed entities

>
> It does seem, quite simply, as the log indicates -- that the updates have
> not been approved for the "Pilot1" target group.
>
>
>
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Senior Data Architect, APQC, Houston, Texas
> MVP - Software Distribution (2005-2007)
>
> 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
>
>

 
Reply With Quote
 
Lawrence Garvin [MVP]
Guest
Posts: n/a

 
      12-05-2007
"SAFairfax" <> wrote in message
news:51C4F47F-82F0-4495-800E-...
> 75 patches were approved, 5 were pushed down and installed, and the rest
> were
> not detected.
>
> I can send you the screenshots to show that they were approved for Pilot1.
>
> Also, those patches seems to always have the status of "downloading".


Uh.. "downloading" to where? To the /WSUS Server/???

If so, that would definitely account for the clients not seeing the updates.

A client system cannot detect an update (and obviously not download/install)
until the update content is successfully downloaded to the WSUS Server.

Review the server Application Event Log for information concerning failures
to download content from microsoft.com



--
Lawrence Garvin, M.S., MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
MVP - Software Distribution (2005-2007)

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

 
Reply With Quote
 
SAFairfax
Guest
Posts: n/a

 
      12-05-2007
It is not indicative of which direction it is downloading... either from
Windows Update website to the WSUS server or from the WSUS server to the
client. We have downloaded all the patches previously.

In the test lab environment, prior to installing the patches, it did
download a bunch of patches (System log event id 18) but it only install the
first 5 and failed to see the rest).

I will try to download again and see what happen...

Thanks for your quick response!

"Lawrence Garvin [MVP]" wrote:

> "SAFairfax" <> wrote in message
> news:51C4F47F-82F0-4495-800E-...
> > 75 patches were approved, 5 were pushed down and installed, and the rest
> > were
> > not detected.
> >
> > I can send you the screenshots to show that they were approved for Pilot1.
> >
> > Also, those patches seems to always have the status of "downloading".

>
> Uh.. "downloading" to where? To the /WSUS Server/???
>
> If so, that would definitely account for the clients not seeing the updates.
>
> A client system cannot detect an update (and obviously not download/install)
> until the update content is successfully downloaded to the WSUS Server.
>
> Review the server Application Event Log for information concerning failures
> to download content from microsoft.com
>
>
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Senior Data Architect, APQC, Houston, Texas
> MVP - Software Distribution (2005-2007)
>
> 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
>

 
Reply With Quote
 
Harry Johnston [MVP]
Guest
Posts: n/a

 
      12-05-2007
SAFairfax wrote:

> It is not indicative of which direction it is downloading... either from
> Windows Update website to the WSUS server or from the WSUS server to the
> client.


Where does the word "downloading" appear? Perhaps you should post a screenshot.

Harry.
 
Reply With Quote
 
Lawrence Garvin [MVP]
Guest
Posts: n/a

 
      12-05-2007
"SAFairfax" <> wrote in message
news:B81EB020-9422-4B68-847D-...
> It is not indicative of which direction it is downloading... either from
> Windows Update website to the WSUS server or from the WSUS server to the
> client. We have downloaded all the patches previously.


Okay.. let me try this another way. :-)

WHAT is saying it is downloading? The WSUS Admin Console.. or the CLIENT
system?


> In the test lab environment, prior to installing the patches, it did
> download a bunch of patches (System log event id 18) but it only install
> the
> first 5 and failed to see the rest).


Yes.. it's sounding more and more like the server simply has not downloaded
the content.

--
Lawrence Garvin, M.S., MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
MVP - Software Distribution (2005-2007)

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

 
Reply With Quote
 
SAFairfax
Guest
Posts: n/a

 
      12-05-2007
In the WSUS console, if you display the "File Status" column, I see the a
page icon with the arrow pointing downward. If you move the mouse over it,
it will show the text as "The update is downloading now...". I am pretty
sure we have downloaded all the necessary updates not just for XP, but also
for other OS platforms.

My only question is if the patches have been downloaded to the WSUS server,
is stopping Update Services going to affect the patch deployment behavior?
It seems to me that there is some sort of dependency.

I realized the issue could be caused by the "Update Services" was stopped to
avoid more downloads from Windows Update website. As soon as I restarted it,
the updates were downloaded immediately and installed at the next
installation interval. It has downloaded and installed 18 updates today and
then rebooted itself and wait for next installation interval.

I read in the forum that one way to force all the patches to be installed
immediately (multiple reboots) is to set the deadline to past date?

Thank you all for chipping in...





"Lawrence Garvin [MVP]" wrote:

> "SAFairfax" <> wrote in message
> news:B81EB020-9422-4B68-847D-...
> > It is not indicative of which direction it is downloading... either from
> > Windows Update website to the WSUS server or from the WSUS server to the
> > client. We have downloaded all the patches previously.

>
> Okay.. let me try this another way. :-)
>
> WHAT is saying it is downloading? The WSUS Admin Console.. or the CLIENT
> system?
>
>
> > In the test lab environment, prior to installing the patches, it did
> > download a bunch of patches (System log event id 18) but it only install
> > the
> > first 5 and failed to see the rest).

>
> Yes.. it's sounding more and more like the server simply has not downloaded
> the content.
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Senior Data Architect, APQC, Houston, Texas
> MVP - Software Distribution (2005-2007)
>
> 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
>

 
Reply With Quote
 
Harry Johnston [MVP]
Guest
Posts: n/a

 
      12-05-2007
SAFairfax wrote:

> In the WSUS console, if you display the "File Status" column, I see the a
> page icon with the arrow pointing downward. If you move the mouse over it,
> it will show the text as "The update is downloading now...". I am pretty
> sure we have downloaded all the necessary updates not just for XP, but also
> for other OS platforms.


(Sigh.) What made you think you had already downloaded the updates if WSUS was
saying that they were downloading?

The front page of the WSUS console shows you the overall status of the WSUS
server's downloads from Microsoft. Does it now say "Updates needing files: 0"?

> My only question is if the patches have been downloaded to the WSUS server,
> is stopping Update Services going to affect the patch deployment behavior?


No, I don't think so; but it'll certainly prevent your WSUS server from
downloading updates. There's no good reason to turn it off; just leave it alone.

Harry.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
WSUS Client Update Failed with Error Code 0xC8000643 sas Windows Update 4 07-07-2008 10:22 PM
WSUS and client updates jmp Windows Update 1 03-17-2006 09:50 AM
Script to detect all 'detect only' updates or known wsus server updates Dim Windows Update 1 02-27-2006 08:58 AM
Script to detect all 'detect only' updates or known wsus server updates Dim Windows Update 0 02-15-2006 08:39 AM
Error 0x800710DD when trying to detect WSUS client Faris Abu Rous Windows Update 1 05-25-2005 10:19 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59