Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.update_services
Thread: Every client visible on WSUS 3.0 server, but no clients updating

HTVi
TV Discussion Newsgroups

Every client visible on WSUS 3.0 server, but no clients updating
glgcag 10/28/2008 9:55:01 PM
I have spent hours looking for a solution to my problem to no avail. I hope
someone here can help me!

I have a new install of WSUS 3.0 on Win2k3 server that I had to move because
the old server crashed. I changed the GPO for all my clients to the new
server and confirmed that all workstations and servers are visible on the
WSUS server. I have the proper permissions in IIS, proper ports, proper
registry settings and I'm getting "0 updates detected" in the
WindowsUpdate.log on the clients even though there are updates needed.

On the GPO I have the TargetGroup as "All Computers" though there is a
Server and Workstations group that I assign each computer to respectively
once it appears in WSUS. I'm wondering if the grouping is the problem?

Here's the last wuaclt.exe /detectnow that I ran (after restarting Automatic
Updates service) from the WindowsUpdate.log:

2008-10-28 14:40:20:169 1836 1438 Service *************
2008-10-28 14:40:20:169 1836 1438 Service ** START ** Service: Service
startup
2008-10-28 14:40:20:169 1836 1438 Service *********
2008-10-28 14:40:20:169 1836 1438 Agent * WU client version 7.1.6001.65
2008-10-28 14:40:20:169 1836 1438 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2008-10-28 14:40:20:169 1836 1438 Agent * Access type: No proxy
2008-10-28 14:40:20:169 1836 1438 Agent * Network state: Connected
2008-10-28 14:41:05:653 1836 1438 Agent *********** Agent: Initializing
Windows Update Agent ***********
2008-10-28 14:41:05:653 1836 1438 Agent *********** Agent: Initializing
global settings cache ***********
2008-10-28 14:41:05:653 1836 1438 Agent * WSUS server: http://BES01a
2008-10-28 14:41:05:653 1836 1438 Agent * WSUS status server: http://BES01a
2008-10-28 14:41:05:653 1836 1438 Agent * Target group: Workstations
2008-10-28 14:41:05:653 1836 1438 Agent * Windows Update access disabled: No
2008-10-28 14:41:05:653 1836 1438 DnldMgr Download manager restoring 0
downloads
2008-10-28 14:41:05:653 1836 1438 AU ########### AU: Initializing Automatic
Updates ###########
2008-10-28 14:41:05:653 1836 1438 AU # WSUS server: http://BES01a
2008-10-28 14:41:05:653 1836 1438 AU # Detection frequency: 8
2008-10-28 14:41:05:653 1836 1438 AU # Target group: Workstations
2008-10-28 14:41:05:653 1836 1438 AU # Approval type: Scheduled (Policy)
2008-10-28 14:41:05:653 1836 1438 AU # Scheduled install day/time: Every
day at 3:00
2008-10-28 14:41:05:653 1836 1438 AU # Auto-install minor updates: Yes
(Policy)
2008-10-28 14:41:05:653 1836 1438 AU Setting AU scheduled install time to
2008-10-29 10:00:00
2008-10-28 14:41:05:919 1836 1438 Report *********** Report: Initializing
static reporting data ***********
2008-10-28 14:41:05:919 1836 1438 Report * OS Version = 5.1.2600.3.0.65792
2008-10-28 14:41:05:950 1836 1438 Report * Computer Brand = Dell Inc.

