Exchange Server 2003 Services Shutdown 3

[SpanishWaiter01]

Dear All,

I am new to Exchange 2003 and would like the benefit of your help.

What would be the best way to shut-down gracefully and Exchange server hosting only Public Folders?

Taking a look at the following book:

Microsoft Exchange Server 2003 24seven

Microsoft Exchange Server 2003 24seven by Jim McBee, Barry Gerber, and Sybex (Paperback - May 14, 2004)

There is a page in the first chapter which lists out the key Exchange Services and there dependencies, which are started when the program is launched and running.

Some of these services mentioned are not installed or are disabled on the particular server.

So, what I did, I stopped each service in reverse order they were printed in the book and stopped the System Attendant Service lastly. All went fine.

Am I being cautious/careless or would a simple shutdown and power off from the ctrl alt del panel would be enough?

Constructive comment are welcomed.

Cheers,
Spanish Waiter

 

[southbeach]

Like you, not an expert but ... helping others I figure I can find myself in a position to learn as well.

I do not thing that what you've done is wrong. In fact, I normally try same in lieu of shutting down the entire server or reboot.

If re-starting services does not get things moving, I then reboot but only as a last resource. I have found that as an Exchange Admin (not that I am one but said responsibility has been placed upon me), one must review Even Logs and Services to make sure things are running smoothly.

I would recommend looking into "Best Practices ..."; this tool points out areas where your attention may be needed.

Good luck!

 

[58sniper]

net stop MSExchangeES /y
net stop MSExchangeIS /y
net stop MSExchangeMTA /y
net stop MSExchangeSA /y
net stop WinHttpAutoProxySvc /y

Is generally what I use for stopping services on a 2003 box.

Pat Richard MVP

 

[xmsre]

If all your dependencies are set correctly, then shutting down the SA should suffice. It never hurts to be cautious though; You certainly are not hurting anything by shotting them down in reverse order. You could make the arguement that the services go down faster because you don't have to wait for dependency timeouts. The cost is a bit of administative overhead (WORK) on your part. If you can live with that, I'd keep doing what you're doing.

XMSRE

 

[xmsre]

If all your dependencies are set correctly, then shutting down the SA should suffice. It never hurts to be cautious though; You certainly are not hurting anything by shutting them down in reverse order. You could make the arguement that the services go down faster because you don't have to wait for dependency timeouts. The cost is a bit of administative overhead (WORK) on your part. If you can live with that, I'd keep doing what you're doing.

XMSRE