 |
|
|
|
Next: Reports: Separating the installed and the Not App..
|
| Author |
Message |
External
Since: Jun 15, 2005
Posts: 22
|
(Msg. 1) Posted: Fri Oct 26, 2007 11:02 am
Post subject: WDS 3.01 dead horse
Archived from groups: microsoft>public>windows>server>update_services (more info?)
|
|
|
At the risk of getting my head chopped off...
I keep seeing posts (rants) here talking about how this was a completely new
version of WDS and how everyone did not have it set to install and it
installed without approval, etc, etc....
The first claim is not the case.
WDS 3.01 r102 was released in March 2007.
WDS 3.01 r105 was released this week.
Also, if you didn't restore a copy of your file server from before it
downloaded this update,
you don't know if the March 2007 version of WDS was approved ot not because
this one superceded it.
You can't blame this all on MS because it worked as advertised.
I'm guessing in most cases, the March update was approved for install on all
computers and since it wasn't needed, it never downloaded.
If you can prove that a legitimate bug or error caused this, get with
Microsoft so they can fix it.
If it was previously approved and it deployed because the "applicability"
changed, then get over it and move on.
Tom S |
|
| Back to top |
|
 | |
External
Since: May 24, 2006
Posts: 5
|
(Msg. 2) Posted: Fri Oct 26, 2007 11:57 am
Post subject: Re: WDS 3.01 dead horse [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Lie down on the block.
The March update was an update applicable only to machines already using
WDS. The "revision" was set to detect as needed on any machine. MS has
already admitted they screwed the pooch on this one.
"Tom S" <me.RemoveThis@work.com> wrote in
news:e9bwXp$FIHA.700@TK2MSFTNGP05.phx.gbl:
> At the risk of getting my head chopped off...
>
> I keep seeing posts (rants) here talking about how this was a
> completely new version of WDS and how everyone did not have it set to
> install and it installed without approval, etc, etc....
>
> The first claim is not the case.
>
> WDS 3.01 r102 was released in March 2007.
> WDS 3.01 r105 was released this week.
>
> Also, if you didn't restore a copy of your file server from before it
> downloaded this update,
> you don't know if the March 2007 version of WDS was approved ot not
> because this one superceded it.
>
> You can't blame this all on MS because it worked as advertised.
>
> I'm guessing in most cases, the March update was approved for install
> on all computers and since it wasn't needed, it never downloaded.
>
> If you can prove that a legitimate bug or error caused this, get with
> Microsoft so they can fix it.
>
> If it was previously approved and it deployed because the
> "applicability" changed, then get over it and move on.
>
> Tom S
>
>
> |
|
| Back to top |
|
| |
External
Since: Jun 15, 2005
Posts: 22
|
(Msg. 3) Posted: Fri Oct 26, 2007 12:14 pm
Post subject: Re: WDS 3.01 dead horse [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Do I get a blindfold? 
"Asher_N" <ashernat DeleteThis @gmail.com> wrote in message
news:Xns99D597F6022AF1203214562@207.46.248.16...
> Lie down on the block.
>
> The March update was an update applicable only to machines already using
> WDS. The "revision" was set to detect as needed on any machine. MS has
> already admitted they screwed the pooch on this one.
>
> "Tom S" <me DeleteThis @work.com> wrote in
> news:e9bwXp$FIHA.700@TK2MSFTNGP05.phx.gbl:
>
>> At the risk of getting my head chopped off...
>>
>> I keep seeing posts (rants) here talking about how this was a
>> completely new version of WDS and how everyone did not have it set to
>> install and it installed without approval, etc, etc....
>>
>> The first claim is not the case.
>>
>> WDS 3.01 r102 was released in March 2007.
>> WDS 3.01 r105 was released this week.
>>
>> Also, if you didn't restore a copy of your file server from before it
>> downloaded this update,
>> you don't know if the March 2007 version of WDS was approved ot not
>> because this one superceded it.
>>
>> You can't blame this all on MS because it worked as advertised.
>>
>> I'm guessing in most cases, the March update was approved for install
>> on all computers and since it wasn't needed, it never downloaded.
>>
>> If you can prove that a legitimate bug or error caused this, get with
>> Microsoft so they can fix it.
>>
>> If it was previously approved and it deployed because the
>> "applicability" changed, then get over it and move on.
>>
>> Tom S
>>
>>
>>
> >> Stay informed about: WDS 3.01 dead horse |
|
| Back to top |
|
| |
External
Since: Jan 28, 2007
Posts: 14
|
(Msg. 4) Posted: Fri Oct 26, 2007 2:03 pm
Post subject: RE: WDS 3.01 dead horse [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
I don't know why you feel the risk of getting your head chopped off - unless
you knew you were speaking without really understanding what you're talking
about.
http://dalepreston.com/images/trojanwsus2007.png
You can see that the new update does not overwrite the March update status.
The history is still shown.
This is not a case of accidentally expanding approvals beyond where they
should have been, as Microsoft has indicated. This is a case, accidental or
not, of Microsoft instructing my WSUS to approve installation of a Microsoft
product that was specifically declined in the past and had not been installed
on any PC on my network.
Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA
"Tom S" wrote:
> At the risk of getting my head chopped off...
>
> I keep seeing posts (rants) here talking about how this was a completely new
> version of WDS and how everyone did not have it set to install and it
> installed without approval, etc, etc....
>
> The first claim is not the case.
>
> WDS 3.01 r102 was released in March 2007.
> WDS 3.01 r105 was released this week.
>
> Also, if you didn't restore a copy of your file server from before it
> downloaded this update,
> you don't know if the March 2007 version of WDS was approved ot not because
> this one superceded it.
>
> You can't blame this all on MS because it worked as advertised.
>
> I'm guessing in most cases, the March update was approved for install on all
> computers and since it wasn't needed, it never downloaded.
>
> If you can prove that a legitimate bug or error caused this, get with
> Microsoft so they can fix it.
>
> If it was previously approved and it deployed because the "applicability"
> changed, then get over it and move on.
>
> Tom S
>
>
> >> Stay informed about: WDS 3.01 dead horse |
|
| Back to top |
|
| |
External
Since: Oct 26, 2007
Posts: 1
|
(Msg. 5) Posted: Fri Oct 26, 2007 3:05 pm
Post subject: Re: WDS 3.01 dead horse [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
"Asher_N" <ashernat DeleteThis @gmail.com> wrote in message
news:Xns99D597F6022AF1203214562@207.46.248.16...
> Lie down on the block.
>
> The March update was an update applicable only to machines already using
> WDS. The "revision" was set to detect as needed on any machine. MS has
> already admitted they screwed the pooch on this one.
>
I agree. This thing killed me. Not a nice thing to come into work and find
this deployed to 5000 PCs. I scripted this command to run against every PC:
%systemroot%\$NtUninstallKB917013$\spuninst\spuninst.exe /quiet /norestart
but it was still a ridiculous and unnecessary pain. >> Stay informed about: WDS 3.01 dead horse |
|
| Back to top |
|
| |
External
Since: Jul 10, 2007
Posts: 7
|
(Msg. 6) Posted: Fri Oct 26, 2007 5:34 pm
Post subject: Re: WDS 3.01 dead horse [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Dale wrote:
> I don't know why you feel the risk of getting your head chopped off -
> unless you knew you were speaking without really understanding what
> you're talking about.
>
> http://dalepreston.com/images/trojanwsus2007.png
>
> You can see that the new update does not overwrite the March update
> status. The history is still shown.
>
> This is not a case of accidentally expanding approvals beyond where
> they should have been, as Microsoft has indicated. This is a case,
> accidental or not, of Microsoft instructing my WSUS to approve
> installation of a Microsoft product that was specifically declined in
> the past and had not been installed on any PC on my network.
>
>
Dale, There's several reported cases where this seems to be true, but it's
not generally the case. If you have a specific case where you are certain
you had *No* prior approval of the previous WDS version for *any* WSUS
computer group, you can best help MS and the community in general with this
issue by getting the information (&documentation) to MS and the WSUS team.
This should be a free call to CSS if you have no other partner or MS direct
connections.
> Dale
>
>> At the risk of getting my head chopped off...
>>
>> I keep seeing posts (rants) here talking about how this was a
>> completely new version of WDS and how everyone did not have it set
>> to install and it installed without approval, etc, etc....
>>
>> The first claim is not the case.
>>
>> WDS 3.01 r102 was released in March 2007.
>> WDS 3.01 r105 was released this week.
>>
>> Also, if you didn't restore a copy of your file server from before it
>> downloaded this update,
>> you don't know if the March 2007 version of WDS was approved ot not
>> because this one superceded it.
>>
>> You can't blame this all on MS because it worked as advertised.
>>
>> I'm guessing in most cases, the March update was approved for
>> install on all computers and since it wasn't needed, it never
>> downloaded.
>>
>> If you can prove that a legitimate bug or error caused this, get with
>> Microsoft so they can fix it.
>>
>> If it was previously approved and it deployed because the
>> "applicability" changed, then get over it and move on.
>>
>> Tom S
--
/kj >> Stay informed about: WDS 3.01 dead horse |
|
| Back to top |
|
| |
| Related Topics: | | WSUS Dead or Alive - I am looking into a patch management solution for several customers and was interested in finding out how long will WSUS be supported by Microsoft with patches? Should I wait for the launch of Windows deployment serves (WDS)? If so how long for WDS... |
|
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Profile
Private Messages
Log in
