Re: Updates broke the network!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Today Noctaire commented courteously on the subject at hand

I hope you fix this, but I'm curious: how'd you allow
/clients/ to set AU to "automatic"? Your experience is
quite common - go to bed with everying A-OK and wake up to
dead system(s). Dpending on how you charge for your
services, lack of due diligence that causes damage may
cause you some financial and legal woes, which
coulda/shoulda been easily preventable.

Although I manage my clients' networks/systems, they are
still owned by the client. I advise them on various
matters and let them decide which direction is best to
take. In some cases, I have them on a monthly maintenance
plan that includes remote support. On the rare occasion
something breaks, I typically remote in and fix it.

In each case, I ensure there is data redundancy and
appropriate backup measures. Automatic updates seldom
cause grief, believe it or not, as they're critical updates
only and if something does go wrong then it's simple to
back the update out (as was done in this case). I maintain
24 hour availability so my clients get quick resolution of
any issues that DO crop up and there's only been 1 case in
7 years where one of my clients actually suffered down time
due to an issue and that was a virus that was
network-capable (they just wouldn't leave the blasted boxes
down until we cleared them).

I'm fortunate to deal primarily with small to medium sized
businesses, and that's a different world from the larger
organizations. Most of these business handle their own
basic IT needs, coming to me for the more difficult things
that require greater technical expertise.

Of course, it's also good to maintain a solid contract that
clearly outlines expectations and limitations on both
sides. :)

well, James, assuming you live in the U.S., the last time I
checked, the First Amendment gives citizens the right to be
stupid, and it gives you your livelihood rescuing them! <grin>

as to big vs small businesses, I know of no big ones who allow
Bill the Gates to swoop in on their
dozens/hundreds/thousands/tens of thousands of PCs and muck
things up. Updates are fully evaluated, tested, and released
across corporate networks. Or not.

--
ATM, aka Jerry

"Whether You Think You CAN Or CAN'T, You're Right." ? Henry
Ford
.



Relevant Pages

  • Re: Access 2010 with Sharepoint 2010
    ... Not real businesses, just individuals. ... if not all of the cloud based offerings from ... I'm not saying there aren't applications where it is a good ... clients that would benefit from moving their mainline applications ...
    (comp.databases.ms-access)
  • Re: slow logon
    ... in the logon time have been reduced so far. ... update the time for the clients that talk to the dc as the logon server. ... start up script in AD to apply updates to the clients machines which is ...
    (microsoft.public.windows.server.active_directory)
  • Re: Clients not updating with WSUS 3.0
    ... I was talking about the one you see on the taskbar on the client, which indicates that there are updates waiting to be installed. ... The one you see next to an update within WSUS, is an indicator that the update has to be 'approved' before it will be rolled out. ... Right click on the update and approved it and then it will be scheduled to be pushed out to the clients. ... sitting at the server, in Update Services console, looking at the computers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Swen annoyances to everyone: wakeup call
    ... the sarc.com site was not too clear about when updates should be ... - if using OE/O email clients, are the basic security settings locked down? ... > | many mail delivery failure messages can infect you. ...
    (microsoft.public.security)
  • Re: slow logon
    ... that i tell the software not to restart the services when new virus updates ... update the time for the clients that talk to the dc as the logon server. ... > We have a Start up script and a login script for users as well as> folder ...
    (microsoft.public.windows.server.active_directory)