Windows Desktop Search deployed automatically

Gus wrote:

> The WSUS team made a mistake.

Doesn't explain Allan's situation. The scenario Bobbie describes only applies
if "Automatically approve new revisions of updates that are already approved" is
enabled; on Allan's system it isn't.

Harry.
 >> Stay informed about: Windows Desktop Search deployed automatically 

allan.wingenbach.DeleteThis@gmail.com wrote:

>> However, this shouldn't have happened if "Automatically approve new revisions of
>> updates that are already approved" is disabled. Could you please doublecheck
>> that this is the case?
>
> I have double checked this, and can assure you that it had been
> disabled since early 2006.

Thanks. Have you noticed this symptom (a new revision of an approved update
being automatically approved despite the setting) before? It would probably be
helpful in diagnosing the problem to have more than one example. Of course I
realize that depending on your methodology this might (ordinarily!) pass
unnoticed, but I thought I'd be optimistic and ask anyway.

Harry.
 >> Stay informed about: Windows Desktop Search deployed automatically 

Select WSUS Updates in the tree to the left of the console. Now on the right
of the console, click search.

In the search window, type the word "search" (no quotes) in the Text field.
Click Find Now.

In each result for WDS, right-click and choose Show Revision History.

It absolutely proves (though maybe not legally proves) that Microsoft is at
fault and violated our trust to install - either accidentally or purposefully
- software that, 1. Customers did not authorize them to install, 2.
Customers did not want, and 3. Microsoft has been losing the battle to
install legitimately in the competitive marketplace.

Dale

--
Dale Preston
MCAD C#
MCSE, MCDBA


"Harry Johnston [MVP]" wrote:

> Peter Ogden wrote:
>
> > The blog says: "...many of you who had approved the initial update package
> > for a limited number of machines, had Tuesdays' WDS revision 105
> > automatically install on all clients because of the expanded applicability
> > scope and because by default, WSUS is set to automatically approve update
> > revisions."
> >
> > We did have automatically approve new revisions enabled, but have never
> > approved WDS on any PC's at any time, yet it still installed on all our
> > PC's. So the Blog isn't entirely correct.
>
> The problem is that (as far as I am aware) there is no built-in way of verifying
> that the previous version of the update wasn't approved, and no particular
> reason why it wouldn't be. Since it came out almost seven months ago it seems
> reasonable to suppose that you might not remember correctly; I certainly
> wouldn't trust my own memory of a routine decision made that long ago.
>
> On the other hand, while it is possible that there is a bug in WSUS that can
> approve updates spontaneously, it is unlikely that it would hit only this one
> particular update.
>
> So from my point of view it is more likely that you are mistaken about this than
> that Microsoft is. Of course it's a different matter if you keep detailed
> records of which updates you approve, and if you do - or if anyone else does and
> experienced the behaviour Peter describes - I'd be very interested to hear about it.
>
> Harry.
>
 >> Stay informed about: Windows Desktop Search deployed automatically 

"Harry Johnston [MVP]" <harry.TakeThisOut@scms.waikato.ac.nz> wrote in message
news:%233wgtB4FIHA.1188@TK2MSFTNGP04.phx.gbl...
> Peter Ogden wrote:
>
>> The blog says: "...many of you who had approved the initial update
>> package for a limited number of machines, had Tuesdays' WDS revision 105
>> automatically install on all clients because of the expanded
>> applicability scope and because by default, WSUS is set to automatically
>> approve update revisions."
>>
>> We did have automatically approve new revisions enabled, but have never
>> approved WDS on any PC's at any time, yet it still installed on all our
>> PC's. So the Blog isn't entirely correct.
>
> The problem is that (as far as I am aware) there is no built-in way of
> verifying that the previous version of the update wasn't approved, and no
> particular reason why it wouldn't be. Since it came out almost seven
> months ago it seems reasonable to suppose that you might not remember
> correctly; I certainly wouldn't trust my own memory of a routine decision
> made that long ago.
>
> On the other hand, while it is possible that there is a bug in WSUS that
> can approve updates spontaneously, it is unlikely that it would hit only
> this one particular update.
>
> So from my point of view it is more likely that you are mistaken about
> this than that Microsoft is. Of course it's a different matter if you
> keep detailed records of which updates you approve, and if you do - or if
> anyone else does and experienced the behaviour Peter describes - I'd be
> very interested to hear about it.
>
> Harry.

As I am the only person in our environment that approves these updates and
decides what our SOE shall be, I am very well aware of what I want installed
and what I don't. I have never wanted Desktop Search and have never approved
it for any WSUS group. Granted, I don't keep records other than what WSUS
shows me, but it definitely installed without approval on our systems.
Perhaps there is some other glitch in our copy of WSUS that allowed it
through, but it certainly caused us some grief.

- Peter Ogden
 >> Stay informed about: Windows Desktop Search deployed automatically 

> As I am the only person in our environment that approves these updates and
> decides what our SOE shall be, I am very well aware of what I want
installed
> and what I don't. I have never wanted Desktop Search and have never
approved
> it for any WSUS group. Granted, I don't keep records other than what WSUS
> shows me, but it definitely installed without approval on our systems.

*Exactly* the same situation here.

Regards
Rolf Lidvall
Swedish Radio (Ltd)
 >> Stay informed about: Windows Desktop Search deployed automatically 

Yes. Same situation here. In my case, it was deployed to 200 Point of Sale
systems in 80 locations.

I'll be looking for an automated removal tool if anybody has any hints.

"allan.wingenbach@gmail.com" wrote:

> On Oct 24, 1:12 pm, Stu Jackson <StuJack....DeleteThis@discussions.microsoft.com>
> wrote:
> > It looks like the Windows Desktop Search 3.01 was auto approved and pushed
> > because of a buried advanced setting in Update Services. If you go to the
> > Automatic Approvals Options and click on the advanced tab there is a section
> > for Revision to Updates. One of the options in that section is Automatically
> > approve new revisions of updates that are already installed. The Windows
> > Desktop Search 3.01 update is considered an update to Windows Desktop Search
> > 2.6.6 and if that was ever approved in your Update Services then you
> > automatically got approval of this one provided that option was turned on.
> >
> > You would think that someone would have noticed what this was going to do
> > and maybe done something to warn the IT community or setup the update so that
> > it didn't auto update.
> >
>
> We have the Automatically Approve New Revisions disabled, Windows
> Desktop Search 2.6.6 was declined way back when and the Windows
> Desktop Search 3.01 STILL auto approved and deployed. Anyone else see
> this behavior?
>
>
 >> Stay informed about: Windows Desktop Search deployed automatically 

On Oct 25, 9:43 pm, "Harry Johnston [MVP]" <ha... DeleteThis @scms.waikato.ac.nz>
wrote:
> allan.wingenb... DeleteThis @gmail.com wrote:
> >> However, this shouldn't have happened if "Automatically approve new revisions of
> >> updates that are already approved" is disabled. Could you please doublecheck
> >> that this is the case?
>
> > I have double checked this, and can assure you that it had been
> > disabled since early 2006.
>
> Thanks. Have you noticed this symptom (a new revision of an approved update
> being automatically approved despite the setting) before? It would probably be
> helpful in diagnosing the problem to have more than one example. Of course I
> realize that depending on your methodology this might (ordinarily!) pass
> unnoticed, but I thought I'd be optimistic and ask anyway.
>
> Harry.

We've never seen this before in WSUS. We've used it since early
versions of SUS, and have come to trust it for updates after
developing a methodology for reviewing and approving updates. Now
I'll be watching it much closer after spending a late night at the
office uninstalling the desktop search virus and not spending time
with my kids. Thanks WSUS team.
 >> Stay informed about: Windows Desktop Search deployed automatically 

Tom S wrote:

> I woke up this morning (was woken actually) to find out that Windows Desktop
> Search 3.01 was synchronized yersterday evening and automatically approved
> for install on all computers.

<http://blogs.technet.com/wsus/>

The summary is that the previous revision of the 3.01 update only installed on
machines that already have WDS. The new revision installed on all machines. By
default new revisions of approved updates are automatically approved.

There is no response yet to the reports of the new revision being automatically
approved for people who have WSUS configured to /not/ automatically approve new
revisions of approved updates.

Harry.
 >> Stay informed about: Windows Desktop Search deployed automatically 

"Harry Johnston [MVP]" <harry DeleteThis @scms.waikato.ac.nz> wrote in message
news:OX1kj50FIHA.1188@TK2MSFTNGP04.phx.gbl...
> Tom S wrote:
>
>> I woke up this morning (was woken actually) to find out that Windows
>> Desktop Search 3.01 was synchronized yersterday evening and automatically
>> approved for install on all computers.
>
> <http://blogs.technet.com/wsus/>
>
> The summary is that the previous revision of the 3.01 update only
> installed on machines that already have WDS. The new revision installed
> on all machines. By default new revisions of approved updates are
> automatically approved.
>
> There is no response yet to the reports of the new revision being
> automatically approved for people who have WSUS configured to /not/
> automatically approve new revisions of approved updates.
>
> Harry.

The blog says: "...many of you who had approved the initial update package
for a limited number of machines, had Tuesdays' WDS revision 105
automatically install on all clients because of the expanded applicability
scope and because by default, WSUS is set to automatically approve update
revisions."

We did have automatically approve new revisions enabled, but have never
approved WDS on any PC's at any time, yet it still installed on all our
PC's. So the Blog isn't entirely correct.

- Peter Ogden
 >> Stay informed about: Windows Desktop Search deployed automatically 

Same thing here. I have never approved a Windows Desktop Search update of
any type. My WSUS backs me up and shows that the previous versions were not
approved.

Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA


"Peter Ogden" wrote:

>
> "Harry Johnston [MVP]" <harry.TakeThisOut@scms.waikato.ac.nz> wrote in message
> news:OX1kj50FIHA.1188@TK2MSFTNGP04.phx.gbl...
> > Tom S wrote:
> >
> >> I woke up this morning (was woken actually) to find out that Windows
> >> Desktop Search 3.01 was synchronized yersterday evening and automatically
> >> approved for install on all computers.
> >
> > <http://blogs.technet.com/wsus/>
> >
> > The summary is that the previous revision of the 3.01 update only
> > installed on machines that already have WDS. The new revision installed
> > on all machines. By default new revisions of approved updates are
> > automatically approved.
> >
> > There is no response yet to the reports of the new revision being
> > automatically approved for people who have WSUS configured to /not/
> > automatically approve new revisions of approved updates.
> >
> > Harry.
>
> The blog says: "...many of you who had approved the initial update package
> for a limited number of machines, had Tuesdays' WDS revision 105
> automatically install on all clients because of the expanded applicability
> scope and because by default, WSUS is set to automatically approve update
> revisions."
>
> We did have automatically approve new revisions enabled, but have never
> approved WDS on any PC's at any time, yet it still installed on all our
> PC's. So the Blog isn't entirely correct.
>
> - Peter Ogden
>
>
>
 >> Stay informed about: Windows Desktop Search deployed automatically 

On Oct 26, 1:01 pm, John Harbridge <John
Harbri....RemoveThis@discussions.microsoft.com> wrote:
> Yes. Same situation here. In my case, it was deployed to 200 Point of Sale
> systems in 80 locations.
>
> I'll be looking for an automated removal tool if anybody has any hints.
>
>
what about scripting something to call the uninstall then using psexec
to call each machine? i'm thingking something like this (untested)

IF EXIST %WINDIR%\$NTUninstallKB917013$\spuninst (
NET STOP "Windows Search"
%WINDIR%\$NtUninstallKB917013$\spuninst\spuninst.exe /passive /
forcerestart
)

again, untested with about 10 minutes of checking the syntax?

~todd.fencl aka todd.fencl

>
> "allan.wingenb...@gmail.com" wrote:
> > On Oct 24, 1:12 pm, Stu Jackson <StuJack....RemoveThis@discussions.microsoft.com>
> > wrote:
> > > It looks like the Windows Desktop Search 3.01 was auto approved and pushed
> > > because of a buried advanced setting in Update Services. If you go to the
> > > Automatic Approvals Options and click on the advanced tab there is a section
> > > for Revision to Updates. One of the options in that section is Automatically
> > > approve new revisions of updates that are already installed. The Windows
> > > Desktop Search 3.01 update is considered an update to Windows Desktop Search
> > > 2.6.6 and if that was ever approved in your Update Services then you
> > > automatically got approval of this one provided that option was turned on.
>
> > > You would think that someone would have noticed what this was going to do
> > > and maybe done something to warn the IT community or setup the update so that
> > > it didn't auto update.
>
> > We have the Automatically Approve New Revisions disabled, Windows
> > Desktop Search 2.6.6 was declined way back when and the Windows
> > Desktop Search 3.01 STILL auto approved and deployed. Anyone else see
> > this behavior?- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: Windows Desktop Search deployed automatically 

Dale wrote:

> In each result for WDS, right-click and choose Show Revision History.

You haven't filled in all the blanks, but I assume you mean that because the
previous revision to the WDS 3.01 update shows as "Not Approved" you are
assuming that this proves you did not approve it. Unfortunately, this isn't the
case; when a new revision is automatically approved, the old revision is
automatically unapproved.

Presumably this is so clients don't attempt to download and install two
different revisions of the same update!

> It absolutely proves (though maybe not legally proves) that Microsoft is at
> fault [...]

That isn't at question; of course they are, and they've already admitted it. I
approved the 3.01 update back in February in order to update any systems that
already had WDS; revisions of this update should not have caused it to install
on other systems. This was caused by human error at Microsoft.

However, if you really didn't approve the original revision of the update when
it was released in February, then there is /another/ problem as yet unexplained.
This is why I'm interested; unfortunately, as I said before, we can't really
build much of a case on the memory of a casual decision made seven months ago,
particularly when it would be such an unlikely coincidence that these two
unrelated problems would affect the same update.

Harry.
 >> Stay informed about: Windows Desktop Search deployed automatically 

Please make it possible to uninstall via WSUS!!! Why "Approved for Removal"
is greyed?

I don't have "Automatic Approval" active but WDS spread to all 300+
computers (XP and 2003 Servers)

"Gus" wrote:

> The WSUS team made a mistake. Bobbie's response pasted below:
>
> WDS update revision follow - up
> Posted Thursday, October 25, 2007 11:50 PM by WSUS
> Hi Folks -
>
> I wanted to get back to you with more information and guidance around
> the Windows Desktop Search (WDS) issue and the results of our
> investigation today.
>
> As you know, Windows Desktop Search was published last February 07, as
> an optional update that was only applicable to systems which had WDS
> previously installed. Then on Tuesday of this week we revised that
> update package to be applicable (but still optional) to Windows XP SP2
> and Windows Server 2003 SP1+ systems which did not have WDS installed.
> Unfortunately, in revising this update, the decision to re-use the
> same update package had unintended consequences to our WSUS
> customers. Namely many of you who had approved the initial update
> package for a limited number of machines, had Tuesdays' WDS revision
> 105 automatically install on all clients because of the expanded
> applicability scope and because by default, WSUS is set to
> automatically approve update revisions. We sincerely regret the
> inconvenience this has caused and extend a sincere apology to all
> impacted customers.
>
> For those of you who want to uninstall the WDS update revision
> released Tuesday of this week, this can be done via
>
> 1. Add/remove programs
>
> 2. Invoking spunisnts: %windir%\$NtUninstallKB917013$\spuninst
> \spuninst.exe /q /promptrestart
>
> 3. Using System Restore on Windows XP (not available on Windows Server
> 2003). This option will leave some software on the machine, but the
> invocation effectively removes WDS 3.01. This should only be used for
> conditions where the /noback switch was used.
>
> I want you to know we are working now to correct the issue and have
> temporarily suspended the distribution of the Windows Desktop Search
> through WSUS. The current package will remain available through the
> Microsoft Download Center. We will make a new package available for
> WSUS in the near future, but not as an update revision, so that you
> can rely on predictable update behavior with auto-approval settings.
> We are also working on improving our internal publishing processes to
> ensure this does not happen again in the future.
>
> Again, our sincere apologies for this publishing process error.
>
> Bobbie Harder
>
> Program Manager, WSUS
>
>
>
>
>
> On Oct 25, 10:33 pm, allan.wingenb....RemoveThis@gmail.com wrote:
> > On Oct 25, 3:43 pm, "Harry Johnston [MVP]" <ha....RemoveThis@scms.waikato.ac.nz>
> > wrote:
> >
> >
> >
> >
> >
> > > allan.wingenb....RemoveThis@gmail.com wrote:
> > > > We have the Automatically Approve New Revisions disabled, Windows
> > > > Desktop Search 2.6.6 was declined way back when and the Windows
> > > > Desktop Search 3.01 STILL auto approved and deployed. Anyone else see
> > > > this behavior?
> >
> > > Desktop Search 2.6.6 is irrelevant to this issue.
> >
> > > However, this shouldn't have happened if "Automatically approve new revisions of
> > > updates that are already approved" is disabled. Could you please doublecheck
> > > that this is the case?
> >
> > > If it is, there is an additional technical issue that Microsoft are unaware of,
> > > or at least haven't acknowledged yet.
> >
> > > Harry.
> >
> > I have double checked this, and can assure you that it had been
> > disabled since early 2006.- Hide quoted text -
> >
> > - Show quoted text -
>
>
>
 >> Stay informed about: Windows Desktop Search deployed automatically