Exchange Tip: Exchange 2003 Quick Tweaks
You've just finished your brand-new Exchange Server 2003 installation. What should you do next? Exchange 2003 is pretty much self-tuning, but you can improve or optimize your environment.
Install Exchange 2003 Service Pack 1 (SP1—http://www.microsoft.com/exchange/downloads/2003/sp1. mspx) and the latest patches or SP2 (http://www.microsoft.com/exch ange/downloads/2003/sp2/overview. mspx). Both packs add improvements and bug fixes. Two of the most important improvements in SP1 are bit-flip auto-correction (http://support.micro soft.com/?kbid=867626) and an easier setup of remote procedure call (RPC) over HTTP or HTTP Secure (HTTPS).
Configure backups. I keep finding people who have no backup of their Exchange infrastructure. Make sure you have at least one weekly full online backup and daily incremental backups. I like Windows Backup, since it has never failed me. I usually advise my customers to use NTBackup in order to back up Exchange to disk, and later use a third-party solution to move those files to tape. You should definitely check out the Microsoft article "How to Back Up and Restore an Exchange Computer by Using the Windows Backup Program"(http:// support.microsoft.com/?kbid=258243).
Move the databases and logs to the definitive location. If you planned your Exchange deployment correctly, you should have configured separate disk volumes for the different Exchange components. At least you should have your database files on a RAID 0+1 array (RAID 5 is acceptable for smaller deployments) and the database log files on a RAID 1 array. If you haven't done that, it's never too late. Read "Optimizing Storage for Exchange Server 2003" (http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/optimizestorage.mspx).
Install Exchange antivirus software. Nowadays most viruses spread themselves by using email, so you really need some antivirus at your server. Don't use file-level scanners (see "Overview of Exchange Server 2003 and antivirus software" at http://support.microsoft.com/?kbid= 823166), and use a specific software designed for Exchange (see http://www.microsoft.com/exchange/partners/antivirus.asp).
Start planning your antispam strategy (if haven't already done so). In today's messaging reality, it's impossible not to have some kind of spamfighting tool. You can use Microsoft Exchange Intelligent Message Filter (IMF—http://www.microsoft.com/exchange/downloads/2003/imf/default.mspx) or a third-party tool (http://www.microsoft.com/exchange/partners/emailcontent.asp).
Create system policies for your stores and servers, even if you have just one of each. These policies will become useful once you start expanding your environment. Some of the settings you might want to configure are Retention Policy and Mailbox Limits.
Install Microsoft Exchange Server Best Practices Analyzer (ExBPA— http://www.exbpa.com) on a separate computer (preferably) and run it against your Exchange server. This tool will give you valuable suggestions, such as memory optimization and performance tuning.
Install (and use) monitoring software. It doesn't have to be Microsoft Operations Manager (MOM); you can use something simpler, such as Woodstone Servers Alive (http://www.woodstone.nu/salive) or Quest Software's Big Brother (http://www.bb4.org).
Implement your Sender Policy Framework (SPF) record so that you can use Sender ID technology (http:// www.microsoft.com/senderid). There are two useful wizards available online that will help you with that task; you can find them at http://spf.pobox.com/wizard.html and http://www.anti-spamtools.org/senderidemailpolicytool/default.aspx.
Start reading some Exchange blogs. You Had Me At EHLO (http://blogs.technet.com/exchange) is indispensable. There some other sites dedicated to Exchange that are worth reading, such as http://www.msd2d.com and http://www.msexchange.org. —Rui J.M. Silva, ParaRede
Exchange 2003 SP2 Provides Lots of Treats
Exchange Server 2003 Service Pack 2 (SP2) made its debut in late October. Look for upcoming articles about the pack's new mobility features, Sender ID framework, migration tips, and more. —Lisa Pere
Prev. page
[1]