2008-10-28 14:41:05:950 1836 1438 Report * Computer Model = Precision
WorkStation 390
2008-10-28 14:41:05:950 1836 1438 Report * Bios Revision = 1.0.4
2008-10-28 14:41:05:950 1836 1438 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 1.0.4
2008-10-28 14:41:05:950 1836 1438 Report * Bios Release Date =
2006-08-16T00:00:00
2008-10-28 14:41:05:950 1836 1438 Report * Locale ID = 1033
2008-10-28 14:41:05:966 1836 1438 AU AU finished delayed initialization
2008-10-28 14:41:05:981 1836 1438 AU #############
2008-10-28 14:41:05:981 1836 1438 AU ## START ## AU: Search for updates
2008-10-28 14:41:05:981 1836 1438 AU #########
2008-10-28 14:41:05:981 1836 1438 AU <<## SUBMITTED ## AU: Search for
updates [CallId = {DC836BAF-70C4-467A-A68B-CB76E2D3C776}]
2008-10-28 14:41:06:856 1836 f84 PT WARNING: Cached cookie has expired or
new PID is available
2008-10-28 14:41:06:856 1836 f84 PT Initializing simple targeting cookie,
clientId = b6165484-51cb-4b09-a6f7-7255cab4029b, target group = Workstations,
DNS name = gge.gsamusic.com
2008-10-28 14:41:06:856 1836 f84 PT Server URL =
http://BES01a/SimpleAuthWebService/SimpleAuth.asmx
2008-10-28 14:41:06:903 1836 f84 Report Uploading 5 events using cached
cookie, reporting URL =
http://BES01a/ReportingWebService/ReportingWebService.asmx
2008-10-28 14:41:06:966 1836 f84 Report Reporter successfully uploaded 5
events.
2008-10-28 14:41:06:997 1836 f84 Report Uploading 2 events using cached
cookie, reporting URL =
http://BES01a/ReportingWebService/ReportingWebService.asmx
2008-10-28 14:41:06:997 1836 f84 Report Reporter successfully uploaded 2
events.
2008-10-28 14:41:07:028 1836 f84 Report Uploading 2 events using cached
cookie, reporting URL =
http://BES01a/ReportingWebService/ReportingWebService.asmx
2008-10-28 14:41:07:028 1836 f84 Report Reporter successfully uploaded 2
events.
2008-10-28 14:41:07:028 1836 f84 Agent *************
2008-10-28 14:41:07:028 1836 f84 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-28 14:41:07:028 1836 f84 Agent *********
2008-10-28 14:41:07:028 1836 f84 Agent * Online = No; Ignore download
priority = No
2008-10-28 14:41:07:028 1836 f84 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2008-10-28 14:41:07:028 1836 f84 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-10-28 14:41:58:325 1836 f84 Agent * Found 0 updates and 45 categories
in search; evaluated appl. rules of 680 out of 969 deployed entities
2008-10-28 14:41:58:356 1836 f84 Agent *********
2008-10-28 14:41:58:356 1836 f84 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-28 14:41:58:356 1836 f84 Agent *************
2008-10-28 14:41:58:356 1836 1058 AU >>## RESUMED ## AU: Search for
updates [CallId = {DC836BAF-70C4-467A-A68B-CB76E2D3C776}]
2008-10-28 14:41:58:356 1836 f84 Report REPORT EVENT:
{F4D5A999-8E05-4DDC-9AC9-E2008D68AC9F} 2008-10-28
14:41:05:653-0700 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
2008-10-28 14:41:58:356 1836 1058 AU # 0 updates detected
2008-10-28 14:41:58:356 1836 1058 AU #########
2008-10-28 14:41:58:356 1836 1058 AU ## END ## AU: Search for updates
[CallId = {DC836BAF-70C4-467A-A68B-CB76E2D3C776}]
2008-10-28 14:41:58:356 1836 1058 AU #############
2008-10-28 14:41:58:356 1836 1058 AU Setting AU scheduled install time to
2008-10-29 10:00:00
2008-10-28 14:42:51:778 1836 1084 AU Triggering AU detection through
DetectNow API
2008-10-28 14:42:51:778 1836 1084 AU Triggering Online detection
(non-interactive)
2008-10-28 14:42:51:778 1836 1438 AU #############
2008-10-28 14:42:51:778 1836 1438 AU ## START ## AU: Search for updates
2008-10-28 14:42:51:778 1836 1438 AU #########
2008-10-28 14:42:51:778 1836 1438 AU <<## SUBMITTED ## AU: Search for
updates [CallId = {D6B4BD36-EFFA-43E1-BA08-E5B6DBDBD638}]
2008-10-28 14:42:51:778 1836 f84 Agent *************
2008-10-28 14:42:51:778 1836 f84 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-28 14:42:51:778 1836 f84 Agent *********
2008-10-28 14:42:51:778 1836 f84 Agent * Online = Yes; Ignore download
priority = No
2008-10-28 14:42:51:778 1836 f84 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2008-10-28 14:42:51:778 1836 f84 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-10-28 14:42:51:778 1836 f84 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-10-28 14:42:51:778 1836 f84 Misc Microsoft signed: Yes
2008-10-28 14:42:51:794 1836 f84 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-10-28 14:42:51:794 1836 f84 Misc Microsoft signed: Yes
2008-10-28 14:42:51:809 1836 f84 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-10-28 14:42:51:809 1836 f84 Misc Microsoft signed: Yes
2008-10-28 14:42:51:825 1836 f84 Setup *********** Setup: Checking whether
self-update is required ***********
2008-10-28 14:42:51:825 1836 f84 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version =
7.1.6001.65
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:825 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:841 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:841 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2008-10-28 14:42:51:841 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-10-28 14:42:51:841 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-10-28 14:42:51:841 1836 f84 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2008-10-28 14:42:51:841 1836 f84 Setup * IsUpdateRequired = No
2008-10-28 14:42:53:497 1836 f84 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-10-28 14:42:53:497 1836 f84 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://BES01a/ClientWebService/client.asmx
2008-10-28 14:43:39:325 1836 f84 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2008-10-28 14:43:39:325 1836 f84 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://BES01a/ClientWebService/client.asmx
2008-10-28 14:43:42:138 1836 f84 Agent * Found 0 updates and 45 categories
in search; evaluated appl. rules of 680 out of 969 deployed entities
2008-10-28 14:43:42:169 1836 f84 Agent *********
2008-10-28 14:43:42:169 1836 f84 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-28 14:43:42:169 1836 f84 Agent *************
2008-10-28 14:43:42:169 1836 1058 AU >>## RESUMED ## AU: Search for
updates [CallId = {D6B4BD36-EFFA-43E1-BA08-E5B6DBDBD638}]
2008-10-28 14:43:42:169 1836 1058 AU # 0 updates detected
2008-10-28 14:43:42:169 1836 1058 AU #########
2008-10-28 14:43:42:169 1836 1058 AU ## END ## AU: Search for updates
[CallId = {D6B4BD36-EFFA-43E1-BA08-E5B6DBDBD638}]
2008-10-28 14:43:42:169 1836 1058 AU #############
2008-10-28 14:43:42:184 1836 1058 AU AU setting next detection timeout to
2008-10-29 05:05:54
2008-10-28 14:43:42:184 1836 1058 AU Setting AU scheduled install time to
2008-10-29 10:00:00
2008-10-28 14:43:47:169 1836 f84 Report REPORT EVENT:
{EC753C72-0ECF-4065-BD34-D4DF796325CE} 2008-10-28
14:43:42:169-0700 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2008-10-28 14:43:47:169 1836 f84 Report REPORT EVENT:
{6B2F4AE1-6C17-462C-822E-765358B5A9EE} 2008-10-28
14:43:42:169-0700 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.

