Web Abstract:
- Microsoft Exchange 2007 requires a server with a 64-bit processor and a 64-bit Windows operating system (OS).
- Microsoft Exchange Server 2007 must run on Windows Server 2003 x64 operating system (OS) or on Windows 2003 R2 x64 OS.
- Microsoft Exchange Server 2007 deployment requires your network to contain an Active Directory (AD) forest and have a DNS server.
- Memory requirements for Exchange Server 2007 are calculated according to the roles the server hosts and the number of processor cores installed.
|
Any time a major new version of an application is released, you might be tempted
to deploy it immediately. With Microsoft Exchange Server 2007, though, a quick
deployment isn't always an option. Exchange 2007's architecture is vastly different
from Exchange Server 2003's. As such, it's critically important that you verify
that your organization meets the Exchange 2007 infrastructure requirements before
deploying the software. Here are the basics you'll need to have in place to
ensure a smooth migration.
Picking Your Processor
Exchange 2007's hardware requirements are considerably different from those
of Exchange 2003. The biggest difference is that Exchange 2007 requires a server
with a 64-bit processor and a 64-bit Windows OS. Exchange 2003 is capable of
running on 64-bit hardware, but only if the server is running a 32-bit version
of Windows. Therefore, an in-place upgrade to Exchange 2007 is impossible. If
your organization is currently running Exchange 2003, you'll have to perform
a migration rather than an upgrade.
As you select server hardware, keep in mind that not all
64-bit processors will meet Exchange 2007's requirements.
Exchange 2007 supports AMD64 and Intel Extended Memory 64 Technology (EM64T) processors. Intel's Itanium processors aren't supported, however. Microsoft implemented
the 64-bit processor requirement as a way of removing the
memory constraints associated with 32-bit OSs, which are
capable of addressing a maximum of 4GB of RAM (Physical
Address Extensions—PAEs—aside). Windows divides this
address space in half, dedicating 2GB to kernel processes
and 2GB to user processes.
Exchange servers with large numbers of mailboxes or large databases commonly
experience performance problems because of insufficient memory. One way around
this problem is to use the /3GB switch in the boot.ini file to allocate 3GB
of memory to user processes and leave the remaining 1GB for kernel processes.
However, this solution can sometimes leave the OS short of page-table entries,
and even 3GB isn't a large enough address space for some Exchange servers to
function optimally.
In contrast, a 64-bit processor running a
64-bit OS is capable of addressing up to 16TB of
memory address space. Exchange 2007 doesn't
have to work within the 4GB address space
constraint. Granted, few servers today can be
equipped with 16TB of memory.
Having a larger address space enhances
Exchange 2007's performance, but it also lets
it comfortably handle larger databases than
Exchange 2003 can. Of course, there's no such
thing as a truly unlimited database; hardware
considerations will always limit their practical
size. The time required to perform backups
might also be a limiting factor, though time will
soon be less of a consideration because Microsoft System Center Data Protection Manager
(DPM) 2.0 will support real-time backups for
Exchange. Some companies are using the ability to maintain larger databases to consolidate
multiple mailbox and public folder servers
onto a single Exchange 2007 server.
Not all processors will perform equally
well in all Exchange 2007 deployments. As you
probably know, one of Exchange 2007's major
architectural changes is that it's now rolebased. An Exchange server can be classified as
a Mailbox server, an Edge Transport server, a
Hub Transport server, a Client Access server, or
a Unified Messaging (UM) server. A server can
also host multiple roles, but for optimal performance and security you should limit each
server to hosting a single role when possible.
Microsoft recommends basing your processor selection on the role(s) that the
server will host. Although Microsoft offers no specific recommendations about
processor speed, it does provide recommendations about the number of processor
cores you should use in various deployment scenarios. Table
1 shows Microsoft's recommended minimum, normal, and maximum number of processor
cores for each Exchange 2007 server role. (The tables in this article are adapted
from Microsoft's Exchange Server 2007 Processor and Memory Recommendations Web
page at http://www.microsoft.com/exchange/hardwareplanning.)
At the time this article was written, the maximum number of cores available
on a single processor was four, and most processors include only two cores.
As such, deployment scenarios in which Microsoft recommends higher numbers of
cores would require the use of multiprocessor servers running multicore processors.
Options for Your OS
Choosing an OS for your Exchange 2007 server isn't nearly as complicated as
choosing the server's processors. In fact, there are really only two choices:
You can use either Windows Server 2003 x64 or Windows 2003 R2 x64; the Standard
and Enterprise Editions of both OSs are acceptable. Exchange 2007 won't initially
work with Longhorn Server; however Exchange 2007 SP1, which is due to be released
this fall, will add Longhorn Server support as well as introducing new capabilities
to the Exchange Management Console.
Although Exchange 2007 itself requires a
64-bit OS, the Exchange 2007 management
tools can be deployed to 32-bit systems running Windows 2003 SP1 or later, Windows
2003 R2 or later, or Windows XP SP2 or later.
Microsoft's official documentation currently
doesn't list Windows Vista as being supported
for any part of Exchange 2007 deployment.
Designing Your Network
It's easy to consider the hardware and OS requirements for the server that will
run Exchange 2007 and forget about requirements for the network that the Exchange
2007 server is on. However, it's essential that you take the rest of the network
into account. For the most part, network-related deployment concerns are beyond
the scope of this article, but you won't even be able to install Exchange 2007
unless your network conforms to some minimum requirements.
First, your network must contain an Active Directory (AD) forest and a DNS
server, and your Exchange server must be a member of an AD domain with a domain
functional level of Windows 2000 Server native or higher. To determine your
domain's functional level, open the Microsoft Management Console (MMC) Active
Directory Domains and Trusts snap-in. In the console, right-click the domain
in question and select Properties from the shortcut menu. The resulting screen
should display the domain's functional level and let you raise the functional
level if necessary.
Previous
Register
