Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Server Update Service
Clients Seem to be Reporting but Not Updating Clients Seem to be Reporting but Not Updating
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read SiteMap

Tags: , ,

Sponsored Links



Clients Seem to be Reporting but Not Updating

Server Update Service


Reply
 
Thread Tools Search this Thread
  #1  
Old 12-06-2008
Member
  
Join Date: May 2008
Posts: 16
Clients Seem to be Reporting but Not Updating
The console shows certain machines need certain updates, but the machine is not showing it needs any updates?
What am I missing?
Reply With Quote
  #2  
Old 12-06-2008
Lawrence Garvin
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
"dkon" <dkon.3aurzd@DoNotSpam.com> wrote in message
news:dkon.3aurzd@DoNotSpam.com...
>
> The console shows certain machines need certain updates, but the machine
> is not showing it needs any updates?
> What am I missing?

What *we* are missing is information concerning the *actual* state of the
machine as obtained from the WindowsUpdate.log.

--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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
  #3  
Old 12-06-2008
Member
  
Join Date: May 2008
Posts: 16
sorry about that . . . the following is for all of yesterday . . .
The console reports 0 updates w/errors; 5 updates needed


2008-06-11 01:59:30:189 972 978 AU #############
2008-06-11 01:59:30:189 972 978 AU ## START ## AU: Search for updates
2008-06-11 01:59:30:189 972 978 AU #########
2008-06-11 01:59:30:189 972 978 AU <<## SUBMITTED ## AU: Search for updates [CallId = {72B3CFE2-DDD8-44C3-A9AD-CDE6CC000300}]
2008-06-11 01:59:30:189 972 a24 Agent *************
2008-06-11 01:59:30:189 972 a24 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-06-11 01:59:30:189 972 a24 Agent *********
2008-06-11 01:59:30:189 972 a24 Agent * Online = Yes; Ignore download priority = No
2008-06-11 01:59:30:189 972 a24 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-06-11 01:59:30:189 972 a24 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-11 01:59:30:189 972 a24 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-11 01:59:30:657 972 a24 Misc Microsoft signed: Yes
2008-06-11 01:59:46:688 972 a24 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-11 01:59:46:688 972 a24 Misc Microsoft signed: Yes
2008-06-11 01:59:46:704 972 a24 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-06-11 01:59:46:720 972 a24 Misc Microsoft signed: Yes
2008-06-11 01:59:46:720 972 a24 Setup *********** Setup: Checking whether self-update is required ***********
2008-06-11 01:59:46:720 972 a24 Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-06-11 01:59:46:735 972 a24 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:751 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:767 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:782 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:798 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:798 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:813 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:829 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:845 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:845 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:860 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:876 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:892 972 a24 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 01:59:46:892 972 a24 Setup * IsUpdateRequired = No
2008-06-11 01:59:48:032 972 a24 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2008-06-11 01:59:48:032 972 a24 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://aquilo:8530/ClientWebService/client.asmx
2008-06-11 01:59:48:407 972 a24 PT WARNING: Cached cookie has expired or new PID is available
2008-06-11 01:59:48:407 972 a24 PT Initializing simple targeting cookie, clientId = 23ad8a1b-2891-4880-96ef-837e028cd7c5, target group = , DNS name = gcq-marq-odd.ad.medctr.ucla.edu
2008-06-11 01:59:48:407 972 a24 PT Server URL = http://aquilo:8530/SimpleAuthWebService/SimpleAuth.asmx
2008-06-11 01:59:50:876 972 a24 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2008-06-11 01:59:50:876 972 a24 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://aquilo:8530/ClientWebService/client.asmx
2008-06-11 01:59:51:376 972 a24 Agent * Found 0 updates and 36 categories in search; evaluated appl. rules of 277 out of 363 deployed entities
2008-06-11 01:59:51:391 972 a24 Agent *********
2008-06-11 01:59:51:391 972 a24 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-06-11 01:59:51:391 972 a24 Agent *************
2008-06-11 01:59:51:391 972 548 AU >>## RESUMED ## AU: Search for updates [CallId = {72B3CFE2-DDD8-44C3-A9AD-CDE6CC000300}]
2008-06-11 01:59:51:391 972 548 AU # 0 updates detected
2008-06-11 01:59:51:391 972 548 AU #########
2008-06-11 01:59:51:391 972 548 AU ## END ## AU: Search for updates [CallId = {72B3CFE2-DDD8-44C3-A9AD-CDE6CC000300}]
2008-06-11 01:59:51:391 972 548 AU #############
2008-06-11 01:59:51:391 972 548 AU AU setting next detection timeout to 2008-06-12 02:43:30
2008-06-11 01:59:56:391 972 a24 Report REPORT EVENT: {F9578F06-65F2-474E-947A-5CB432CEE2FA} 2008-06-11 01:59:51:391-0700 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
2008-06-11 01:59:56:391 972 a24 Report REPORT EVENT: {C34B5DAF-9667-425F-A641-F483EBEDE6BD} 2008-06-11 01:59:51:391-0700 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2008-06-11 02:00:56:500 972 a24 Report Uploading 2 events using cached cookie, reporting URL = http://aquilo:8530/ReportingWebServi...ebService.asmx
2008-06-11 02:00:56:500 972 a24 Report Reporter successfully uploaded 2 events.
2008-06-11 14:24:36:523 972 790 AU AU found 0 updates for install at shutdown
2008-06-11 14:24:36:555 3956 570 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0700) ===========
2008-06-11 14:24:36:555 3956 570 Misc = Process: C:\WINDOWS\Explorer.EXE
2008-06-11 14:24:36:555 3956 570 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2008-06-11 14:24:36:555 3956 570 Shutdwn Install at shutdown: no updates to install
2008-06-11 14:24:49:742 972 978 AU ########### AU: Uninitializing Automatic Updates ###########
2008-06-11 14:24:50:476 972 978 Service *********
2008-06-11 14:24:50:476 972 978 Service ** END ** Service: Service exit [Exit code = 0x240001]
2008-06-11 14:24:50:476 972 978 Service *************
2008-06-11 14:27:32:484 968 8e8 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0700) ===========
2008-06-11 14:27:32:484 968 8e8 Misc = Process: C:\WINDOWS\System32\svchost.exe
2008-06-11 14:27:32:484 968 8e8 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2008-06-11 14:27:32:484 968 8e8 Service *************
2008-06-11 14:27:32:484 968 8e8 Service ** START ** Service: Service startup
2008-06-11 14:27:32:484 968 8e8 Service *********
2008-06-11 14:27:32:609 968 8e8 Agent * WU client version 7.1.6001.65
2008-06-11 14:27:32:609 968 8e8 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2008-06-11 14:27:32:625 968 8e8 Agent * Access type: No proxy
2008-06-11 14:27:32:625 968 8e8 Agent * Network state: Connected
2008-06-11 14:28:17:689 968 8e8 Agent *********** Agent: Initializing Windows Update Agent ***********
2008-06-11 14:28:17:689 968 8e8 Agent *********** Agent: Initializing global settings cache ***********
2008-06-11 14:28:17:689 968 8e8 Agent * WSUS server: http://aquilo:8530
2008-06-11 14:28:17:689 968 8e8 Agent * WSUS status server: http://aquilo:8530
2008-06-11 14:28:17:689 968 8e8 Agent * Target group: (Unassigned Computers)
2008-06-11 14:28:17:689 968 8e8 Agent * Windows Update access disabled: No
2008-06-11 14:28:18:000 968 8e8 DnldMgr Download manager restoring 0 downloads
2008-06-11 14:28:18:000 968 8e8 AU ########### AU: Initializing Automatic Updates ###########
2008-06-11 14:28:18:000 968 8e8 AU # WSUS server: http://aquilo:8530
2008-06-11 14:28:18:000 968 8e8 AU # Detection frequency: 22
2008-06-11 14:28:18:000 968 8e8 AU # Approval type: Pre-install notify (Policy)
2008-06-11 14:28:18:000 968 8e8 AU # Auto-install minor updates: Yes (Policy)
2008-06-11 14:28:18:000 968 8e8 AU # Will interact with non-admins (Non-admins are elevated)
2008-06-11 14:28:18:000 968 8e8 AU AU finished delayed initialization
2008-06-11 14:28:18:119 968 8e8 Report *********** Report: Initializing static reporting data ***********
2008-06-11 14:28:18:119 968 8e8 Report * OS Version = 5.2.3790.2.0.196880
2008-06-11 14:28:18:193 968 8e8 Report * Computer Brand = Dell Computer Corporation
2008-06-11 14:28:18:193 968 8e8 Report * Computer Model = PowerEdge 1850
2008-06-11 14:28:18:193 968 8e8 Report * Bios Revision = A04
2008-06-11 14:28:18:193 968 8e8 Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A04
2008-06-11 14:28:18:193 968 8e8 Report * Bios Release Date = 2005-09-22T00:00:00
2008-06-11 14:28:18:193 968 8e8 Report * Locale ID = 1033
2008-06-11 19:43:29:886 968 8e8 AU #############
2008-06-11 19:43:29:886 968 8e8 AU ## START ## AU: Search for updates
2008-06-11 19:43:29:886 968 8e8 AU #########
2008-06-11 19:43:29:886 968 8e8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {88F9D4A1-8BFB-4AC9-ABB6-254C1A8891E9}]
2008-06-11 19:43:29:886 968 268 Agent *************
2008-06-11 19:43:29:886 968 268 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-06-11 19:43:29:886 968 268 Agent *********
2008-06-11 19:43:29:886 968 268 Agent * Online = Yes; Ignore download priority = No
2008-06-11 19:43:29:886 968 268 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-06-11 19:43:29:886 968 268 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-06-11 19:43:29:902 968 268 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-11 19:43:29:949 968 268 Misc Microsoft signed: Yes
2008-06-11 19:43:45:996 968 268 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-06-11 19:43:45:996 968 268 Misc Microsoft signed: Yes
2008-06-11 19:43:46:074 968 268 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2008-06-11 19:43:46:074 968 268 Misc Microsoft signed: Yes
2008-06-11 19:43:46:105 968 268 Setup *********** Setup: Checking whether self-update is required ***********
2008-06-11 19:43:46:105 968 268 Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2008-06-11 19:43:46:121 968 268 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:121 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:136 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:136 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:136 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:152 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:152 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:167 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:167 968 268 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:183 968 268 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:183 968 268 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:199 968 268 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:246 968 268 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2008-06-11 19:43:46:246 968 268 Setup * IsUpdateRequired = No
2008-06-11 19:43:47:308 968 268 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2008-06-11 19:43:47:308 968 268 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://aquilo:8530/ClientWebService/client.asmx
2008-06-11 19:43:47:574 968 268 PT WARNING: Cached cookie has expired or new PID is available
2008-06-11 19:43:47:574 968 268 PT Initializing simple targeting cookie, clientId = 23ad8a1b-2891-4880-96ef-837e028cd7c5, target group = , DNS name = gcq-marq-odd.ad.medctr.ucla.edu
2008-06-11 19:43:47:574 968 268 PT Server URL = http://aquilo:8530/SimpleAuthWebService/SimpleAuth.asmx
2008-06-11 19:43:54:652 968 268 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2008-06-11 19:43:54:652 968 268 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://aquilo:8530/ClientWebService/client.asmx
2008-06-11 19:43:55:011 968 268 Agent * Found 0 updates and 36 categories in search; evaluated appl. rules of 277 out of 363 deployed entities
2008-06-11 19:43:55:027 968 268 Agent *********
2008-06-11 19:43:55:027 968 268 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-06-11 19:43:55:027 968 268 Agent *************
2008-06-11 19:43:55:027 968 8c8 AU >>## RESUMED ## AU: Search for updates [CallId = {88F9D4A1-8BFB-4AC9-ABB6-254C1A8891E9}]
2008-06-11 19:43:55:027 968 8c8 AU # 0 updates detected
2008-06-11 19:43:55:027 968 8c8 AU #########
2008-06-11 19:43:55:027 968 8c8 AU ## END ## AU: Search for updates [CallId = {88F9D4A1-8BFB-4AC9-ABB6-254C1A8891E9}]
2008-06-11 19:43:55:027 968 8c8 AU #############
2008-06-11 19:43:55:027 968 8c8 AU AU setting next detection timeout to 2008-06-12 20:40:46
2008-06-11 19:44:00:011 968 268 Report REPORT EVENT: {8E7CA083-A76C-4055-A627-2B936A29B082} 2008-06-11 19:43:55:011-0700 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
2008-06-11 19:44:00:011 968 268 Report REPORT EVENT: {ABDD669F-A75F-4D07-8D42-E3C3E35E7497} 2008-06-11 19:43:55:011-0700 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2008-06-11 19:55:11:460 968 268 Report Uploading 2 events using cached cookie, reporting URL = http://aquilo:8530/ReportingWebServi...ebService.asmx
2008-06-11 19:55:12:148 968 268 Report Reporter successfully uploaded 2 events.
Reply With Quote
  #4  