--
glgcag
Re: Every client visible on WSUS 3.0 server, but no clients updating
"Lawrence Garvin \(MVP\)" <lawrence[ at ]nospam> 10/29/2008 2:36:30 AM
"glgcag" <glgcag[ at ]discussions.microsoft.com> wrote in message
news:9456542D-EE5F-49E5-B120-65AF55BCD374[ at ]microsoft.com...

[Quoted Text]
>I have spent hours looking for a solution to my problem to no avail. I hope
> someone here can help me!

> On the GPO I have the TargetGroup as "All Computers" though there is a
> Server and Workstations group that I assign each computer to respectively
> once it appears in WSUS. I'm wondering if the grouping is the problem?

Yes. Lose the "All Computers" assignment. "All Computers" is a reserved name
used to rollup the individual groups. By placing a machine explicity in the
"All Computers" group, you make it *NOT* in any other group, and thus
they'll get exactly the "0 updates detected" that you are experiencing.


But the logfile you posted does not appear to be a machine involved in the
above scenario....

> 2008-10-28 14:41:05:653 1836 1438 Agent * WSUS server: http://BES01a
> 2008-10-28 14:41:05:653 1836 1438 Agent * WSUS status server:
> http://BES01a
> 2008-10-28 14:41:05:653 1836 1438 Agent * Target group: Workstations

