Rebooting the Exchange Server
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
The Exchange Server is in most cases a robust system. There are times, however, when you may encounter periodic problems with Exchange, including, but not limited to:
Users are not able to send or receive mail.
A user checks for members of the distribution list and the workstation locks up.
The network administrator checks the event-viewer logs and finds that there is a problem with the Directory Service.
CPU usage may continuously stay at 100%.
When you encounter any of these situations, your first response might be to perform Exchange maintenance on the database that you think is the problem. However a simple reboot can resolve many problems. How often should the Exchange server be rebooted? Rebooting should take place at least once every two months. The following is the procedure to follow when preparing to reboot the Exchange Server:
- Double Click on the Services Icon located in Control Panel.
- Locate Microsoft Exchange System Attendant.
- Click Stop. Then Click OK
- When ALL Services are stopped click Close.
- The Exchange Server can now be restarted.
Note: Services such as the Information Store make require a longer period to stop if the database is large. An Information Store database size of 2GB may take approximately 10 minutes to stop.
Adesh Rampat has 10 years experience with network and IT administration. He is a member of the Association of Internet Professionals, the Institute for Network Professionals and the International Webmasters Association. He has also lectured extensively on a variety of topics.
Did you like this tip? If so, (or if not) why not let us know. Send an email to us and sound off.
Administering Exchange 2000 Server
Author : Mitch Tulloch
Publisher : Osborne
Published : Feb 2001
Timed to follow release of Exchange 2000 Server, this book complements our Exchange 2000 Server: The Complete Reference and gives administrators task-based coverage of this messaging platform. Covers all new features of this new product and addresses complexities introduced by Windows 2000--a must-have for administrators.