Ok... so if you look at 936301 it has links in it that I'm guessing you
downloaded and applied on your WSUS 2.0 SP1 server?? If so this is not how it
works. You need to have 936301 downloaded on your WSUS server and you need to
approve it for install. You also need to have your WSUS server pointed
towards itself for updates. I would set a deadline on it in the past a run a
detectnow to get things kicked off quicker. This should force the install of
the 936301 update on your WSUS 2.0 SP1 server and update the selfupdate tree
to start handing out the WUA 3.0 client. The links off of the KB936301 are
just the links to the WUA 3.0 client which only updates the actual WUA client
on the WSUS server to 3.0 and not the actual selfupdate tree itself from what
I understand.
My VM is currently down otherwise i would test this to make sure for you but
thats how I currently understand the process is supposed to work.
Hopefully this helps
Kurt Falde [MSFT]
"JPenrose" wrote:
[Quoted Text] > Thanks Hank,
>
> 3 days prior to approving the MSI update I updated my WSUS 2.0 SP1 server so
> it would build a self update tree for the 3.0 client KB936301). I waited 3
> days and then let the MSI go. It turns out that the clients are still at
> 5.8.0.2607 not 7.0.6000.374 as I expected. No self update.
>
> What am I doing wrong here? I applied 936301 to the WSUS server to build the
> self update tree and my clients check in every day with the server. I recall
> that updates to WSUS itself were pre approved so I went back to check and I
> see the BITS update (with the old WU logo next to it) from 2005 but I don't
> see a pre approved update for the WU client. Any ideas would be appreciated.
> I don't think I'm alone with this issue.
>
> -J
>
> "Hank Arnold" wrote:
>
> > To fix the problem, you need *both* this patch and the new 3.0 client.
> >
> > Regards,
> > Hank Arnold
> >
> > JPenrose wrote:
> > > When I uninstall it the clients no longer have an issue. After checking into
> > > it more it seems that when this patch is installed it does the opposite of
> > > what it was intended to do. My understanding is that 927891 was supposed to
> > > fix the svchost 100% CPU issue with automatic updates when combined with WUAU
> > > 3.0 client. It appears that the exact opposite has happened; the update has
> > > caused the issue to surface not prevent it.
> > >
> > > Am I going mad or is this the ultimate insulting irony? I pushed this via
> > > WSUS 2.0 SP1 to over 100 clients.
> > >
> > > "Nigel Jett" wrote:
> > >
> > >> I recently deployed this patch to my beta test group, so far none of
> > >> them have reported any issues.
> > >> Does the slowness go away when you manually uninstall it? (can it even
> > >> be uninstalled? I've noticed more patches can't be these days).
> > >>
> > >> JPenrose wrote:
> > >>> Is anyone having trouble with slow logins and performance hits after
> > >>> installing 927891 with WSUS?
> > >>>
> > >>> Second question: what method can be deployed to uninstall 927891 from 100 or
> > >>> PCs if I determine it's the cause of the issue. I'm hoping it's not the
> > >>> heel-toe-express.
> > >>>
> > >>> Thanks,
> > >>> JPenrose
> >
|