> 2008-10-28 14:41:06:856 1836 f84 PT Initializing simple targeting cookie,
> clientId = b6165484-51cb-4b09-a6f7-7255cab4029b, target group =
> Workstations,
> DNS name = gge.gsamusic.com

This machine is NOT in "All Computers"! This machine is assigned in
"Workstations".


> 2008-10-28 14:41:58:325 1836 f84 Agent * Found 0 updates and 45
> categories
> in search; evaluated appl. rules of 680 out of 969 deployed entities

This client performed a perfectly valid detection. The only logical
conclusion from this logfile is that there's nothing approved for
"Workstations" that is NEEDED by this client.

Specifically what update(s) do you feel should be detected by this client?

Specifically what update(s) are being reported as NEEDED by the
"Workstations" group, and is this particular machine (gge.gsamusic.com) one
of the machines listed with the update "Not Installed"?



--
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/profile/Lawrence.Garvin

Re: Every client visible on WSUS 3.0 server, but no clients updati
glgcag 10/29/2008 3:34:07 PM
Lawrence,

Thank you for your response. My WSUS admin console is showing this
workstation status as needing 20 updates, yet the log says 0 updates needed.
I can't seem to find a reason why the workstation won't see the needed
updates.
--
glgcag


"Lawrence Garvin (MVP)" wrote:

[Quoted Text]
> "glgcag" <glgcag[ at ]discussions.microsoft.com> wrote in message
> news:9456542D-EE5F-49E5-B120-65AF55BCD374[ at ]microsoft.com...
>
> >I have spent hours looking for a solution to my problem to no avail. I hope
> > someone here can help me!
>
> > On the GPO I have the TargetGroup as "All Computers" though there is a
> > Server and Workstations group that I assign each computer to respectively
> > once it appears in WSUS. I'm wondering if the grouping is the problem?
>
> Yes. Lose the "All Computers" assignment. "All Computers" is a reserved name
> used to rollup the individual groups. By placing a machine explicity in the
> "All Computers" group, you make it *NOT* in any other group, and thus
> they'll get exactly the "0 updates detected" that you are experiencing.
>
>
> But the logfile you posted does not appear to be a machine involved in the
> above scenario....
>
> > 2008-10-28 14:41:05:653 1836 1438 Agent * WSUS server: http://BES01a
> > 2008-10-28 14:41:05:653 1836 1438 Agent * WSUS status server:
> > http://BES01a
> > 2008-10-28 14:41:05:653 1836 1438 Agent * Target group: Workstations
>
> > 2008-10-28 14:41:06:856 1836 f84 PT Initializing simple targeting cookie,
> > clientId = b6165484-51cb-4b09-a6f7-7255cab4029b, target group =
> > Workstations,
> > DNS name = gge.gsamusic.com
>
> This machine is NOT in "All Computers"! This machine is assigned in
> "Workstations".
>
>
> > 2008-10-28 14:41:58:325 1836 f84 Agent * Found 0 updates and 45
> > categories
> > in search; evaluated appl. rules of 680 out of 969 deployed entities
>
> This client performed a perfectly valid detection. The only logical
> conclusion from this logfile is that there's nothing approved for
> "Workstations" that is NEEDED by this client.
>
> Specifically what update(s) do you feel should be detected by this client?
>
> Specifically what update(s) are being reported as NEEDED by the
> "Workstations" group, and is this particular machine (gge.gsamusic.com) one
> of the machines listed with the update "Not Installed"?
>
>
>
> --
> 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/profile/Lawrence.Garvin
>
>
Re: Every client visible on WSUS 3.0 server, but no clients updati
DaveMills <DaveMills[ at ]newsgroup.nospam> 10/29/2008 7:26:28 PM
On Wed, 29 Oct 2008 08:34:07 -0700, glgcag <glgcag[ at ]discussions.microsoft.com>
wrote:

