Discussion:
WSUS 3.0 SP2 not yet reported
(too old to reply)
Rick
2010-06-02 13:21:01 UTC
Permalink
Raw Message
I have read probably 30 posts about this issue and just cant find the answer
for my problem. I have abou 450 computer / servers that are not reporting
any information. I ran the client diag tool and everything passed. I think
my self update directory is setup correctly as I can browse to all documents.
Also in my window update log file, I am seeing " Self Update check
completed. Self Update is NOT required". What do u need from me as I need
to start getting some information about our systems.

Thanks- Rick
Lawrence Garvin [MVP]
2010-06-02 13:34:37 UTC
Permalink
Raw Message
Post by Rick
I have read probably 30 posts about this issue and just cant find the answer
for my problem. I have abou 450 computer / servers that are not reporting
any information. I ran the client diag tool and everything passed. I think
my self update directory is setup correctly as I can browse to all documents.
Also in my window update log file, I am seeing " Self Update check
completed. Self Update is NOT required". What do u need from me as I need
to start getting some information about our systems.
The actual output of the Client Diagnostic Tool. The tool does not always
accurately identify issues.

The results from this procedure:

1. Pick a machine that is not reporting.
2. Record the system time.
3. Restart the Automatic Updates service. (net stop wuauserv; net start
wuauserv).
4. Run this command: wuauclt /resetauthorization /detectnow
5. Wait 30 minutes.
6. Post all of the entries from the WindowsUpdate.log starting at the time
recorded in Step #2.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Rick
2010-06-02 14:29:01 UTC
Permalink
Raw Message
2010-06-02 09:57:04:366 940 89c AU ########### AU: Uninitializing Automatic
Updates ###########
2010-06-02 09:57:07:736 940 89c Report CWERReporter finishing event
handling. (00000000)
2010-06-02 09:57:07:923 940 89c Service *********
2010-06-02 09:57:07:923 940 89c Service ** END ** Service: Service exit
[Exit code = 0x240001]
2010-06-02 09:57:07:923 940 89c Service *************
2010-06-02 09:57:08:251 940 f20 Misc =========== Logging initialized
(build: 7.4.7600.226, tz: -0400) ===========
2010-06-02 09:57:08:251 940 f20 Misc = Process:
C:\Windows\system32\svchost.exe
2010-06-02 09:57:08:251 940 f20 Misc = Module:
c:\windows\system32\wuaueng.dll
2010-06-02 09:57:08:251 940 f20 Service *************
2010-06-02 09:57:08:251 940 f20 Service ** START ** Service: Service startup
2010-06-02 09:57:08:251 940 f20 Service *********
2010-06-02 09:57:08:251 940 f20 Agent * WU client version 7.4.7600.226
2010-06-02 09:57:08:251 940 f20 Agent * Base directory:
C:\Windows\SoftwareDistribution
2010-06-02 09:57:08:251 940 f20 Agent * Access type: No proxy
2010-06-02 09:57:08:329 940 f20 Agent * Network state: Connected
2010-06-02 09:57:23:414 940 ed8 Report CWERReporter::Init succeeded
2010-06-02 09:57:23:414 940 ed8 Agent *********** Agent: Initializing
Windows Update Agent ***********
2010-06-02 09:57:23:414 940 ed8 Agent *********** Agent: Initializing
global settings cache ***********
2010-06-02 09:57:23:414 940 ed8 Agent * WSUS server:
http://servername.fqdn:80/
2010-06-02 09:57:23:414 940 ed8 Agent * WSUS status server:
http://servername.fqdn:80/
2010-06-02 09:57:23:414 940 ed8 Agent * Target group: (Unassigned
Computers)
2010-06-02 09:57:23:414 940 ed8 Agent * Windows Update access disabled: No
2010-06-02 09:57:23:523 940 ed8 DnldMgr Download manager restoring 0
downloads
2010-06-02 09:57:23:601 940 ed8 AU ########### AU: Initializing Automatic
Updates ###########
2010-06-02 09:57:23:601 940 ed8 AU # WSUS server:
http://servername.fqdn:80/
2010-06-02 09:57:23:601 940 ed8 AU # Detection frequency: 22
2010-06-02 09:57:23:601 940 ed8 AU # Approval type: Scheduled (User
preference)
2010-06-02 09:57:23:601 940 ed8 AU # Scheduled install day/time: Every
day at 3:00
2010-06-02 09:57:23:601 940 ed8 AU # Auto-install minor updates: Yes
(User preference)
2010-06-02 09:57:23:601 940 ed8 AU # Will interact with non-admins
(Non-admins are elevated (User preference))
2010-06-02 09:57:23:601 940 ed8 AU Setting AU scheduled install time to
2010-06-03 07:00:00
2010-06-02 09:57:24:584 940 f20 Report *********** Report: Initializing
static reporting data ***********
2010-06-02 09:57:24:584 940 f20 Report * OS Version = 6.1.7600.0.0.65792
2010-06-02 09:57:24:584 940 f20 Report * OS Product Type = 0x00000030
2010-06-02 09:57:24:615 940 f20 Report * Computer Brand = Dell Inc.

