Tip

Top 10 Microsoft Exchange performance worst practices

This tip originally appeared on SearchExchange.com, a sister site of SearchCIO-Midmarket.com.

With Exchange Server at the core of much of the world's corporate communications infrastructure today, achieving optimal messaging

    Requires Free Membership to View

system performance -- whether actual or perceived -- has become an important part of every Exchange administrator's job. Whatever the reason, if "email is slow," your help desk phones will start ringing, and if "email is down," your future at the company may be limited.

Taking a different approach to the challenge of Exchange Server performance, David Sengupta, longtime Exchange MVP and resident SearchExchange.com expert, outlines 10 worst practices you should avoid if you want your Exchange servers to perform at their best.


Top 10 Exchange performance worst practices

 Home: Introduction
 Worst Practice #1: Treat "high availability" as a future project
 Worst Practice #2: Leave "IOPS" for the consultant
 Worst Practice #3: Use identical configuration for all Exchange Server roles
 Worst Practice #4: Encourage users to keep everything in their Inboxes
 Worst Practice #5: Schedule backups and system maintenance during peak usage
 Worst Practice #6: Throttle the RAM available to Exchange
 Worst Practice #7: Virus scan and back up the M drive
 Worst Practice #8: Ignore client configuration, type and usage
 Worst Practice #9: Don't use change control
 Worst Practice #10: Ignore management tools

David Sengupta is a product manager in the Windows Management group at Quest Software. He has also been a Microsoft MVP in the Exchange Server category for six consecutive years. Sengupta has contributed to various Exchange and Windows books, magazines and white papers from a number of publishers. He also frequently represents Microsoft on staff at Ask the Experts, Microsoft Experts Area and Peer Talk at conferences such as MEC and TechEd. Sengupta has an M.T.S. from Tyndale Seminary, Canada, a B.Sc. from University of Ottawa, Canada, and MCSE (Messaging) and CCA certifications. He runs a blog on Microsoft Exchange and email compliance issues at http://p0stmaster.blogspot.com and can be reached at mailman@quest.com.


This was first published in June 2005

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.