Old 13-06-2008
Lawrence Garvin
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
"dkon" <dkon.3awh3f@DoNotSpam.com> wrote in message
news:dkon.3awh3f@DoNotSpam.com...
>
> sorry about that . . . the following is for all of yesterday . . .

The single most common cause...

> 2008-06-11 01:59:48:407 972 a24 PT Initializing simple targeting cookie,
> clientId = 23ad8a1b-2891-4880-96ef-837e028cd7c5,
> target group = ,
> DNS name = gcq-marq-odd.ad.medctr.ucla.edu

The client has no target group information.

Either the target group settings are misconfigured, the policy is not being
applied correctly, or the client is not expiring a cached targeting cookie.

Verify the configuration is correct, and then run the command:
wuauclt /resetauthorization /detectnow

> 2008-06-11 19:43:47:574 968 268 PT WARNING: Cached cookie has expired
> or new PID is available

And, since the WUA is routinely logging that the cookie has expired,
that kind of leaves us with an incorrect target group configuration.


--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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
  #5  
Old 21-06-2008
Member
  
Join Date: May 2008
Posts: 16
my clients are configured locally and the "enable client-side targeting" setting is unconfigured.
They show in the console initially in the "unassigned computers" group, then I move them to groups I have created . . .
What am I doing wrong?
Reply With Quote
  #6  