2010-06-02 09:57:24:615 940 f20 Report * Computer Model = OptiPlex 745

2010-06-02 09:57:24:615 940 f20 Report * Bios Revision = 2.3.1
2010-06-02 09:57:24:615 940 f20 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 2.3.1
2010-06-02 09:57:24:615 940 f20 Report * Bios Release Date =
2007-05-21T00:00:00
2010-06-02 09:57:24:615 940 f20 Report * Locale ID = 1033
2010-06-02 09:57:24:646 940 ed8 AU Successfully wrote event for AU health
state:0
2010-06-02 09:57:24:646 940 ed8 AU Initializing featured updates
2010-06-02 09:57:24:646 940 ed8 AU Found 0 cached featured updates
2010-06-02 09:57:24:646 940 ed8 AU Successfully wrote event for AU health
state:0
2010-06-02 09:57:24:646 940 ed8 AU Successfully wrote event for AU health
state:0
2010-06-02 09:57:24:646 940 ed8 AU AU finished delayed initialization
2010-06-02 09:57:24:646 940 ed8 AU Triggering AU detection through
DetectNow API
2010-06-02 09:57:24:646 940 ed8 AU Triggering Online detection
(non-interactive)
2010-06-02 09:57:24:646 940 f20 AU #############
2010-06-02 09:57:24:646 940 f20 AU ## START ## AU: Search for updates
2010-06-02 09:57:24:646 940 f20 AU #########
2010-06-02 09:57:24:911 940 f20 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {CC3DB630-B953-444D-86D2-ACCBCEB00FAF}]
2010-06-02 09:57:25:083 940 4c8 Agent *************
2010-06-02 09:57:25:083 940 4c8 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2010-06-02 09:57:25:083 940 4c8 Agent *********
2010-06-02 09:57:25:083 940 4c8 Agent * Online = Yes; Ignore download
priority = No
2010-06-02 09:57:25:083 940 4c8 Agent * 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"
2010-06-02 09:57:25:083 940 4c8 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-06-02 09:57:25:083 940 4c8 Agent * Search Scope = {Machine}
2010-06-02 09:57:25:083 940 4c8 Setup Checking for agent SelfUpdate
2010-06-02 09:57:25:083 940 4c8 Setup Client version: Core: 7.4.7600.226
Aux: 7.4.7600.226
2010-06-02 09:57:25:098 940 4c8 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-06-02 09:57:25:098 940 4c8 Misc Microsoft signed: Yes
2010-06-02 09:57:27:516 940 4c8 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-06-02 09:57:27:563 940 4c8 Misc Microsoft signed: Yes
2010-06-02 09:57:27:610 940 4c8 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-06-02 09:57:27:625 940 4c8 Misc Microsoft signed: Yes
2010-06-02 09:57:27:641 940 4c8 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-06-02 09:57:27:657 940 4c8 Misc Microsoft signed: Yes
2010-06-02 09:57:27:703 940 4c8 Setup Determining whether a new setup
handler needs to be downloaded
2010-06-02 09:57:27:703 940 4c8 Misc Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2010-06-02 09:57:27:719 940 4c8 Misc Microsoft signed: Yes
2010-06-02 09:57:27:719 940 4c8 Setup SelfUpdate handler update NOT
required: Current version: 7.4.7600.226, required version: 7.4.7600.226
2010-06-02 09:57:27:719 940 4c8 Setup Evaluating applicability of setup
package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-06-02 09:57:27:719 940 4c8 Setup Setup package
"WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" is already
installed.
2010-06-02 09:57:27:719 940 4c8 Setup Evaluating applicability of setup
package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226"
2010-06-02 09:57:27:750 940 4c8 Setup Setup package
"WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226" is
already installed.
2010-06-02 09:57:27:750 940 4c8 Setup Evaluating applicability of setup
package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226"
2010-06-02 09:57:27:797 940 4c8 Setup Setup package
"WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226" is
already installed.
2010-06-02 09:57:27:797 940 4c8 Setup SelfUpdate check completed.
SelfUpdate is NOT required.
2010-06-02 09:57:28:405 940 4c8 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2010-06-02 09:57:28:405 940 4c8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://servername.fqdn:80/ClientWebService/client.asmx
2010-06-02 09:57:28:452 940 4c8 PT Initializing simple targeting cookie,
clientId = 01e2a7b8-c5ec-4cfd-a807-0208eccc49b4, target group = , DNS name =
pcname
2010-06-02 09:57:28:452 940 4c8 PT Server URL =
http://servername.fqdn:80/SimpleAuthWebService/SimpleAuth.asmx
2010-06-02 09:57:33:413 940 ed8 AU Triggering AU detection through
DetectNow API
2010-06-02 09:57:33:413 940 ed8 AU Piggybacking on an AU detection already
in progress
2010-06-02 09:57:35:722 940 4c8 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2010-06-02 09:57:35:722 940 4c8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://servername.fqdn:80/ClientWebService/client.asmx
2010-06-02 09:57:35:784 940 4c8 PT Initializing simple targeting cookie,
clientId = 01e2a7b8-c5ec-4cfd-a807-0208eccc49b4, target group = , DNS name =
pcname
2010-06-02 09:57:35:784 940 4c8 PT Server URL =
http://servername.fqdn:80/SimpleAuthWebService/SimpleAuth.asmx
2010-06-02 09:57:36:127 940 4c8 Agent * Found 0 updates and 57 categories
in search; evaluated appl. rules of 484 out of 834 deployed entities
2010-06-02 09:57:36:127 940 4c8 Agent *********
2010-06-02 09:57:36:127 940 4c8 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2010-06-02 09:57:36:127 940 4c8 Agent *************
2010-06-02 09:57:36:127 940 13fc AU >>## RESUMED ## AU: Search for
updates [CallId = {CC3DB630-B953-444D-86D2-ACCBCEB00FAF}]
2010-06-02 09:57:36:127 940 13fc AU # 0 updates detected
2010-06-02 09:57:36:143 940 13fc AU #########
2010-06-02 09:57:36:143 940 13fc AU ## END ## AU: Search for updates
[CallId = {CC3DB630-B953-444D-86D2-ACCBCEB00FAF}]
2010-06-02 09:57:36:143 940 13fc AU #############
2010-06-02 09:57:36:143 940 13fc AU Successfully wrote event for AU health
state:0
2010-06-02 09:57:36:143 940 13fc AU Featured notifications is disabled.
2010-06-02 09:57:36:143 940 13fc AU AU setting next detection timeout to
2010-06-03 10:27:36
2010-06-02 09:57:36:143 940 13fc AU Setting AU scheduled install time to
2010-06-03 07:00:00
2010-06-02 09:57:36:143 940 13fc AU Successfully wrote event for AU health
state:0
2010-06-02 09:57:36:143 940 13fc AU Successfully wrote event for AU health
state:0
2010-06-02 09:57:36:377 940 4c8 Report CWERReporter finishing event
handling. (00000000)
2010-06-02 09:57:41:135 940 4c8 Report REPORT EVENT:
{35148D61-30E8-4666-BC86-0B8CCED31713} 2010-06-02
09:57:36:127-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2010-06-02 09:57:41:135 940 4c8 Report REPORT EVENT:
{6222299F-D331-4A45-85D8-6B0D6DCF5D80} 2010-06-02
09:57:36:127-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2010-06-02 09:57:41:135 940 4c8 Report CWERReporter finishing event
handling. (00000000)