[Quoted Text]
>Lawrence,
>
>Thank you for your response. My WSUS admin console is showing this
>workstation status as needing 20 updates, yet the log says 0 updates needed.
>I can't seem to find a reason why the workstation won't see the needed
>updates.

Are you sure it does not say "0 updates detected", this is not the same thing. A
needed update is one that the computer needs but a detected update if one that
is needed AND available to download.

If my guess is correct then either the updates are not approved for install
(check the group approvals) or they are not downloaded to the WSUS server (check
the status on the WSUS server).
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
Re: Every client visible on WSUS 3.0 server, but no clients updati
"Lawrence Garvin \(MVP\)" <lawrence[ at ]nospam> 10/29/2008 8:46:52 PM
"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message
news:oudhg4to8lonsf44bokaus3vg1k6diul4q[ at ]4ax.com...
[Quoted Text]
> On Wed, 29 Oct 2008 08:34:07 -0700, glgcag
> <glgcag[ at ]discussions.microsoft.com>
> wrote:
>
>>Lawrence,
>>
>>Thank you for your response. My WSUS admin console is showing this
>>workstation status as needing 20 updates, yet the log says 0 updates
>>needed.
>>I can't seem to find a reason why the workstation won't see the needed
>>updates.
>
> Are you sure it does not say "0 updates detected", this is not the same
> thing. A
> needed update is one that the computer needs but a detected update if one
> that
> is needed AND available to download.

Good catch, Dave! The log only records updated =detected=. The console makes
the distinction between (Needed / Not Applicable / Installed).

The scenario where the console shows updates as "Needed", but the log
records none as "Detected" is also possible, particularly in the case where
the client is unable to successfully sync/detect with the server. In that
instance, the server will report the data provided from the last successful
Reporting Event (which might well have noted the updates were Needed), but
the current scenarios is preventing the client from successfully executing
the detection -- which would result in a report of "0 updates detected".

--
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/profile/Lawrence.Garvin

Re: Every client visible on WSUS 3.0 server, but no clients updati
glgcag 11/5/2008 8:50:06 PM
OK, you guys nailed it!!!! I am still new to this software and I'm getting
successful synchronization reports for WSUS, but nowhere does it indicate
that though the syncs happened, the actual files were NOT downloaded!

I don't know why I can't get any of the actual update files to download! I
right click the update and hit retry download but it never works. Any
suggestions?

glgcag


"Lawrence Garvin (MVP)" wrote:

