4. Configuring Exchange Server 2013 for Maximum Performance and Reliability
After
decisions have been made about AD design, Exchange server placement,
and client access, optimization of the Exchange server itself helps
ensure efficiency, reliability, and security for the messaging platform.
Designing an Optimal Operating System Configuration for Exchange Server
As
previously mentioned, Exchange Server 2013 only operates on the Windows
Server 2008 R2 with SP1 or Windows Server 2012 operating systems. The
Standard Edition of Windows Server 2008 is sufficient for Exchange
servers when the server is not a member of a DAG.
Note
Contrary to popular misconception, the
Enterprise Edition of Exchange Server can be installed on the Standard
Edition of the operating system, and vice versa. Choose the version of
each based on the requirements.
Working with Multiple Exchange Server Databases
Exchange
Server 2013 database availability groups allow for multiple databases
to be installed across multiple servers and to have multiple versions
of those databases in more than one location. It also has the following
advantages:
• Reduce database restore time—Smaller
databases take less time to restore from tape, so it may make more
sense to deploy a larger quantity of smaller databases. This concept
can be helpful if there is a group of users who require quicker
recovery time (such as management). All mailboxes for this group might
then be placed in a separate database to provide quicker recovery time
in the event of a server or database failure.
• Provide for separate mailbox limit policies—Each
database can be configured with different mailbox storage limits. For
example, the standard user database could have a 200-MB limit on
mailboxes, and the management database could have a 500-MB limit.
• Mitigate risk by distributing user load—By
distributing user load across multiple databases, the risk of losing
all user mail connectivity is reduced. For example, if a single
database failed that contained all users, no one would be able to mail.
If those users were divided across three databases, however, only one
third of those users would be unable to mail in the event of a database
failure.
Monitoring Design Concepts with System Center Operations Manager 2012
The
enhancements to Exchange Server 2013 do not stop with the improvements
to the product itself. New functionality has been added to the Exchange
Management Pack for System Center Operations Manager that enables
OpsMgr to monitor Exchange servers for critical events and performance
data. The OpsMgr Management Pack is preconfigured to monitor for
Exchange Server–specific information and to enable administrators to
proactively monitor Exchange servers.
5. Securing and Maintaining an Exchange Server 2013 Implementation
One
of the greatest advantages of Exchange Server 2013 is its emphasis on
security. Along with Windows Server, Exchange Server 2013 was developed
during and after the Microsoft Trustworthy Computing initiative, which
effectively put a greater emphasis on security over
new features in the products. In Exchange Server 2013, this means that
the OS and the application were designed with services “Secure by
Default.”
With Secure by Default, all
nonessential functionality in Exchange Server must be turned on if
needed. This is a complete change from earlier Microsoft practice,
which had all services, add-ons, and options turned on and running at
all times, presenting much larger security vulnerabilities than was
necessary. Designing security effectively becomes much easier in
Exchange Server 2013 because it now becomes necessary only to identify
components to turn on, as opposed to identifying everything that needs
to be turned off.
Patching the Operating System Using Windows Software Update Services
Although
Windows Server presents a much smaller target for hackers, viruses, and
exploits by virtue of the Secure by Default concept, it is still
important to keep the OS up to date against critical security patches
and updates. Currently, two approaches can be used to automate the
installation of server patches. The first method involves configuring
the Windows Server Automatic Updates client to download patches from
Microsoft and install them on a schedule. The second option is to set
up an internal server to coordinate patch distribution and management.
The solution that Microsoft supplies for this functionality is known as
Windows Software Update Services (WSUS).
WSUS
enables a centralized server to hold copies of OS patches for
distribution to clients on a preset schedule. WSUS can be used to
automate the distribution of patches to Exchange Server 2013 servers,
so that the OS components will remain secure between service packs.
WSUS might not be necessary in smaller environments, but can be
considered in medium-sized to large organizations that want greater
control over their patch management strategy.
Summary
Exchange
Server 2013 offers a broad range of functionality and improvements to
messaging and is well suited for organizations of any size. With proper
thought for the major design topics, a robust and reliable Exchange
Server email solution can be put into place that will perfectly
complement the needs of any organization.
When
Exchange Server design concepts have been fully understood, the task of
designing the Exchange Server 2013 infrastructure can take place.
Best Practices
The following are best practices from this article:
•
Use DAGs to distribute multiple copies of all mailboxes to multiple
locations, taking advantage of high availability and disaster recovery
capabilities that are built in to Exchange Server 2013.
• Separate the Exchange Server log and database files onto separate physical volumes.
•
Plan for a Windows Server 2003 forest functional level and at least one
Windows Server 2003 SP2 or later domain controller in each site that
will run Exchange Server.
• Integrate a backup strategy into Exchange Server design.
• Install at least two global catalog servers in the same site as any Exchange server.
•
Keep the OS and Exchange Server up to date through service packs and
software patches, either manually or via Windows Software Update
Services.
• Keep the AD DS 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 2013 technology.
• Monitor DNS functionality closely in the environment on the AD DS domain controllers.
