Re: Dear Microsoft... Rebooting servers id NOT security..

From: Karl Levinson, mvp (levinson_k_at_despammed.com)
Date: 05/28/05

  • Next message: Karl Levinson, mvp: "Re: Should users be local admins?"
    Date: Sat, 28 May 2005 09:30:12 -0400
    
    

    Microsoft claims that with Windows 2003, far fewer patches require reboots.
    Their number was around 80% fewer, I think. I haven't checked to confirm
    this. Additionally, many patches that are critical for other OSes are not
    critical for Windows 2003, as the vulnerabilities are mitigated by default
    settings. If the patch isn't critical, you may be able to wait a month or
    several to install it, depending on the details.

    Microsoft is also working on hot patching technology to replace running
    executables without rebooting. However, if you have to patch your web
    server software, you're probably going to have to cause some sort of
    downtime by stopping the web server service, whether you're talking Windows
    or *nix. Having said all that, I'm sure it is frustrating if a patch for
    something unrelated like RPC / DCOM forces you to reboot and lose your
    unrelated web services, and many Microsoft customers have always hated that
    MS forces you to install IE and Outlook on Windows servers and force you to
    install patches nearly monthly. I think they may finally be listening to
    the customers and fixing this as well, I don't know.

    Most people that can't tolerate 5 minutes of downtime during a reboot 1) use
    clustered servers for fault tolerance, because 2) they can't tolerate even
    30 seconds of downtime that would be caused by stopping the web service on
    Windows or *nix. There are large well known commercial web sites that run
    in large Windows clusters in data centers.

    "Duse" <dude@soft.com> wrote in message
    news:Oyxg33XXFHA.2684@TK2MSFTNGP09.phx.gbl...
    > The recent rend for critical patches for win 2003 to require rebooting the
    > server is USELESS!!!
    >
    > Win 2003 is a SEVER, it cannot be continually rebooted and offer any
    Server
    > level to its users.
    >
    > Additionally the fact that only a partial installation occures ( which
    > leaves the server in a unstable state) is also USELESS...
    >
    > FYI: server are NOT workstations and do not have people sitting at them to
    > monitor and react to your auto updates and installs..
    >
    > Is this truely what you think improving security is....
    >
    > Unhappy..
    >
    >
    >


  • Next message: Karl Levinson, mvp: "Re: Should users be local admins?"

    Relevant Pages

    • Re: Dear Microsoft... Rebooting servers id NOT security..
      ... > whole idea of installing patches in the first place. ... > I operate a server for a small company, run the updates, etc. ... > very knowledgable about computers & most Windows versions in general. ...
      (microsoft.public.windows.server.security)
    • Re: DST Updates - fun, fun
      ... Most XP machines received the daylight savingtimeupdate ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ... All patches applied. ...
      (microsoft.public.windowsxp.general)
    • Re: Question about a Windows 2003 server with service problems after applying latest patches
      ... I don't think uninstalling the patches would ... > Windows Update and rebooted the server. ... > several messages about corrupt registry hives that windows would attempt ... > rebooting multiple times but I get the same problems each time. ...
      (microsoft.public.windows.server.general)
    • Windows 2000 (Pro and Server) having services.exe error and rebooting
      ... I'd say probably a quarter of our Windows ... following error and rebooting: ... Window Title: System Shutdown ... and this KB does not refer to 2K Pro, only Server. ...
      (microsoft.public.win2000.general)
    • Re: DST Updates - fun, fun
      ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ... All patches applied. ...
      (microsoft.public.windowsxp.general)