Exchange 2010 Prerequisites

Below are the prep work need to be done before installation of exchange 2010.

CAS Server
1. install .NET 3.25
2. install Windows remote management
3. PowerShell V2
4. KB951725

ServerManagerCmd -i RSAT-ADDS

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

ServerManagerCmd -i Web-Dyn-Compression

ServerManagerCmd -i NET-HTTP-Activation

ServerManagerCmd -I RPC-over-HTTP-proxy

ServerManagerCmd -i Web-Digest-Auth


ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

IF the mailbox server be clustered

ServerManagerCmd -i Failover-Clustering


Planning and Designing Exchange 2010

One of the most frequent asked questions is defining storage configuration for Exchange 2010, what type of disk to go with and what type of RAID should be used. In reality most of these will depend upon your IT spending at the time when you plan or purchase this equipment.

If you are looking for advice or justification as what to purchase or perhaps doing design you might want to start reading links I am providing. Most of these generic questions have been answered in great details. Pay attention to “Best Practices” section the most (- :

Most of the best practices familiar but including DAG and redundancy less to worry if you go with redundant logs and databases.

Database size Supported up to 16 TB as best practice is less than 2 TB and provision 120% calculated maximum database size. In reality the major changes in ESE database and huge reduction on I/O requirements made Exchange more to give when it comes to databases. This is one of the primary reason Exchange even added “Archived database” out the box, since there is no longer I/O fear exist in a way in Exchange 2010 if you compare to previous versions. Still selecting fast disk should be preferred and give as much memory and CPU power to Exchange servers in reasonable measures and fallowing MS best practices as guidelines for each role and capacity.

Mailbox Storage Design Process
Understanding High Availability Factors
Understanding Storage Configuration
Understanding Exchange 2010 LUN Architecture
Exchange 2010 Mailbox Server Role Design Example

Top 10 Exchange Storage Myths

Here is another great article by MSExchange team touching base some of the mostly asked questions in Exchange 2010.

Simplifying and reducing the complexity of messaging environment while making it full redundant and faster is the most impressive part of Exchange 2010. You don’t need to deploy Exchange in complicated SAN.

Use DAS ( direct attached storage ) and simplify the operations of Exchange by taking dedicated SAN personal out the picture and have your Exchange administrators to have full responsibility and control.

As you can read more from bottom link most of these improvement are targeted to lower the cost, simplify the application deployment and operations while providing the best messaging experience.

Some of the highlights from this article

1. Exchange 2010 supports up to 100,000 items per folder,Remember Exchange 2007 supported up to 20.000 items per folder.
2. SIS is gone.Exchange 2010 does provide 20% database compression for HTML/Plain Text Messages
3. Simply the deployment, no more dedicated SAN person into Exchange deployment scenarios, simply use DAS to deploy exchange.
4. What is “backup less” Exchange ? With the ability to have multiple copies of each database, along with features such as single item recovery and lagged copy support, you might not need to use traditional backups


Exchange 2010 Large Mailbox Vision Whitepaper