"Power Point" <PowerPoint@discussions.microsoft.com> wrote in message
news:A7034F42-1A7F-427F-AB80-F3B8E33FD97D@microsoft.com...
>> I'm having the same problem here. I'm dealing with 4000 computers & as
>> soon
>> as I heard about the problem, I unapproved the update. Installing it
>> manually
>> is not really an option. Not all computers have the issue, but they all
>> report a sucessful install to the server. The ReportingEvents log is no
>> help.
>> It says the update has been installed, then 2 lines later it says ready
>> for
>> installation. I've tried deleting the DataStore.edb & the contents of the
>> download folder, but it still comes back like a bad penny. Any ideas
>> other
>> than to install it manually would be appreciated.
> Roger I am with you. I cannot believe no one has reported this issue.
> Microsoft doesnt even post anything on this issue! when I search on this
> issue all i get is my post! AGGHH
Well, in fact, to date, only TWO people have reported this issue, and you've
not really given me (or anybody else here) a lot to work with.
But the basic behavior you're reporting is not uncommon, and certainly not
exclusive to this update.
Typically when an update reports successful installation, but continues to
attempt to install, it's either because the installation is, in fact,
failing - but misreporting success -- or because the metadata that's used to
determine if the update is installed, is defective.
Now, added to this mix is that this update is a "Windows Live" update, so
who knows what the issue might actually be.
I will make these observations: Although I approved it for installation on
my desktops, in fact, I believe none of my desktops have the Windows Live
Sign-In Assistant module installed. To my benefit, the update is reporting
as Not Applicable on all machines in my network.
My first question, of course, would be: Do you have the Windows Live Sign-In
Assistant installed on your machines?
My second question would be: What *version* of the Windows Live Sign-In
Assistant is installed? This update was originally released over a year ago.
To my recollection there have been at least two new versions of Windows Live
products released since February, 2008, so I'm guessing that this update is
for the older Windows Live and it's lacking the necessary capacity to
properly deal with the newer versions. Possibly, even, the newer versions
have already incorporated. According to the KB article, this update appears
to be designed to upgrade the 4.x versions to the Live Sign-In Assistant
v5.0. If your systems already have a Live Sign-In Assistance v5.x or later
installed, this could be the cause.
Another possibility, according to the KB article, this update is only
applicable to Windows XP systems. Did you approve this update for Vista or
server systems?
Oh.. and deleting the DataStore.edb because an update malfunctions at
installation.... that's pretty bloody radical, and might even be
*contributing* or *complicating* your issues!
So.... If you have machines still running Windows Live Sign-In Assistant
v4.x (which, as noted, was replaced by a newer version over a year ago),
then put them in a special WSUS target group, and approve this update only
for those machines. If you have an issue installing this update on a
machines that is an intended target, let's work through one of those
examples.
Otherwise -- simple solution -- which you've already done -- Don't Approve
Updates You Don't Need!
--
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 Websites:
http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin