WSUS 3.0 question

A simple question, but I can't find an answer for it after searching for a
few days....

SBS 2003 R2 standard server -

I recently upgraded to WSUS 3.0 sp1. I found a white paper out there and
followed the instructions to do an upgrade.

Do I continue using update services in server management as I used to, or do
I now manage thru the update services console I now see installed under
start>administrative tools ??

I can't really tell if its working correctly or not, I did see a few updates
come in to the server management > update services, but I am also getting
event id 13001 in the event viewer.

"M. Murphy" <> wrote in message
news:...
>A simple question, but I can't find an answer for it after searching for a
>few days....
>
> SBS 2003 R2 standard server -
>
> I recently upgraded to WSUS 3.0 sp1. I found a white paper out there and
> followed the instructions to do an upgrade.

I hope it was mine. :-)


> Do I continue using update services in server management as I used to

No.

> or do I now manage thru the update services console I now see installed
> under start>administrative tools ??

Yes.

> but I am also getting event id 13001 in the event viewer.

Message: Client computers are installing updates with a higher than %1
percent failure rate. This should be monitored.

Probably a reflection of either an unsuccessful upgrade, or a misconfigured
environment.

Let's start with identifying the whitepaper, and specific steps, you used to
upgrade your SBS R2 (with WSUS2SP1) to WSUS3SP1.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Thank you for the info so far,

I read this article,
http://www.microsoft.com/downloads/d...n#RelatedLinks

and this, http://technet.microsoft.com/en-us/l...91(WS.10).aspx

and this, http://technet.microsoft.com/en-us/l...07(WS.10).aspx

and also this,
http://blogs.technet.com/sbs/archive...-behavior.aspx
I also searched around and read up on every other article and
troubleshooting posts that I could find, just to be as prepared as I could
be.

