From: "Robert Comer" 

> SP2 has been very solid here so far, and as I said in another thread, SUS
> is
> working well for me.

It's working pretty well for me as well so far, I haven't really run into
any incompatibilities, though I do have to configure the firewall for our
apps for every PC I put it on, which isn't really a problem.  I wish it
gave a little more info when trying to block something, but it's definitely
a step in the right direction.

- Bob Comer


"Glenn Meadows"  wrote in message
news:4126600a{at}w3.nls.net...
> Yea, I figured it will roll out for all eventually as well.
>
> SP2 has been very solid here so far, and as I said in another thread, SUS
> is
> working well for me.
>
> --
> Glenn M.
>
>
> "Robert Comer" 
wrote in message
> news:41265ebe$1{at}w3.nls.net...
>> > 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.
>>
>> I've seen that one for a long time, I've had SP2 for quite awhile.
>>
>> It's not really uncommon for Microsoft to update WU.  (We are up to V5
> now)
>> I'd expect and update for older OS's to use it too, but I have no
> knowledge
>> of such a thing.
>>
>> - Bob Comer
>>
>>
>> "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.
>> >
>> > --
>> > 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.
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>

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