Old 21-06-2008
Wade Godfrey
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
Have you verified that you have approved the updates for install to the
group(s) that your machines reside in?

From the looks of your original logs, no updates were found to be
installed. If you don't approve the updates for install to your
configured groups, they won't show as available to install on the clients.

dkon wrote:
> my clients are configured locally and the "enable client-side targeting"
> setting is unconfigured.
> They show in the console initially in the "unassigned computers" group,
> then I move them to groups I have created . . .
> What am I doing wrong?
>
>
Reply With Quote
  #7  
Old 21-06-2008
Member
  
Join Date: May 2008
Posts: 16
yes they are approved.
Reply With Quote
  #8  
Old 21-06-2008
Lawrence Garvin
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
"dkon" <dkon.3bblja@DoNotSpam.com> wrote in message
news:dkon.3bblja@DoNotSpam.com...
>
> my clients are configured locally and the "enable client-side targeting"
> setting is unconfigured.

> They show in the console initially in the "unassigned computers" group,
> then I move them to groups I have created . . .

> What am I doing wrong?

Nothing. The system is working as designed.

What behavior did you expect???

--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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
  #9  
Old 21-06-2008
Member
  
Join Date: May 2008
Posts: 16
I guess I'm confused as the console says updates are needed but the clients are not seeming to load them over the last week?