The only changes that were made were taking out the servername.fqdn and the
dns computer name. Thanks in advance for your help.

Rick
Post by Lawrence Garvin [MVP]
The actual output of the Client Diagnostic Tool. The tool does not always
accurately identify issues.
1. Pick a machine that is not reporting.
2. Record the system time.
3. Restart the Automatic Updates service. (net stop wuauserv; net start
wuauserv).
4. Run this command: wuauclt /resetauthorization /detectnow
5. Wait 30 minutes.
6. Post all of the entries from the WindowsUpdate.log starting at the time
recorded in Step #2.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)
My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Lawrence Garvin [MVP]
2010-06-02 15:45:01 UTC
Permalink
Raw Message
Post by Rick
http://servername.fqdn:80/
http://servername.fqdn:80/
One thing you'll want to do, but is not likely a cause of this critical
issue -- is to remove the port specifier and trailing slash from the
configured URL.

http://servername.fqdn is sufficient for a WSUS service installed on the
Default Web Site.

The trailing slash has been known to cause duplicate slashes in URLs, which
sometimes does not translate well on the web server.
Post by Rick
2010-06-02 09:57:23:414 940 ed8 Agent * Target group: (Unassigned
Computers)
2010-06-02 09:57:35:784 940 4c8 PT Initializing simple targeting cookie,
clientId = 01e2a7b8-c5ec-4cfd-a807-0208eccc49b4,
target group = , DNS name = pcname
Are you using Server-Side Targeting, or Client-Side Targeting?
Post by Rick
2010-06-02 09:57:23:601 940 ed8 AU # Approval type: Scheduled (User
preference)
2010-06-02 09:57:23:601 940 ed8 AU # Auto-install minor updates: Yes
(User preference)
2010-06-02 09:57:23:601 940 ed8 AU # Will interact with non-admins
(Non-admins are elevated (User preference))
This is the first I've seen this suffix "User preference" on a log entry. Is
this a manifestation of using AUOptions=5 and configuring the WUAgent in the
Control Panel,
or have you implemented some Group Policy Client Side Preference settings?
Post by Rick
2010-06-02 09:57:36:127 940 4c8 Agent * Found 0 updates and 57
categories
in search; evaluated appl. rules of 484 out of 834 deployed entities
Okay.. so... whatever group(s) the client is scanning . . . it's not finding
any updates to install.


