Re: Me Too

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

From: Steve Foster [SBS MVP] (steve.foster_at_picamar.co.uk)
Date: 03/29/04 

Date: Sun, 28 Mar 2004 17:42:21 -0800

Jeff Middleton [SBS-MVP] wrote:

> Leave it to Steve to take the conversation to a technicality with
> modest, but measurable importance.
>
> FWIW, I did my testing of the script (while writing it) on my own XP
> workstation....not testing the effect of the reg change, just the
> script execution.
>
> I've done a quick survey of workstations and servers nearby:
>
> My SBS 2000 shows this key to be 600000.
> My W2K workstation shows 20000
> My XP workstation shows 20000

Interesting, my SBS2000 has 20000.

20000 allows for each service to do graceful shutdown in 20s or less.
Which could be tight on a server like SBS (though mine has never shown
any problems).

120000 equates to 2 minutes, which seems like an awfully long time for
any service to take for a normal shutdown.

>
> This compared to the 120000 we are setting the SBS 2003.
>
> Those are values I take to be milliseconds to shutdown delay.
>
> Therefore, this reg edit change made to a workstation would
> potentially mean that if a service/process is unresponsive to a
> shutdown request, the delay would be longer than normal for a
> workstation than normal before the system interupts the process to
> kill it.
>
> You could use the numbers above to correct settings on your machine
> if you ran the script on a local machine.
>
> My original point was that no critical harm is likely to be created
> if this key was changed. I'm betting it's not often used in
> workstations cause it isn't often needed to kill a service.
>

I'm thinking that high values for this key could explain interminably
long shutdown times for SBS servers. If a number of services have
locked or crashed or whatever, the OS will allow each one
WaitToKillServiceTimeout ms before unceremoniously killing that service. 

-- 
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Relevant Pages

  • Re: Me Too
    ... >> script execution. ... >> Those are values I take to be milliseconds to shutdown delay. ... >> workstation than normal before the system interupts the process to ... >> if you ran the script on a local machine. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 R2 Shutdown Problem
    ... It has on every SBS network I've run across so far that's had the problem. ... Did not previously have any shutdown problems ... > What is Trend? ... >>> similar script for Trend as I have done for Exchange. ...
    (microsoft.public.windows.server.sbs)
  • Re: Finetuning: Remote Shutdown with WMI, some errors occur.
    ... Joris van der Struijk wrote: ... Also we would like that a workstation that's locked is also shutdown by this ... could then call that from your script instead of the Win32Shutdown ...
    (microsoft.public.windows.server.scripting)
  • Re: Default SBS_LOGON_SCRIPT.BAT
    ... The script checks to see whether there are applications waiting to be ... installed on the workstation. ... Les Connor [SBS Community Member - SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: GPO Shutdown Scripts
    ... Checked the workstation registry and it references the script on the ... shutdown command using shutdown.exe from the 2000 Resource kit as it ...
    (microsoft.public.windows.group_policy)