Windows Desktop Search deployed automatically

Exactly. See the question I'm just posting.
--
-Rob-


"dejuid00" wrote:

> Same happened here. NOT happy. It is an "Update" so it shouldn't install
> 3.0.1 unless I have 3.0.0. And, no, it wasn't previously approved either.
>
> "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.
> >
> > Needless to say that caused quite a stir.
> >
> > Anyone else have this happen or did I miss something?
> > The automatically approve previous approvals is on but WDS was not approved
> > previously.
> >
> > Tom
> >
> >
> >
 >> Stay informed about: Windows Desktop Search deployed automatically 

"dejuid00" wrote in message

> Same happened here. NOT happy. It is an "Update" so it shouldn't install
> 3.0.1 unless I have 3.0.0. And, no, it wasn't previously approved either.

Same here, how do I automatically remove it from the machines it has already
been installed to. I have now manually declined the update in WSUS?

Thanks,
Box
 >> Stay informed about: Windows Desktop Search deployed automatically 

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.

"Boxington Headmaker" wrote:

> "dejuid00" wrote in message
>
> > Same happened here. NOT happy. It is an "Update" so it shouldn't install
> > 3.0.1 unless I have 3.0.0. And, no, it wasn't previously approved either.
>
> Same here, how do I automatically remove it from the machines it has already
> been installed to. I have now manually declined the update in WSUS?
>
> Thanks,
> Box
>
>
>
 >> Stay informed about: Windows Desktop Search deployed automatically 

On Oct 24, 1:12 pm, Stu Jackson
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 

wrote in message

> On Oct 24, 1:12 pm, Stu Jackson
> 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?

Yes, I am sure I declined 2.6.x, yet 3.01 was auto approved and deployed.
This is causing us a lot of grief.

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

Funnily enough my server automatically declined this update!
Hmmm

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
 >> Stay informed about: Windows Desktop Search deployed automatically 

Ben Evans wrote in :

> Funnily enough my server automatically declined this update!
> Hmmm
>
> EggHeadCafe - .NET Developer Portal of Choice
> http://www.eggheadcafe.com
>

Both 2.6.6 and 3.0.1 are unapproved and show as not needed here.
 >> Stay informed about: Windows Desktop Search deployed automatically 

For some reason this update shows up as "not approved" when I list "any
except declined" updates, but when I list only unapproved updates it
doesn't show up. When I look at its status report it shows that it has
not been approved for any groups, but when I look at the actual details
it shows an approval status of "install" on a bunch of computers which
match up with two of my groups. I don't know what the deal is here but
it seems like Microsoft may have screwed something up with this update.


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.
>
> Needless to say that caused quite a stir.
>
> Anyone else have this happen or did I miss something?
> The automatically approve previous approvals is on but WDS was not approved
> previously.
>
> Tom
>
>
 >> Stay informed about: Windows Desktop Search deployed automatically 

Stu Jackson 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.

No, 2.6.6 has nothing to do with this. In most cases, the new revision of 3.01
would be automatically approved because the original revision of 3.01 was
already approved. The original revision only installed on machines that already
had WDS so most people would have approved it.

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

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.
 >> Stay informed about: Windows Desktop Search deployed automatically 

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, wrote:
> On Oct 25, 3:43 pm, "Harry Johnston [MVP]"
> wrote:
>
>
>
>
>
> > 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 

Revision to update would mean that yesterday they released an update and I
approved it and today they found they had to fix it. Same KB #, etc. This
is not a revision to an update, it is a newer update than the previosu update
but it is a replacement update, not a revision update.

This is absolutely abuse of trust and access.

Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA


"Stu Jackson" 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.
>
> "Boxington Headmaker" wrote:
>
> > "dejuid00" wrote in message
> >
> > > Same happened here. NOT happy. It is an "Update" so it shouldn't install
> > > 3.0.1 unless I have 3.0.0. And, no, it wasn't previously approved either.
> >
> > Same here, how do I automatically remove it from the machines it has already
> > been installed to. I have now manually declined the update in WSUS?
> >
> > Thanks,
> > Box
> >
> >
> >
 >> Stay informed about: Windows Desktop Search deployed automatically 

They were just about a day late (and a few billion dollars ahead) with that
change. Since every WSUS server in the world already has the patch, it is
completely meaningless to stop distributing it to WSUS servers.


Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA


"Gus" wrote:
> 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.
 >> Stay informed about: Windows Desktop Search deployed automatically