Andrew
Fri Sep 12 19:16:22 CDT 2003
I'll be honest-- I never stop Exchange or AV and I haven't had a
problem yet. I could see Exchange but I definitely don't like allowing
unchecked files-- even Microsoft files-- into the network unless it won't
work any other way in a particular case.
"Kevin Weilbacher" <kweilbac@gte.net> wrote in message
news:es5Hr6MeDHA.1736@TK2MSFTNGP12.phx.gbl...
> Andrew,
>
> RE: your comment "I know Windows Update is not well-liked for servers...",
I
> would say that from what I have observer over the last two years, the
issue
> or concern with WU was that often WU would not work correctly on SBS
> servers, or cause proiblems.
>
> However, once it was identified that stopping Exchange & A/V services
before
> using WU --- there have been little issues posted here in this NG. So,
> although WU does work, just don't run it in automatic update mode for the
> server. I follow up WU with either HfNetChk or MBSA to ensure all known
> patches are discovered.
>
> -kw
>
>
> "Andrew M. Saucci, Jr." <andrew@2000computer.com> wrote in message
> news:OEsZYWMeDHA.2140@TK2MSFTNGP10.phx.gbl...
> > Basically, what I've been doing is Windows Update followed by
MBSA
> > to verify the critical stuff and Exchange, ISA, SQL, etc. If MBSA still
> > complains, then I download what's left manually. I know Windows Update
is
> > not well-liked for servers but I can't find anything more practical, and
> > I've monitored its activity. All it does is download a series of patches
> and
> > run them sequentially. If one really, really wanted to be careful, the
way
> > to go would be to apply one patch at a time and reboot after each one--
> but
> > at ten minutes per patch, it simply cannot be done in a reasonable
amount
> of
> > time.
> >
> > "Kevin Weilbacher" <kweilbac@gte.net> wrote in message
> > news:uTNuARLeDHA.3788@tk2msftngp13.phx.gbl...
> > > 1. There are no guarantees in life when it comes to computers,
updates,
> > and
> > > whether things will work or not.
> > > 2. Saying that there are simple things you can do.
> > > 3. Understand the Windows Update (WU) does NOT report all patches -
for
> > > example it does not report SQL patches, or Exchange patches.
> > > 4. Most people use a combination of WU and perhaps HfNetChkLT - which
is
> > > free.
> > > 5. Here's what I recommend and what I do with patches:
> > >
> > > a. I never install or apply the recommended patches or driver patches
> from
> > > WU - only the critical patches.
> > > b. I also use HfNetChkLT to identify other patches (SQL, Exhchange,
> etc.)
> > > c. I always reboot my server BEFORE installing patches, and thne clear
> out
> > > my event id logs.
> > > d. I also make sure I have a recent ERD diskette nad tape backup
> > > e. I install the patches. If there happens to be a lot of patches to
> > > install, I will review them and install the major ones first
> > > f. I then reboot the server again after installing some or all of the
> > > patches.
> > >
> > > -kw
> > >
> > > "jhardy" <jhardy012003@yahoo.com.au> wrote in message
> > > news:097501c37873$483ec030$a501280a@phx.gbl...
> > > > Hi
> > > >
> > > > What is the easiest way to keep my server updated with the
> > > > latest microsoft updates?
> > > >
> > > > How do i know that these updates will not screw up my
> > > > Server?
> > > >
> > > > I have got a dial up modem connection to the internet from
> > > > the Server.
> > > >
> > > > Please, please, please keep it simple for me.
> > > >
> > > > thanks again
> > >
> > >
> >
> >
>
>