[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] Making an SBS box shut down faster... - THE OFFICIAL BLOG OF THE SBS "DIVA"
Mon, Aug 14 2006 20:23 bradley

Making an SBS box shut down faster...

So Matt asked how to make his SBS box shut down faster and I said.....

Exchange.

Kill off Exchange. It's Exchange/AD that is the slow poke that makes you wait forever.

Build a batch file that stops anything and everything with the name "Exchange" in it or just the System Attendant.

net stop "Microsoft Exchange Information Store"  /y
net stop "Microsoft Exchange System Attendant" /y
net stop "Microsoft Exchange Routing Engine" /y
net stop "Microsoft Exchange Management" /y
net stop "Simple Mail Transfer Protocol (SMTP)" /y 

http://www.ultrabac.com/kb6/htm/UBQ000038.htm

How to Stop All Exchange Server 2003 Services on a Server:

(and thanks to Simon who reminded me I forgot the "/y" to ensure that the "Yes, stop the service" would be automatically done)

Filed under:

# re: Making an SBS box shut down faster...

Tuesday, August 15, 2006 1:41 AM by Simon Mitchell

Hi

A /y is required at the end of each net stop command so that you don't have to sit pressing keys, as it is expecting you to be interactive, as in "do you really want to do this".

You can also do the reverse by using net start. Useful for bouncing the services.

regards
Simon

# welcome to the funcave » killing exchange server…with one blow!

Tuesday, August 15, 2006 7:11 AM by welcome to the funcave » killing exchange server…with one blow!

PingBack from http://www.chrisrue.com/funcave/2006/08/killing-exchange-serverwith-one-blow.html

# re: Making an SBS box shut down faster...

Tuesday, August 15, 2006 8:35 AM by Ben Winzenz

You really only need to stop the System Attendant.  The problem here is that the NetLogon service stops before the System Attendant service does.  The System Attendant (specifically the DSAccess component I believe) has a large timeout value where it will continue to try to contact AD, after which it times out and will shut down.  If you stop just the System Attendant, it will stop any dependant services (Information Store and MTA Stacks).