[Quoted Text]
> "DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message
> news:oudhg4to8lonsf44bokaus3vg1k6diul4q[ at ]4ax.com...
> > On Wed, 29 Oct 2008 08:34:07 -0700, glgcag
> > <glgcag[ at ]discussions.microsoft.com>
> > wrote:
> >
> >>Lawrence,
> >>
> >>Thank you for your response. My WSUS admin console is showing this
> >>workstation status as needing 20 updates, yet the log says 0 updates
> >>needed.
> >>I can't seem to find a reason why the workstation won't see the needed
> >>updates.
> >
> > Are you sure it does not say "0 updates detected", this is not the same
> > thing. A
> > needed update is one that the computer needs but a detected update if one
> > that
> > is needed AND available to download.
>
> Good catch, Dave! The log only records updated =detected=. The console makes
> the distinction between (Needed / Not Applicable / Installed).
>
> The scenario where the console shows updates as "Needed", but the log
> records none as "Detected" is also possible, particularly in the case where
> the client is unable to successfully sync/detect with the server. In that
> instance, the server will report the data provided from the last successful
> Reporting Event (which might well have noted the updates were Needed), but
> the current scenarios is preventing the client from successfully executing
> the detection -- which would result in a report of "0 updates detected".
>
> --
> 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/profile/Lawrence.Garvin
>
>
Re: Every client visible on WSUS 3.0 server, but no clients updati
glgcag 11/5/2008 9:06:03 PM
OK, so now that I have a better idea of what is going on, the application
event viewer had an error 364 for wsus, which is the following:

Event 364 Source: Windows Server Update Category: Synchronization

Content file download failed. Reason: The server does not support the
necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
requires that the server support the Range protocol header.
Source File:
/msdownload/update/v3-19990518/cabpool/visio2002-kb917150-fullfile-glb_c086ab10bda5e695d8ea26d91a690e225fc239d6.cab
Destination File:
d:\WSUS\WsusContent\D6\C086AB10BDA5E695D8EA26D91A690E225FC239D6.CAB.

This was suggested on a forum:

<beginquote>KB 922330 says the problem is because the affected computer is
behind a firewall or proxy. They specifically mention Sonicwall security
appliances as a culprit and suggest selecting the Enable HTTP Byte-Range
request with Gateway AV check box on the Sonicwall configuration. This
particular WSUS client does sit behind a Sonicwall 3060 security appliance.
I went into the Sonicwall administation page, but could not find where to
enable this feature. Luckily I came across this post, where J.B. pointed out
where to find the setting:

“Instructions for Sonic Enhanced OS:
Click Security Services, Gateway Anti-Virus, Configure Gateway AV Settings.
Check the box for “Enable HTTP Byte-Range requests with Gateway AV”.

I made the change to the Sonicwall, then ran wuauclt /detectnow on the WSUS
server/client. We’ll see if the Event 364 reappears. </endquote>

Since I'm behind a Sonicwall I tried the solution and it actually works! I'm
retrying downloads and they are working now! Thanks for the help and I hope
this post helps someone else!
--
glgcag


"Lawrence Garvin (MVP)" wrote:

[Quoted Text]
> "DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message
> news:oudhg4to8lonsf44bokaus3vg1k6diul4q[ at ]4ax.com...
> > On Wed, 29 Oct 2008 08:34:07 -0700, glgcag
> > <glgcag[ at ]discussions.microsoft.com>
> > wrote:
> >
> >>Lawrence,
> >>
> >>Thank you for your response. My WSUS admin console is showing this
> >>workstation status as needing 20 updates, yet the log says 0 updates
> >>needed.
> >>I can't seem to find a reason why the workstation won't see the needed
> >>updates.
> >
> > Are you sure it does not say "0 updates detected", this is not the same
> > thing. A
> > needed update is one that the computer needs but a detected update if one
> > that
> > is needed AND available to download.
>
> Good catch, Dave! The log only records updated =detected=. The console makes
> the distinction between (Needed / Not Applicable / Installed).
>
> The scenario where the console shows updates as "Needed", but the log
> records none as "Detected" is also possible, particularly in the case where
> the client is unable to successfully sync/detect with the server. In that
> instance, the server will report the data provided from the last successful
> Reporting Event (which might well have noted the updates were Needed), but
> the current scenarios is preventing the client from successfully executing
> the detection -- which would result in a report of "0 updates detected".
>
> --
> 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/profile/Lawrence.Garvin
>
>

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen