Plan for Exchange Server 2010
Planning is probably the most important stage of Exchange organization. By understanding Exchange 2010 technologies prior to deploying allows us to avoid technical limitations. I will start by briefly describing technologies new to Exchange 2010.
Client Access Server (CAS) – single point of entry
All clients (Outlook, OWA, mobile device, etc.) now connect to Client Access Server (CAS) directly. Client Access server redirects clients to proper mailbox server. This allows mailbox database portability and faster convergence in disaster recovery scenarios.
Database Availability Groups – new DR technology (replaced CCR,LCR and SCR)
Database Availability Groups (DAG) allows replication of mailbox database to DR server. This feature and new CAS single point of entry design allows Exchange to be highly available.
OS required: Server 2008 x64 or Server 2008 R2 x64
Third-Party software support
It’s import to ensure 3rd party software you are planning to use supports Exchange 2010. This includes Antivirus software, Spam filtering software, Backup software, Fax, etc.
Active Directory domain requirements
1. Domain function level: Windows Server 2003
2. At least one Server 2003 SP2 or higher domain controller within AD site
3. One Global catalog server per AD site (note: Exchange 2010 needs full GCs, not read-only)
Disk requirements
By segregating the disk as described below, it allows for maximum performance.
Volume1: OS
Volume2: Exchange Logs
Volume3: Exchange Database
Mailbox server role
Main concern when planning for Mailbox server role is whether to choose Standard version or Enterprise. Standard version only allow up to 5 mailbox databases while Enterprise allows up to 50. Most organization would want to go with the Enterprise version
Client Access Server role
To Plan for this role, you need to know what clients will be connecting to Exchange. If you want to support IMAP and POP3, you will need to enable these manually after the installation. They are not turned on by default. Also, you may need to configure both POP and IMAP for plain text authentication. To allow ActiveSync access, you need to port forward 443 from your external IP to CAS.
Hub Transport server role
This role acts as a central mail hub server for an AD site. Email between different AD sites must go through hub server and that’ where the decision is made. You want to plan for at least two Hub Transport role within an AD site.
Note that, you must have each of these roles in every Active Directory site.
Remote access technologies
ActiveSync
Activesync is enabled by default and used to connect remote AS devices.
Outlook Anywere
This feature allows Outlook to access Exchange without VPN remotely. This feature can be enabled on CAS Server.
Administration with Exchange 2010 Management Shell
Exchange 2010 Management Shell is based on Powershell V2. This means, it has all the basic functionality of Powershell V2 plus Exchange extensions. Powershell V2 also allows remote access so remote administration of Exchange 2010 is possible. The shell is priceless for large enterprises as It can easily create over 10,000 user accounts with simple script. It also make bulk changes a lot easier. Every GUI task performed runs Exchange Management Shell in the background. Every task that can be performed in GUI can be performed from the shell.
Exchange Server 2010 DR features
This version of Exchange includes more robust disaster recovery features compare to previous versions. Microsoft introduced a new continuous backup technology that allows Exchange to host up to 16 mailbox copies. Note that previous versions of Exchange only had one copy of the mailbox. Microsoft eliminated SCC(single copy clusters), LCR(Local Continuous Replication) and CCR which were DR technologies included with Exchange Server 2007. Exchange 2010 Introduces Database Availability Group replication technology, which is very similar to Exchange 2007 CCR.
------------------------------------------------------------------------------------------
Exchange 2010 requirements
Hardware:
Processor:
X64 architecture-based computer with Intel Processor that supports Intel EM64T
AMD processor that supports AMD64 platform
Note—Intel Itanium IA64 processors are NOT supported.
Exchange 2010 Memory requirements
As always, memory is something you don’t want to skimp on. Personally, I am running 16gb of ram on 500 mailboxes. But below is the recommendation. Use below formula / calculator to determine your memory requirement.
2GB + 5MB*(number of mailboxes) = Memory requirement
For example: Server that will host 500 mailboxes will need at least 4.5GB of ram. Remember, these are minimal requirements.
OS: Server 2008 x64 or Server 2008 R2 x64
Software:
Microsoft .NET Framework 3.5
Windows Remote Management 2.0
Windows Powershell V2
Microsoft Management Console 3.0
Internet Information Services (IIS) 7.0
Exchange 2010 Active Directory domain requirements
1. Domain function level: Windows Server 2003
2. At least one Server 2003 SP2 or higher domain controller within AD site
3. One Global catalog server per AD site (note: Exchange 2010 needs full GCs, not read-only)