From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0CF8_01C486C7.BF01B2F0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Windows Update is on its fifth major version.  Migrations are always =
separate for different operating system releases.  I wouldn't be =
surprised if older versions are still on the v3 site.

Rich

  "Glenn Meadows"  wrote in message =
news:41265bb7{at}w3.nls.net...
  Oh, and the Windows Update site/pages are now different for XP, at =
least if
  SP2 is in place on Pro.  After updating a system using SUS (which =
worked
  great, BTW), I used the regular Windows Update Web Page, to see what
  non-critical updates might be there, and I got a request to allow the =
latest
  version of WU to download, so I let it come down (new dialogs =
displaying),
  and then the page was different, with two options, for two different =
styles
  of update.

  Went back with a Win2K machine, and got the old page, so XP is =
migrating to
  a different, maybe more intelligent, or maybe just different Update =
engine.

  --=20
  Glenn M.


  "Robert Comer"  wrote in message
  news:412656da$1{at}w3.nls.net...
  > > This is changing under our feet as we speak.  Today I took a
  fully-patched
  > > machine, set to "download, then ask" to WinUpdate. 
It prompted me =
with
  a
  > > standard "may I?" dialog for the asx client v5.  I
declined SP2, =
and the
  > > pages
  > > in MyComputer had already changed to the new style, and WinUpdate, =
of
  > > course,
  > > displayed with the new look.
  >
  > I'm not surprised. :(
  >
  > > I also noticed some nice behavior from NIS. (Get thee behind me; =
shakes
  > > rattle).  A full (with reboot) update of NIS this week gets the =
WMI
  > > client,
  > > and *intercepts* the security panel installation, advising the =
user to
  go
  > > with
  > > NIS instead of Windows Firewall.  Accept that, and NIS takes over =
fully
  > > and
  > > properly, as the only firewall.
  >
  > Oh gak, that's even worse!
  >
  > - Bob Comer
  >
  >
  >
  > "Frank Haber"  wrote in message
  > news:4126540f$1{at}w3.nls.net...
  > > >This is all easy to recreate, install WinXP (anything =
apparently), make
  > > >sure
  > > auto update is turned off from the get-go (not just prompt)  WU up =
all
  the
  > > patches available -- no security dialog change, turn on autoupdate =
and
  > > wait
  > > for it to cycle, new security dialog.
  > >
  > > This is changing under our feet as we speak.  Today I took a
  fully-patched
  > > machine, set to "download, then ask" to WinUpdate. 
It prompted me =
with
  a
  > > standard "may I?" dialog for the asx client v5.  I
declined SP2, =
and the
  > > pages
  > > in MyComputer had already changed to the new style, and WinUpdate, =
of
  > > course,
  > > displayed with the new look.
  > >
  > > I also noticed some nice behavior from NIS. (Get thee behind me; =
shakes
  > > rattle).  A full (with reboot) update of NIS this week gets the =
WMI
  > > client,
  > > and *intercepts* the security panel installation, advising the =
user to
  go
  > > with
  > > NIS instead of Windows Firewall.  Accept that, and NIS takes over =
fully
  > > and
  > > properly, as the only firewall.
  > >
  >
  >


------=_NextPart_000_0CF8_01C486C7.BF01B2F0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Windows
Update is on its =
fifth major=20
version.  Migrations are always separate for different operating = system=20
releases.  I wouldn't be surprised if older versions are still on
= the v3=20
site.
 
Rich
 

  "Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in message=20
  news:41265bb7{at}w3.nls.net...Oh=
,=20
  and the Windows Update site/pages are now different for XP, at least =
ifSP2=20
  is in place on Pro.  After updating a system using SUS (which=20
  workedgreat, BTW), I used the regular Windows Update Web Page, to =
see=20
  whatnon-critical updates might be there, and I got a request to =
allow the=20
  latestversion of WU to download, so I let it come down (new =
dialogs=20
  displaying),and then the page was different, with two options, for =
two=20
  different stylesof update.Went back with a
Win2K machine, =
and got=20
  the old page, so XP is migrating toa different, maybe more =
intelligent, or=20
  maybe just different Update engine.-- Glenn =
M."Robert=20
  Comer" <bobcomer_removeme{at}mindsp=">mailto:bobcomer_removeme{at}mindspring.com">bobcomer_removeme{at}mindsp=
ring.com>=20
  wrote in messagenews:412656da$1{at}w3.nls.net...=
>=20
  > This is changing under our feet as we speak.  Today I took=20
  afully-patched> > machine, set to
"download, then ask" =
to=20
  WinUpdate.  It prompted me witha>
> standard "may =
I?"=20
  dialog for the asx client v5.  I declined SP2, and the> =
>=20
  pages> > in MyComputer had already changed to the
new style, =
and=20
  WinUpdate, of> > course,>
> displayed with the new =

  look.>> I'm not surprised.
:(>> > I =
also=20
  noticed some nice behavior from NIS. (Get thee behind me; =
shakes> >=20
  rattle).  A full (with reboot) update of NIS this week gets the=20
  WMI> > client,> > and
*intercepts* the security =
panel=20
  installation, advising the user togo> >
with> =
> NIS=20
  instead of Windows Firewall.  Accept that, and NIS takes over=20
  fully> > and> > properly,
as the only=20
  firewall.>> Oh gak, that's even
worse!>> - =
Bob=20
 
Comer>>>>
"Frank Haber" <frhaber{at}N0SPMrcn.com>">mailto:frhaber{at}N0SPMrcn.com">frhaber{at}N0SPMrcn.com>
=
wrote in=20
  message> news:4126540f$1{at}w3.nls.net...=
>=20
  > >This is all easy to recreate, install WinXP (anything =
apparently),=20
  make> > >sure> >
auto update is turned off from =
the=20
  get-go (not just prompt)  WU up
allthe> > patches =
available=20
  -- no security dialog change, turn on autoupdate and> > =
wait>=20
  > for it to cycle, new security dialog.>
>> > =
This is=20
  changing under our feet as we speak.  Today I took=20
  afully-patched> > machine, set to
"download, then ask" =
to=20
  WinUpdate.  It prompted me witha>
> standard "may =
I?"=20
  dialog for the asx client v5.  I declined SP2, and the> =
>=20
  pages> > in MyComputer had already changed to the
new style, =
and=20
  WinUpdate, of> > course,>
> displayed with the new =

  look.> >> > I also
noticed some nice behavior from =
NIS.=20
  (Get thee behind me; shakes> > rattle). 
A full (with =
reboot)=20
  update of NIS this week gets the WMI> >
client,> > =
and=20
  *intercepts* the security panel installation, advising the user=20
  togo> > with> >
NIS instead of Windows =
Firewall. =20
  Accept that, and NIS takes over fully> >
and> > =
properly,=20
  as the only firewall.>=20
>>>

------=_NextPart_000_0CF8_01C486C7.BF01B2F0--

--- BBBS/NT v4.01 Flag-5