This chapter is from the book
The following are best practices from this chapter:
- Use Database Availability Groups (DAGs) to distribute multiple copies of all mailboxes to multiple locations, taking advantage of HA and DR capabilities that are built into Exchange Server 2010.
- Separate the Exchange Server log and database files onto separate physical volumes whenever possible, but also be cognizant of the fact that Exchange Server can be installed on slower, cheaper disks when using DAGs.
- Plan for a Windows Server 2003 functional forest and at least one Windows Server 2003 SP2 or Windows Server 2008 domain controller in each site that will run Exchange Server.
- Integrate an antivirus and backup strategy into Exchange Server design.
- Keep a local copy of a full global catalog close to any Exchange servers.
- Keep the OS and Exchange Server up to date through service packs and software patches, either manually or via Windows Server Update Services.
- Keep the AD design simple, with a single forest and single domain, unless a specific need exists to create more complexity.
- Identify the client access methods that will be supported and match them with the appropriate Exchange Server 2010 technology.
- Monitor DNS functionality closely in the environment on the AD domain controllers.