|
|
I have several machines keeping trying to install this update again and
again. Is there anyway that I can take some update that has already
approved out of the updates list from WSUS console?
|
|
|
|
Lawrence Garvin wrote:
[Quoted Text] > "april" <april[ at ]123.com> wrote in message
> news:u7LSPpFMJHA.276[ at ]TK2MSFTNGP02.phx.gbl...
>> I have several machines keeping trying to install this update again
>> and again. Is there anyway that I can take some update that has
>> already approved out of the updates list from WSUS console?
>
> Mark it as "Not Approved"???
>
But I think that the update has already been downloaded in the
workstation. Will "not approved" take the download back?
I appreciate your response. Thank you very much!
|
|
"april" <april[ at ]123.com> wrote in message
news:eaJG4KGMJHA.4668[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] >>> I have several machines keeping trying to install this update again and
>>> again. Is there anyway that I can take some update that has already
>>> approved out of the updates list from WSUS console?
>> Mark it as "Not Approved"???
> But I think that the update has already been downloaded in the
> workstation. Will "not approved" take the download back?
Yes. If you mark an update as "Not Approved" that has previously been marked
as "Approved", and even downloaded, but not yet installed, when the client
performs the next detection it will see that the update is no longer
approved for installation and it will unschedule the pending installation.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
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/profile/Lawrence.Garvin
|
|
april wrote:
[Quoted Text] > I have several machines keeping trying to install this update again and
> again. Is there anyway that I can take some update that has already
> approved out of the updates list from WSUS console?
Lawrence has already explained how to do this, but I wanted to add that this
will leave the affected machines insecure. It would be preferable to fix the
problem that is causing the installation to fail. (Typically this is due to a
printer driver locking the affected file, and the easiest fix is to manually
install the update in safe mode.)
Harry.
|
|
"Harry Johnston [MVP]" <harry[ at ]scms.waikato.ac.nz> wrote in message
news:%23AR$cAKMJHA.4772[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > april wrote:
>
>> I have several machines keeping trying to install this update again and
>> again. Is there anyway that I can take some update that has already
>> approved out of the updates list from WSUS console?
>
> Lawrence has already explained how to do this, but I wanted to add that
> this will leave the affected machines insecure.
Perhaps so, and let me clarify my recommendation to "unapprove" the updates.
First, there was a lot of confusion recently over a package of updates that
came out for MSXML, and out of that came the awareness (for a lot of people,
particularly myself), that there are currently five different versions of
MSXML in distribution -- most of which can exist side-by-side.
Plus, the MSXML4 and MSXML6 packages also, now, have service packs that are
applicable.
With all the several variations of MSXML out there, it's not lost on me that
there might be undiscovered defects in the detection logic of individual
update packages.
> It would be preferable to fix the problem that is causing the installation
> to fail.
Allow me to absolutely endorse this statement.
The number one solution is always: Fix the problem! (Don't work around
it---FIX IT!).
However, that should not discount the possibility that the "fix" is that a
particular update is being erroneously detected as Needed. In all such
scenarios, it's incumbent upon a patch administrator to *verify* that a
patch is actually applicable to a given system. If the patch is applicable,
then the appropriate resolution is to diagnose and repair why the
installation is failing -- and sometimes it's as simple as performing the
installation on an idle system (as is typically the case with .NET Framework
Service Packs). If the patch is not applicable, the appropriate resolution
(nay, the only resolution), may be to create a special group to handle the
defective update, mark it as "Not Approved" for that group, and put all
systems who are known to not need the update --into that special group so
the update is no longer detected.
> (Typically this is due to a printer driver locking the affected file, and
> the easiest fix is to manually install the update in safe mode.)
Never actually encountered this -- but I have no doubt it's a distinct
possiblity!
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
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/profile/Lawrence.Garvin
|
|
Lawrence Garvin wrote:
[Quoted Text] > However, that should not discount the possibility that the "fix" is that
> a particular update is being erroneously detected as Needed.
Agreed. However, in this particular case:
>> (Typically this is due to a printer driver locking the affected file,
>> and the easiest fix is to manually install the update in safe mode.)
>
> Never actually encountered this -- but I have no doubt it's a distinct
> possiblity!
There have been a /lot/ of reports of this in the windowsupdate group, so
failure to install successfully is the way to bet. :-)
Harry.
|
|
|