Bug city

Let's face it folks, this product is riddled with bugs! I've got clean
installs left and right with all my "T's" crossed and "I's" dotted. BUGGY!

"Steve" <> wrote in message
news:6F225CB3-5F43-4267-8251-...
> Let's face it folks, this product is riddled with bugs! I've got clean
> installs left and right with all my "T's" crossed and "I's" dotted.
> BUGGY!

Truly, this post smells like trolling. If that's your intent, take it
elsewhere please.

But if you're actually interested in solving a problem -- Some *actual*
information would help immensely!

I *can* tell you, unequivocally, that if you had a CLEAN installation,
everything would be working perfectly. I've done dozens and dozens of CLEAN
installs over the past four years, and never once has anything failed to
work out of the box. If you have something not working "out of the box",
then either you're not installing to a CLEAN system, or you're not following
the documented installation and configuration procedures.



--
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 Garvin [MVP]" wrote:

> "Steve" <> wrote in message
> news:6F225CB3-5F43-4267-8251-...
> > Let's face it folks, this product is riddled with bugs! I've got clean
> > installs left and right with all my "T's" crossed and "I's" dotted.
> > BUGGY!
>
> Truly, this post smells like trolling. If that's your intent, take it
> elsewhere please.
>
> But if you're actually interested in solving a problem -- Some *actual*
> information would help immensely!
>
> I *can* tell you, unequivocally, that if you had a CLEAN installation,
> everything would be working perfectly. I've done dozens and dozens of CLEAN
> installs over the past four years, and never once has anything failed to
> work out of the box. If you have something not working "out of the box",
> then either you're not installing to a CLEAN system, or you're not following
> the documented installation and configuration procedures.
>
>
>
> --
> 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
>
>

I've got numerous machines reporting that they have "Needed" updates, but
those same updates have already been applied. WindowsUpdate log shows the
below information in a similar manner for each machine. The Console will not
seem to reconcile despite resetting via /resetauthorization and /detectnow.


009-08-06 09:10:05:661 868 714 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-08-06 09:10:05:661 868 714 Setup Update NOT required for
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wuapi.dll\7.2.6001.788\wuapi.dll:
target version = 7.2.6001.788, required version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wuapi.dll\7.2.6001.788\wuapi.dll.mui:
target version = 7.2.6001.788, required version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wups.dll\7.2.6001.788\wups.dll: target version = 7.2.6001.788, required version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\SoftwareDistribution\Setup\Ser viceStartup\wups2.dll\7.2.6001.788\wups2.dll:
target version = 7.2.6001.788, required version = 7.1.6001.65
2009-08-06 09:10:05:676 868 714 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65

"Steve" <> wrote in message
news:18E1AC41-7163-415F-9EC7-...

>> > Let's face it folks, this product is riddled with bugs! I've got clean
>> > installs left and right with all my "T's" crossed and "I's" dotted.
>> > BUGGY!

>> Truly, this post smells like trolling. If that's your intent, take it
>> elsewhere please.
>>
>> But if you're actually interested in solving a problem -- Some *actual*
>> information would help immensely!
>>
>> I *can* tell you, unequivocally, that if you had a CLEAN installation,
>> everything would be working perfectly. I've done dozens and dozens of
>> CLEAN
>> installs over the past four years, and never once has anything failed to
>> work out of the box. If you have something not working "out of the box",
>> then either you're not installing to a CLEAN system, or you're not
>> following
>> the documented installation and configuration procedures.

> I've got numerous machines reporting that they have "Needed" updates,

The below log segment shows *Nothing* about needed updates.

> WindowsUpdate log shows the
> below information in a similar manner for each machine. The Console will
> not
> seem to reconcile despite resetting via /resetauthorization and
> /detectnow.

Hmm.. what we have here is a panic over normal entries in a logfile as a
result of being unfamiliar with what one is reading.

> 009-08-06 09:10:05:661 868 714 Setup Update NOT required for
> C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required
> version
> = 7.1.6001.65

This is a NORMAL indication, and will be logged at EVERY detection event. It
is the WUAgent checking the 'selfupdate' feature of the WSUS Server to
determine if it needs to be updated. In this case, it does not. The
installed WUAgent is v7.2.6001.788 (which was likely obtained from WU/MU
during an earlier session), and the minimum required version is v7.1.6001.65
(which is what's available from WSUS via the selfupdate feature).



--
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 Garvin [MVP]" wrote:

> "Steve" <> wrote in message
> news:18E1AC41-7163-415F-9EC7-...
>
> >> > Let's face it folks, this product is riddled with bugs! I've got clean
> >> > installs left and right with all my "T's" crossed and "I's" dotted.
> >> > BUGGY!
>
> >> Truly, this post smells like trolling. If that's your intent, take it
> >> elsewhere please.
> >>
> >> But if you're actually interested in solving a problem -- Some *actual*
> >> information would help immensely!
> >>
> >> I *can* tell you, unequivocally, that if you had a CLEAN installation,
> >> everything would be working perfectly. I've done dozens and dozens of
> >> CLEAN
> >> installs over the past four years, and never once has anything failed to
> >> work out of the box. If you have something not working "out of the box",
> >> then either you're not installing to a CLEAN system, or you're not
> >> following
> >> the documented installation and configuration procedures.
>
> > I've got numerous machines reporting that they have "Needed" updates,
>
> The below log segment shows *Nothing* about needed updates.
>
> > WindowsUpdate log shows the
> > below information in a similar manner for each machine. The Console will
> > not
> > seem to reconcile despite resetting via /resetauthorization and
> > /detectnow.
>
> Hmm.. what we have here is a panic over normal entries in a logfile as a
> result of being unfamiliar with what one is reading.
>
> > 009-08-06 09:10:05:661 868 714 Setup Update NOT required for
> > C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required
> > version
> > = 7.1.6001.65
>
> This is a NORMAL indication, and will be logged at EVERY detection event. It
> is the WUAgent checking the 'selfupdate' feature of the WSUS Server to
> determine if it needs to be updated. In this case, it does not. The
> installed WUAgent is v7.2.6001.788 (which was likely obtained from WU/MU
> during an earlier session), and the minimum required version is v7.1.6001.65
> (which is what's available from WSUS via the selfupdate feature).
>
>
>
> --
> 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, Freud. The primary issue, however, is that the Console is not
updating.

"Steve" <> wrote in message
news:9FCF55C7-70BF-4275-895A-...

> Thank you, Freud.


Snide remarks, beyond your original demonstrated attitude, will not endear
those in this group qualified and (still) interested in helping you.

> The primary issue, however, is that the Console is not updating.


Then, perhaps showing relevant information to this issue would be helpful.
Merely showing that the WUAgent is not (nor should be) updated, tells us
nothing about what the WUAgent is actually doing. (Note, the Console is
"updated" by activity initiated by the WUAgent, so if the console "appears
to be" not updating, it is most likely because the WUAgent is not properly
reporting to the console -- possibly because it has been misconfigured.)

Please do the following to assist in identifying WHY the Console appears to
be not updating.

1. Download and run the Client Diagnostic Tool. Post the output (unedited).

2. Perform this procedure:

a. Note the system time
b. Restart the Automatic Updates service (net stop/start wuauserv)
c. Run this command: wuauclt /resetauthorization /detectnow
d. Wait =30= minutes
e. Post all entries (unedited) from the WindowsUpdate.log 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

Steve wrote:

> Thank you, Freud. The primary issue, however, is that the Console is not
> updating.

You realise it may take several hours after a successful detection event before
the new information is visible from the console?

Harry.