Also, notably absent from your logfile was a call to the
ReportingEventWebService; which explains the cause of your original
observation -- no clients are reporting.

Either you didn't post a full 30 minutes of log entries, or something is
blocking the calls to the ReportingEventWebService. I suspect it is the
latter, since if the call to the ReportingEventWebService did actually
occur, you would have at least one computer in your console.

Do you have System Center Configuration Manager installed in your
environment?
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Rick
2010-06-02 15:59:01 UTC
Permalink
Raw Message
OK- I removed the port and the trailing slash from the URL. For now, until
all the bugs are worked out with my compputer, I am just updating my local
group policy. I will change the domain GP when all the settings are correct.


I dont understand your targeting question.

I agree with your comments about not having approved updates to push to the
clients. I want to see where we are with each client before I just start
pushing updates. I did wait for 30 minutes before posting and we do have
System Center installed in our environment.

Thanks for you help so far. Please let me know if there is anything else I
can do.

Rick
Post by Lawrence Garvin [MVP]
Post by Rick
http://servername.fqdn:80/
http://servername.fqdn:80/
One thing you'll want to do, but is not likely a cause of this critical
issue -- is to remove the port specifier and trailing slash from the
configured URL.
http://servername.fqdn is sufficient for a WSUS service installed on the
Default Web Site.
The trailing slash has been known to cause duplicate slashes in URLs, which
sometimes does not translate well on the web server.
Post by Rick
2010-06-02 09:57:23:414 940 ed8 Agent * Target group: (Unassigned
Computers)
2010-06-02 09:57:35:784 940 4c8 PT Initializing simple targeting cookie,
clientId = 01e2a7b8-c5ec-4cfd-a807-0208eccc49b4,
target group = , DNS name = pcname
Are you using Server-Side Targeting, or Client-Side Targeting?
Post by Rick
2010-06-02 09:57:23:601 940 ed8 AU # Approval type: Scheduled (User
preference)
2010-06-02 09:57:23:601 940 ed8 AU # Auto-install minor updates: Yes
(User preference)
2010-06-02 09:57:23:601 940 ed8 AU # Will interact with non-admins
(Non-admins are elevated (User preference))
This is the first I've seen this suffix "User preference" on a log entry. Is
this a manifestation of using AUOptions=5 and configuring the WUAgent in the
Control Panel,
or have you implemented some Group Policy Client Side Preference settings?
Post by Rick
2010-06-02 09:57:36:127 940 4c8 Agent * Found 0 updates and 57
categories
in search; evaluated appl. rules of 484 out of 834 deployed entities
Okay.. so... whatever group(s) the client is scanning . . . it's not finding
any updates to install.
Also, notably absent from your logfile was a call to the
ReportingEventWebService; which explains the cause of your original
observation -- no clients are reporting.
Either you didn't post a full 30 minutes of log entries, or something is
blocking the calls to the ReportingEventWebService. I suspect it is the
latter, since if the call to the ReportingEventWebService did actually
occur, you would have at least one computer in your console.
Do you have System Center Configuration Manager installed in your
environment?
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)
My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Lawrence Garvin [MVP]
2010-06-02 16:52:41 UTC
Permalink
Raw Message
Post by Rick
I dont understand your targeting question.
This is a critical point, then. If you are not familiar with the
distinctions between server-side targeting and client-side targeting, then
there is a high degree of probability that this has been misconfigured, and
is contributing to your failure to detect updates.

I would suggest reviewing the following documentation selections:

From the Step-By-Step (Installation) Guide, Step 6: Configure Computer
Groups
http://technet.microsoft.com/en-us/library/dd939860(WS.10).aspx

From the Deployment Guide, the section Create the Computer Groups in the
chapter Configure the WSUS 3.0 SP2 Server
http://technet.microsoft.com/en-us/library/dd939826(WS.10).aspx
Post by Rick
and we do have System Center installed in our environment.
Then you'll also want to review this WSUS Support Team Blog Post, as it's
most likely the case that your System Center admins are responsible for your
reporting failures:

http://blogs.technet.com/b/sus/archive/2008/11/12/wsus-clients-install-updates-properly-but-don-t-send-any-status-reports-back-to-the-server.aspx
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Loading...