Update KB917013 - Windows Desktop Search 3.01

External Since: Oct 26, 2007 Posts: 1

It seems that we've got lucky because this update hasn't been pushed out to
our clients. However I actually would like to test it on a few workstations
but I'm not able to because the update now shows as 'Expired'. I presume
this is how Microsoft are resolving the issue they've inadvertently created
with this update going out automatically. Will it ever become 'unexpired' so
I can try it?

" " wrote:

> We noticed that this update "Windows Desktop Search 3.01 for Windows
> XP (KB917013) was being installed on client machines in our network.
> Since we have a scheduled day for reviewing and approving update for
> deployment, we know that no one approved this update. The previous
> version, "Windows Desktop Search 2.6.6 (KB926356)" had been declined
> as we have legitimate reasons for not wanting this software on our
> systems.
>
> Looking at the release date of 10/23/2007 for this update tells us
> that this is being pushed out without the opportunity to first review
> and test an update - which was kind of the point of implementing WSUS
> in the first place. Also, the update does not support removal.
> Great.
>
> Anyone else see this problem?
>
> Microsoft, what the hell are you thinking? No update should be
> automatically deployed in WSUS without approval - period.
>
> Allan Wingenbach
>
>

External Since: Oct 26, 2007 Posts: 1

On Oct 26, 7:33 am, wrote:
> We declined the update in WSUS, then had to go to each computer where
> this virus had installed and do the following:
>
> 1. Run "wuauclt /detectnow" at the command prompt.
> 2. Remove the desktop search virus from Add/Remove programs.
> 4. Reboot
> 3. Run "wuauclt /detectnow" at the command prompt again.
>
> The first windows update command ensures that the virus register as
> declined will not attempt to re-install after it is removed. We had
> to do this on just over 60 workstations, so we're feeling more than
> just a little negative toward MS search right now. There is perhaps a
> better way to do this in a vbs script that can be applied via a GPO,
> but we didn't have the time to mess around.
>
> Anyone out there care to provide a script that can do this? If I get
> some time today, I may be able to post one.
>
> Allan

So how do you set this up in zenworks? I am new to zenworks and am not
sure how to set this up. I tried setting up as simple application to
run as a batch file and I also tried setting it up as a distribution
script to run before distribution. Neither way is removing it. Please
help.