Is there a way to automatically update WUA using WSUS
sharkfist
WSUS. I have a problem with some machines being very slow and unusable on
startup. After reading some other posts I think the problem is due to an old
version of WUA. Rather than upgrade machines manually I'm hoping there is a
way to automate the process.
Thanks in advance
Lawrence Garvin [MVP]
"sharkfist" <shar...@discussions.microsoft.com> wrote in message
news:69F12E6B-A6C1-42C7...@microsoft.com...
> As the subject describes is there a way to automatically update WUA using
> WSUS.
Well... yes... it's a core feature of WSUS. It's called 'selfupdate'.
Perhaps you mean to ask -- Is there a way I can deploy a *newer* version of
the WUAgent using the WSUS selfupdating capability?
The answer to that question is No.
> I have a problem with some machines being very slow and unusable on
> startup. After reading some other posts I think the problem is due to an
> old
> version of WUA. Rather than upgrade machines manually I'm hoping there is
> a
> way to automate the process.
Being intimately familiar with the concerns about the potential performance
issues in the WUAgent v7.0 and v7.1, I can tell you there are a half dozen
other things that should be checked and verified before being concerned
about updating the WUAgent.
--
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/profile/Lawrence.Garvin
sharkfist
"Lawrence Garvin [MVP]" wrote:
> "sharkfist" <shar...@discussions.microsoft.com> wrote in message
> news:69F12E6B-A6C1-42C7...@microsoft.com...
> > As the subject describes is there a way to automatically update WUA using
> > WSUS.
>
> Well... yes... it's a core feature of WSUS. It's called 'selfupdate'.
>
> Perhaps you mean to ask -- Is there a way I can deploy a *newer* version of
> the WUAgent using the WSUS selfupdating capability?
That's what I meant. I'll be clearer next time. Somewhat assumed that
people knowing WSUS would understand my request.
>
> The answer to that question is No.
That's what I thought :(
>
> > I have a problem with some machines being very slow and unusable on
> > startup. After reading some other posts I think the problem is due to an
> > old
> > version of WUA. Rather than upgrade machines manually I'm hoping there is
> > a
> > way to automate the process.
>
> Being intimately familiar with the concerns about the potential performance
> issues in the WUAgent v7.0 and v7.1, I can tell you there are a half dozen
> other things that should be checked and verified before being concerned
> about updating the WUAgent.
>
I have a bunch of machines that become very slow and unusable on startup.
I've narrowed it down to them running an older version of WUA ((7.1.6001.65).
It doesn't seem to be a problem on machines runnig 7.2.6001.788. Hence my
question re: updating using WSUS.
Intrestingly enough I see that SP2 will include a new version of WUA, but I
don't want to use a RC in a production environment.
It seems like I'm going to have to script the install through GPO.
Lawrence Garvin [MVP]
That may be a coincidental symptom.
> It doesn't seem to be a problem on machines runnig 7.2.6001.788. Hence my
> question re: updating using WSUS.
Well, yes, there are performance issues in the v7.1 client, but in *many*
circumstances, these issues are caused by SERVER-side conditions.
> Intrestingly enough I see that SP2 will include a new version of WUA, but
> I
> don't want to use a RC in a production environment.
Fair enough.
> It seems like I'm going to have to script the install through GPO.
NO... first you need to apply the proper remediations in the proper order.
Updating the WUAgent, as I tried to point out in my last post, is the FIFTH
step in a process of five steps for investigating such performance issues.
They are:
[1] Upgrade to WSUS v3.1 and apply KB927891 (obviously not an issue here).
[2] If Outlook 2003 has been installed on Office XP installations, upgrade
Office XP to Office 2003.
[3] This issue is quite commonly caused by a LARGE number of updates having
been installed to an Office 2003 installation. This is caused because the
%windir%\Installer folder is excessively large, and causing the WUAgent to
spend unnecessary effort scanning "already installed" updates on the local
machine in order to determine applicability.
The recommended remediation is:
[a] Uninstall/Reinstall Office 2003.
[b] Apply Office 2003 Service Pack 3 directly.
[c] Apply remaining Office 2003 updates.
[4] Decline all superceded updates on the WSUS Server. In fact, this issue
is more often the cause, and the solution (and a much easier and more
appropriate solution, at that), than trying to update the WUAgent on dozens
or hundreds of clients.
[5] IF *ALL* of the above have been eliminated as possible causes, then
updating the WUAgent is appropriate. You can update the WUAgent by using the
WindowsUpdateAgent30-x86 (or WindowsUpdateAgent30-x64.exe) installers, which
will install the v7.2 WUAgent. (And, of course, WSUS3SP2RC can be used to
deploy the v7.4 RC WUAgent).
Now.. I'll grant that #3 may not be a desirable solution -- but you should
also know that if #3 is an issue, upgrading the WUAgent to v7.2 may not
resolve your issue.