You mentioned below:
"From the looks of your original logs, no updates were found to be
installed. If you don't approve the updates for install to your
configured groups, they won't show as available to install on the clients."

since the updates are approved, shouldn't they load?


You also mentioned below:
"The client has no target group information.
Either the target group settings are misconfigured, the policy is not being
applied correctly, or the client is not expiring a cached targeting cookie."

Is this still a possible issue?
Reply With Quote
  #10  
Old 22-06-2008
Lawrence Garvin
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
"dkon" <dkon.3bd7ve@DoNotSpam.com> wrote in message
news:dkon.3bd7ve@DoNotSpam.com...
>
> I guess I'm confused as the console says updates are needed but the
> clients are not seeming to load them over the last week?
>
> You mentioned below:
> "From the looks of your original logs, no updates were found to be
> installed. If you don't approve the updates for install to your
> configured groups, they won't show as available to install on the
> clients."
>
> since the updates are approved, shouldn't they load?

ONLY if they're approved for the GROUP that the client thinks it belongs to.

> You also mentioned below:
> "The client has no target group information.

Which is the core problem. If you've not approve the update for "Unassigned
Computers", then the client doesn't have an approval. When the client has no
target group information, it only checks "Unassigned Computers".

> Either the target group settings are misconfigured, the policy is not
> being
> applied correctly, or the client is not expiring a cached targeting
> cookie."
>
> Is this still a possible issue?

Until you fix it. :-)

--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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
  #11  
Old 22-06-2008
Member
  
Join Date: May 2008
Posts: 16
so even if I moved them to different groups, since I never originally assigned the to a group other then "unassigned" the only way they will update is if I approve to to the "unassigned" group rather then the current group they are in???
Reply With Quote
  #12  
Old 22-06-2008
Lawrence Garvin
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
"dkon" <dkon.3bdrbb@DoNotSpam.com> wrote in message
news:dkon.3bdrbb@DoNotSpam.com...
>
> so even if I moved them to different groups, since I never originally
> assigned the to a group other then "unassigned" the only way they will
> update is if I approve to to the "unassigned" group rather then the
> current group they are in???

No.. that's not what I'm saying.

What I'm saying is that whatever method you're trying to use to inform the
client what group they belong to -- it ain't working.

If you're using Group Policy and client-side targeting, then you need to
check the policy configuration and status.

If you're using server-side targeting, then the client isn't getting those
server-side group changes. If this is the case, run 'wuauclt
/resetauthorization /detectnow' on the client, to force the targeting
information to be discarded and refreshed from the server.

If you're using server-side targeting, but the client thinks you're using
client-side targeting, then you need to fix that policy configuration,
before any of this will work.


As for "never originally assigned them...", if you're using server-side
targeting, ALL computers are first placed in "Unassigned Computers" and you
/must/ reassign them to a new group -- or else approve updates for "All
Computers" or "Unassigned Computers".



--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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
  #13  
Old 28-06-2008
Member
  
Join Date: May 2008
Posts: 16
OK
1) I deleted the client from the console, and under options changed to client-side targeting
2) I went to the local policy of the client, enabled client-side targeting and specified the desired existing group
3) ran 'wuauclt /resetauthorization /detectnow' on the client and it populated the desired group
4) verified I had approved a "bunch" of updates

The console shows the client status in the console shows:
0 updates with errors
116 updates needed
1474 updates installed/not applicable
0 updates with now status
. . . but the server does not seem to be pulling those 116 needed updates . . .

again I must ask, what am i doing wrong?
Reply With Quote
  #14  
Old 28-06-2008
TimParker
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
I had just posted a message with the same type of problem (apparently
my searching didn't turn this up till after the fact, go figure!)

I just found what I believe to be my problem. I also had a machine
that was reporting, but not getting updates after it had been rebuilt.
It is in a working group that has all of our agency workstations and
the rest are working just fine.

Something in a post above made me go check something of my previously
installed and applied patches. The previous MIS Guy, that I replaced
had set a deadline on the patches to be installed by a certain date
(we are currently still running WSUS 2.0 right now as an FYI). The
first two patches that I thought should have been installed on this
machine were from 2007. So I think if I go back and remove these
deadlines, they will install just fine! Deadlines seem to be nice, as
long as you never need to rebuild or put a machine back into that
group that might need it.

Hope this helps.

Tim

On Jun 27, 6:33*pm, dkon <dkon.3bo...@DoNotSpam.com> wrote:
> OK
> 1) I deleted the client from the console, and under options changed to
> client-side targeting
> 2) I went to the local policy of the client, enabled client-side
> targeting and specified the desired existing group
> 3) ran 'wuauclt /resetauthorization /detectnow' on the client and it
> populated the desired group
> 4) verified I had approved a "bunch" of updates
>
> The console shows the client status in the console shows:
> 0 updates with errors
> 116 updates needed
> 1474 updates installed/not applicable
> 0 updates with now status
> . . . but the server does not seem to be pulling those 116 needed
> updates . . .
>
> again I must ask, what am i doing wrong?
>
> --
> dkon
> ------------------------------------------------------------------------
> dkon's Profile:http://forums.techarena.in/members/50723.htm
> View this thread:Clients Seem to be Reporting but Not Updating
>
> http://forums.techarena.in

Reply With Quote
  #15  
Old 30-06-2008
Lawrence Garvin
 
Posts: n/a
Re: Clients Seem to be Reporting but Not Updating
"dkon" <dkon.3bosjf@DoNotSpam.com> wrote in message
news:dkon.3bosjf@DoNotSpam.com...
>
> OK
> 1) I deleted the client from the console, and under options changed to
> client-side targeting
> 2) I went to the local policy of the client, enabled client-side
> targeting and specified the desired existing group
> 3) ran 'wuauclt /resetauthorization /detectnow' on the client and it
> populated the desired group
> 4) verified I had approved a "bunch" of updates
>
> The console shows the client status in the console shows:
> 0 updates with errors
> 116 updates needed
> 1474 updates installed/not applicable
> 0 updates with now status
> . . but the server does not seem to be pulling those 116 needed
> updates . . .

> again I must ask, what am i doing wrong?

NOTHING.

> 116 updates needed

The client identified needed updates.

Now you need to inspect the =LOGFILE= again. Surely you weren't expecting
116 updates to instantaneously become installed? It'll probably take some
time for those 116 updates to download to the client system, and then they
need to be =installed=, then the server needs to be restarted, and =then=
the updates will display on the WSUS Console as "Installed".

--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Server Update Service

« XP SP3 installed via WSUS does not show as installed    Manually Remove WSUS 3 »

Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Clients Seem to be Reporting but Not Updating"
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
WSUS 3.0 SP1: Vista Clients not reporting Terry Windows Update 3 19-11-2008 11:29 PM
WSUS upgrade from 2.0 - 3.0 and now only some clients reporting crazdt Server Update Service 21 16-08-2008 02:55 AM
Some Clients not reporting back or detecting updates Martin Searle Server Update Service 9 21-06-2008 07:10 PM
clients not reporting status after updating WSUS 2 to WSUS 3.0 Veronika Server Update Service 5 17-07-2007 10:37 PM


All times are GMT +5.5. The time now is 03:40 AM.

Contact Us - TechArena - Privacy Statement -