I didnt have the "blue shield" when I started out, but did have some issues
with the update services part of server management. If I followed the
"mowing the grass" procedure (http://www.wsuswiki.com/MowingtheGrass), those
issues went away, but they were coming back more frequently. Monitoring and
reporting was not working either, but since upgrading it is working again, I
am back to getting the daily reports in my email.


After the upgrade, the update services part of server management worked
again, there were a few updates available to approve, but I am also getting
that event id 13001 quite frequently. From reading all that stuff, I decided
to try running the server cleanup wizard. Did the steps one at a time, from
the bottom of the list up (read somewhere that was a good way to do it).
All of them worked except the first one in the list, unused updates and
update revisions. I let it run over the weekend, and it failed.

it gives up this error message,
The WSUS administration console was unable to connect to the WSUS Server
Database.

Verify that SQL server is running on the WSUS Server. If the problem
persists, try restarting SQL.


System.Data.SqlClient.SqlException -- Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding.
The statement has been terminated.

Source
..Net SqlClient Data Provider

Stack Trace:
at System.Windows.Forms.Control.MarshaledInvoke(Contr ol caller, Delegate
method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at System.Windows.Forms.Control.Invoke(Delegate method)
at
Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerC leanup.ServerCleanupWizard.OnCleanupComplete(Objec t
sender, PerformCleanupCompletedEventArgs e)

and I have to press "reset server node"

Wow, I hope I havent supplied too much info here.

Thanks for listening!!


"Lawrence Garvin [MVP]" <> wrote in message
news:...
> "M. Murphy" <> wrote in message
> news:...
>>A simple question, but I can't find an answer for it after searching for a
>>few days....
>>
>> SBS 2003 R2 standard server -
>>
>> I recently upgraded to WSUS 3.0 sp1. I found a white paper out there and
>> followed the instructions to do an upgrade.
>
> I hope it was mine. :-)
>
>
>> Do I continue using update services in server management as I used to
>
> No.
>
>> or do I now manage thru the update services console I now see installed
>> under start>administrative tools ??
>
> Yes.
>
>> but I am also getting event id 13001 in the event viewer.
>
> Message: Client computers are installing updates with a higher than %1
> percent failure rate. This should be monitored.
>
> Probably a reflection of either an unsuccessful upgrade, or a
> misconfigured environment.
>
> Let's start with identifying the whitepaper, and specific steps, you used
> to upgrade your SBS R2 (with WSUS2SP1) to WSUS3SP1.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"M. Murphy" <> wrote in message
news:%...
> Thank you for the info so far,
>
> I read this article,

All good articles.. but none (as I recall) specifically addresse the special
needs of migrating an SBS R2 WSUS2SP1 system to WSUS v3.

Here's a white paper that does discuss that -- unfortunately it's gotten
buried over time.
http://download.microsoft.com/downlo...3_networks.doc


> I didnt have the "blue shield" when I started out, but did have some
> issues with the update services part of server management. If I followed
> the "mowing the grass" procedure (http://www.wsuswiki.com/MowingtheGrass),

Arggh... be careful of older stuff that was written for =WSUS2= that's no
longer applicable to =WSUS3=. This is a great article by Jeff Centimano, but
it's somewhat dated in that many of those procedures are now 'built-in' to
WSUS v3 through the Server Cleanup Wizard.

Okay.. to cut to the chase... the most likely issue here is that you have
policies leftover from the R2-WSUS2SP1 installation that are either
conflicting with new policies that you've created for WSUS3, or are
misconfigured.

Whilst we're sorting out the R2-to-WSUS3SP1 upgrade, which is most likely
the *cause* of these issues, let's see if we can get some functionality
returned to your environment.

Run the Client Diagnostic Tool on the SBS/WSUS Server and post the results.

Run the Client Diagnostic Tool on one of your client systems and post the
results.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Ok, downloading the tool now, but are you sure you don't want me to run the
server tool on the server?


"Lawrence Garvin [MVP]" <> wrote in message
news:uUM6d$...
> "M. Murphy" <> wrote in message
> news:%...
>> Thank you for the info so far,
>>
>> I read this article,
>
> All good articles.. but none (as I recall) specifically addresse the
> special needs of migrating an SBS R2 WSUS2SP1 system to WSUS v3.
>
> Here's a white paper that does discuss that -- unfortunately it's gotten
> buried over time.
> http://download.microsoft.com/downlo...3_networks.doc
>
>
>> I didnt have the "blue shield" when I started out, but did have some
>> issues with the update services part of server management. If I followed
>> the "mowing the grass" procedure
>> (http://www.wsuswiki.com/MowingtheGrass),
>
> Arggh... be careful of older stuff that was written for =WSUS2= that's no
> longer applicable to =WSUS3=. This is a great article by Jeff Centimano,
> but it's somewhat dated in that many of those procedures are now
> 'built-in' to WSUS v3 through the Server Cleanup Wizard.
>
> Okay.. to cut to the chase... the most likely issue here is that you have
> policies leftover from the R2-WSUS2SP1 installation that are either
> conflicting with new policies that you've created for WSUS3, or are
> misconfigured.
>
> Whilst we're sorting out the R2-to-WSUS3SP1 upgrade, which is most likely
> the *cause* of these issues, let's see if we can get some functionality
> returned to your environment.
>
> Run the Client Diagnostic Tool on the SBS/WSUS Server and post the
> results.
>
> Run the Client Diagnostic Tool on one of your client systems and post the
> results.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"M. Murphy" <> wrote in message
news:...
> Ok, downloading the tool now, but are you sure you don't want me to run
> the server tool on the server?

The server tool will give us no useful information for what we need to
discover.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

log file from client (this client has a red x in the update services console
> computers> update services client computers list):
WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . PASS
Winhttp local machine ProxyBypass. . . . . . . PASS
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . PASS
User IE ProxyByPass. . . . . . . . . . . . . . PASS
User IE AutoConfig URL Proxy . . . . . . . . . PASS
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://CETEK01:8530
WUStatusServer = http://CETEK01:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS

log file from client tool ran on server:
WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . PASS
Winhttp local machine ProxyBypass. . . . . . . PASS
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . PASS
User IE ProxyByPass. . . . . . . . . . . . . . PASS
User IE AutoConfig URL Proxy . . . . . . . . . PASS
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://CETEK01:8530
WUStatusServer = http://CETEK01:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS


I am going back to reading your white paper, while I await your comments,
thank you once again.

"Lawrence Garvin [MVP]" <> wrote in message
news:uUM6d$...
> "M. Murphy" <> wrote in message
> news:%...
>> Thank you for the info so far,
>>
>> I read this article,
>
> All good articles.. but none (as I recall) specifically addresse the
> special needs of migrating an SBS R2 WSUS2SP1 system to WSUS v3.
>
> Here's a white paper that does discuss that -- unfortunately it's gotten
> buried over time.
> http://download.microsoft.com/downlo...3_networks.doc
>
>
>> I didnt have the "blue shield" when I started out, but did have some
>> issues with the update services part of server management. If I followed
>> the "mowing the grass" procedure
>> (http://www.wsuswiki.com/MowingtheGrass),
>
> Arggh... be careful of older stuff that was written for =WSUS2= that's no
> longer applicable to =WSUS3=. This is a great article by Jeff Centimano,
> but it's somewhat dated in that many of those procedures are now
> 'built-in' to WSUS v3 through the Server Cleanup Wizard.
>
> Okay.. to cut to the chase... the most likely issue here is that you have
> policies leftover from the R2-WSUS2SP1 installation that are either
> conflicting with new policies that you've created for WSUS3, or are
> misconfigured.
>
> Whilst we're sorting out the R2-to-WSUS3SP1 upgrade, which is most likely
> the *cause* of these issues, let's see if we can get some functionality
> returned to your environment.
>
> Run the Client Diagnostic Tool on the SBS/WSUS Server and post the
> results.
>
> Run the Client Diagnostic Tool on one of your client systems and post the
> results.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"M. Murphy" <> wrote in message
news:ej%...
> log file from client (this client has a red x in the update services
> console
> > computers> update services client computers list):

> log file from client tool ran on server:

Neither of these systems have any configuration errors and both are capable
of successfully registering with the WSUS Server.

> I am going back to reading your white paper, while I await your comments,

Let me know when you get there, and we can determine if there were any
issues in the upgrade process that we need to consider.

If not, our next step is to look at the WindowsUpdate.log for the client
with the red X.

1. Note the system time.
2. Restart the Automatic Updates service (net stop/start wuauserv).
3. Run the command 'wuauclt /resetauthorization /detectnow'
4. Wait 30 minutes.
5. Post the WindowsUpdate.log entries starting at the time recorded in Step
#1.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence, thank you for spending some time on my issue, I see that you are
quite busy in this group!

I didnt see any issues when installing the 3.0 package on the server, no
error messages popped up.
After playing around with the console, I was able to find a few updates that
had not been approved for the server, and got them to install.
There are 2 more computers with warning signs instead of the red x signs in
update services client computers, but I don't see any updates on the those
computers. I guess I will just wait for a few days to see if they come up.

Still can not use the cleanup wizard > unused updates and update revisions,
it still loses the connection to the node. This is the problem that
concerns me the most.

This computer with the red x is failing to install kb960353 and does not
seem to be getting any new ones -
I won't be able to get back to this tomorrow (day off, yea!!) but will be
back to troubleshooting on thursday.

Here is the log of the last 30 minutes after following your instructions:
2009-07-21 15:01:19:507 836 7ec AU ########### AU: Uninitializing
Automatic Updates ###########
2009-07-21 15:01:20:147 836 7ec Service *********
2009-07-21 15:01:20:147 836 7ec Service ** END ** Service: Service exit
[Exit code = 0x240001]
2009-07-21 15:01:20:147 836 7ec Service *************
2009-07-21 15:01:31:194 836 ac4 Misc =========== Logging initialized
(build: 7.1.6001.65, tz: -0400) ===========
2009-07-21 15:01:31:194 836 ac4 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-07-21 15:01:31:194 836 ac4 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-07-21 15:01:31:194 836 ac4 Service *************
2009-07-21 15:01:31:194 836 ac4 Service ** START ** Service: Service
startup
2009-07-21 15:01:31:194 836 ac4 Service *********
2009-07-21 15:01:31:194 836 ac4 Agent * WU client version 7.1.6001.65
2009-07-21 15:01:31:194 836 ac4 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-07-21 15:01:31:194 836 ac4 Agent * Access type: No proxy
2009-07-21 15:01:31:210 836 ac4 Agent * Network state: Connected
2009-07-21 15:02:04:335 836 434 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-07-21 15:02:04:335 836 434 Agent *********** Agent: Initializing
global settings cache ***********
2009-07-21 15:02:04:335 836 434 Agent * WSUS server: http://CETEK01:8530
2009-07-21 15:02:04:335 836 434 Agent * WSUS status server:
http://CETEK01:8530
2009-07-21 15:02:04:335 836 434 Agent * Target group: (Unassigned
Computers)
2009-07-21 15:02:04:335 836 434 Agent * Windows Update access disabled:
No
2009-07-21 15:02:04:350 836 434 DnldMgr Download manager restoring 0
downloads
2009-07-21 15:02:04:366 836 434 AU ########### AU: Initializing Automatic
Updates ###########
2009-07-21 15:02:04:382 836 434 AU # WSUS server: http://CETEK01:8530
2009-07-21 15:02:04:382 836 434 AU # Detection frequency: 1
2009-07-21 15:02:04:382 836 434 AU # Approval type: Pre-install notify
(Policy)
2009-07-21 15:02:04:382 836 434 AU # Auto-install minor updates: Yes
(Policy)
2009-07-21 15:02:04:382 836 434 AU # Will interact with non-admins
(Non-admins are elevated)
2009-07-21 15:02:04:382 836 434 AU AU finished delayed initialization
2009-07-21 15:02:04:382 836 434 AU Triggering AU detection through
DetectNow API
2009-07-21 15:02:04:382 836 434 AU Triggering Online detection
(non-interactive)
2009-07-21 15:02:04:944 836 ac4 Report *********** Report: Initializing
static reporting data ***********
2009-07-21 15:02:04:944 836 ac4 Report * OS Version = 5.1.2600.3.0.65792
2009-07-21 15:02:04:975 836 ac4 Report * Computer Brand = INTEL_
2009-07-21 15:02:04:975 836 ac4 Report * Computer Model = D845PESV
2009-07-21 15:02:04:975 836 ac4 Report * Bios Revision =
SV84510A.86A.0013.P08.0303171920
2009-07-21 15:02:04:975 836 ac4 Report * Bios Name = BIOS Date: 03/17/03
19:20:24 Ver: 08.00.07
2009-07-21 15:02:04:975 836 ac4 Report * Bios Release Date =
2003-03-17T00:00:00
2009-07-21 15:02:04:975 836 ac4 Report * Locale ID = 1033
2009-07-21 15:02:04:991 836 ac4 AU #############
2009-07-21 15:02:04:991 836 ac4 AU ## START ## AU: Search for updates
2009-07-21 15:02:04:991 836 ac4 AU #########
2009-07-21 15:02:04:991 836 ac4 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {18EAA158-8F4C-402B-B0C4-EE19BA810E51}]
2009-07-21 15:02:07:335 836 438 Agent *************
2009-07-21 15:02:07:335 836 438 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-07-21 15:02:07:335 836 438 Agent *********
2009-07-21 15:02:07:335 836 438 Agent * Online = Yes; Ignore download
priority = No
2009-07-21 15:02:07:335 836 438 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"
2009-07-21 15:02:07:335 836 438 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-07-21 15:02:07:335 836 438 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-07-21 15:02:07:335 836 438 Misc Microsoft signed: Yes
2009-07-21 15:02:07:366 836 438 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-07-21 15:02:07:382 836 438 Misc Microsoft signed: Yes
2009-07-21 15:02:07:413 836 438 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-07-21 15:02:07:428 836 438 Misc Microsoft signed: Yes
2009-07-21 15:02:07:428 836 438 Setup *********** Setup: Checking whether
self-update is required ***********
2009-07-21 15:02:07:428 836 438 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:428 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:444 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:444 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version
= 7.1.6001.65
2009-07-21 15:02:07:444 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:444 836 438 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required
version = 7.1.6001.65
2009-07-21 15:02:07:444 836 438 Setup * IsUpdateRequired = No
2009-07-21 15:02:16:647 836 438 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-07-21 15:02:16:647 836 438 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://CETEK01:8530/ClientWebService/client.asmx
2009-07-21 15:02:16:678 836 438 PT Initializing simple targeting cookie,
clientId = 76c42169-3baf-4e52-aa8d-ca64474944ab, target group = , DNS name =
oemcomputer.cetek.local
2009-07-21 15:02:16:678 836 438 PT Server URL =
http://CETEK01:8530/SimpleAuthWebSer...impleAuth.asmx
2009-07-21 15:02:16:881 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {AA98D401-BAC2-4069-B29B-01BE3425E2D6}.100, hr
= 8007066F
2009-07-21 15:02:17:085 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {4F1A6104-4297-4E6D-9D39-1BA87689000A}.102, hr
= 8007066F
2009-07-21 15:02:17:303 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {32E4DD06-3CC6-4491-8EBA-CB565635760F}.100, hr
= 8007066F
2009-07-21 15:02:17:491 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {6D6FD00B-5750-4C4B-B6B2-4D7D0C078F2E}.100, hr
= 8007066F
2009-07-21 15:02:17:678 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {3FC0F70C-5FA3-4A93-B1DC-394916AEF0CD}.100, hr
= 8007066F
2009-07-21 15:02:17:866 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {685D590F-500D-4D7D-84F2-0E0AE5496AE2}.100, hr
= 8007066F
2009-07-21 15:02:18:100 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {168AB016-1E46-4DBF-86FE-1A84E2612785}.100, hr
= 8007066F
2009-07-21 15:02:18:303 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {3C897489-76FC-4E20-890E-C3A75DF5F3A2}.101, hr
= 8007066F
2009-07-21 15:02:18:491 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {508C6349-D00C-47FF-9CEC-701CEF9CE0CC}.102, hr
= 8007066F
2009-07-21 15:02:18:960 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {BE30DC1D-9FE2-4656-8195-4EB6410B4B40}.100, hr
= 8007066F
2009-07-21 15:02:19:178 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {3BFC3924-FF81-4907-994D-CF5B2A71ADB1}.100, hr
= 8007066F
2009-07-21 15:02:19:397 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {E9030EE4-B527-4A0F-8F3B-5F1A6E545498}.101, hr
= 8007066F
2009-07-21 15:02:19:600 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {2631CB2A-8A93-496B-ADB8-731C6ED9E3BF}.101, hr
= 8007066F
2009-07-21 15:02:19:803 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {2669B77D-FD35-445F-B615-E189A0F7A41E}.101, hr
= 8007066F
2009-07-21 15:02:20:022 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {B6A60635-E227-4139-B7B1-694ABFBF1CBB}.101, hr
= 8007066F
2009-07-21 15:02:20:210 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {4CBF819A-44F0-4A36-AF94-E05509395CD6}.101, hr
= 8007066F
2009-07-21 15:02:20:460 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {55BA4A37-818B-40BD-ACB4-8FA7BF72FCC4}.100, hr
= 8007066F
2009-07-21 15:02:20:756 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {CE64FC3C-DD11-4800-B017-BF4EC04232FA}.100, hr
= 8007066F
2009-07-21 15:02:20:991 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {9378E1A9-E9FC-464A-A770-2EE7E1F3D513}.100, hr
= 8007066F
2009-07-21 15:02:21:428 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {F66A3AF1-9A47-40EB-87F8-33474E1C09B3}.101, hr
= 8007066F
2009-07-21 15:02:21:663 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {F5D6B773-713D-440B-A7CE-4EB66533F0EE}.100, hr
= 8007066F
2009-07-21 15:02:21:975 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {C36CBA7E-1265-47CF-8DA2-AD0F8A486080}.100, hr
= 8007066F
2009-07-21 15:02:22:303 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {569CAC54-9B54-4B63-88F8-EE5C48D9C930}.100, hr
= 8007066F
2009-07-21 15:02:22:960 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {00E6C573-C433-4430-949A-940C1D802836}.100, hr
= 8007066F
2009-07-21 15:02:23:241 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {1095F778-86FF-4AFC-906A-143B8EE8F7BF}.101, hr
= 8007066F
2009-07-21 15:02:23:444 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {FD772E79-C784-4F74-8A3F-B59998FFA6AB}.101, hr
= 8007066F
2009-07-21 15:02:23:741 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {86E0E187-9ADA-460A-B841-85AAAF0FC4C0}.100, hr
= 8007066F
2009-07-21 15:02:24:350 836 438 Agent WARNING: Failed to evaluate
Installable rule, updateId = {DD42B3A8-C735-4A59-818C-A29D92E43EF2}.100, hr
= 8007066F
2009-07-21 15:02:27:678 836 438 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2009-07-21 15:02:27:678 836 438 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://CETEK01:8530/ClientWebService/client.asmx
2009-07-21 15:02:41:584 836 438 Agent * Found 0 updates and 51 categories
in search; evaluated appl. rules of 763 out of 1084 deployed entities
2009-07-21 15:02:42:850 836 438 Agent *********
2009-07-21 15:02:42:850 836 438 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-07-21 15:02:42:850 836 438 Agent *************
2009-07-21 15:02:42:866 836 b98 AU >>## RESUMED ## AU: Search for updates
[CallId = {18EAA158-8F4C-402B-B0C4-EE19BA810E51}]
2009-07-21 15:02:42:866 836 b98 AU # 0 updates detected
2009-07-21 15:02:42:866 836 b98 AU #########
2009-07-21 15:02:42:866 836 b98 AU ## END ## AU: Search for updates
[CallId = {18EAA158-8F4C-402B-B0C4-EE19BA810E51}]
2009-07-21 15:02:42:866 836 b98 AU #############
2009-07-21 15:02:42:866 836 b98 AU AU setting next detection timeout to
2009-07-21 19:56:02
2009-07-21 15:02:47:850 836 438 Report REPORT EVENT:
{211EC388-09B0-4ADA-973F-43CA9DF2E9A3} 2009-07-21 15:02:42:850-0400 1 147
101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Software Synchronization Windows Update Client successfully detected 0
updates.
2009-07-21 15:02:47:850 836 438 Report REPORT EVENT:
{81537336-A9F9-4A19-B703-BA9ADECBA754} 2009-07-21 15:02:42:850-0400 1 156
101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success
Pre-Deployment Check Reporting client status.
2009-07-21 15:03:19:803 836 438 Report Uploading 4 events using cached
cookie, reporting URL =
http://CETEK01:8530/ReportingWebServ...ebService.asmx
2009-07-21 15:03:19:803 836 438 Report Reporter successfully uploaded 4
events.

"Lawrence Garvin [MVP]" <> wrote in message
news:...
> "M. Murphy" <> wrote in message
> news:ej%...
>> log file from client (this client has a red x in the update services
>> console
>> > computers> update services client computers list):
>
>> log file from client tool ran on server:
>
> Neither of these systems have any configuration errors and both are
> capable of successfully registering with the WSUS Server.
>
>> I am going back to reading your white paper, while I await your comments,
>
> Let me know when you get there, and we can determine if there were any
> issues in the upgrade process that we need to consider.
>
> If not, our next step is to look at the WindowsUpdate.log for the client
> with the red X.
>
> 1. Note the system time.
> 2. Restart the Automatic Updates service (net stop/start wuauserv).
> 3. Run the command 'wuauclt /resetauthorization /detectnow'
> 4. Wait 30 minutes.
> 5. Post the WindowsUpdate.log entries starting at the time recorded in
> Step #1.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"M. Murphy" <> wrote in message
news:%...

> This computer with the red x is failing to install kb960353 and does not
> seem to be getting any new ones -

I got good news.. and I gots bad news...

> Here is the log of the last 30 minutes after following your instructions:

The bad news is that either this client is not correctly configured to know
it's intended target group, or the one hour detection frequency is keeping
the targeting cookie from being expired (which, I note, was not expired in
this session even though the /resetauthorization should have explicitly
forced that to happen).

According to the service startup log entries... this computer is assigned to
"(Unassigned Computers)", which really translates to -- it's not been
assigned to a group yet.

Then, when the targeting cookie is initialized, which should have been
purged as a result of the /resetauthorization, the targeting cookie still
shows no assigned group.

> 2009-07-21 15:02:16:678 836 438 PT Initializing simple targeting cookie,
> clientId = 76c42169-3baf-4e52-aa8d-ca64474944ab,
> target group = ,
> DNS name = oemcomputer.cetek.local

Thus, the end result is that =zero= updates are being detected as approved
for installation.

> 2009-07-21 15:02:41:584 836 438 Agent * Found 0 updates and 51
> categories in search; evaluated appl. rules of 763 out of 1084 deployed
> entities


The good news is that this client system is detecting and reporting
correctly -- it just ain't finding anything to install.

So, as for KB960353 -- this clients doesn't even see that update as
available.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin