Deployment Flexibility in Microsoft Exchange

Maximize uptime. Minimize coming in on weekends.

Install Silverlight

Whether deploying on-premises, in the cloud, or in a combination of the two, Exchange 2010 helps reduce costs and provides tools to simplify the deployment experience. Exchange 2010 allows you to:

  • Drive down the cost of storage by offering additional storage architecture choices in on-premises deployments
  • Use hardware virtualization to consolidate multiple under-utilized physical servers in on-premises deployments
  • Simplify deployment with custom instructions for installing or upgrading to Exchange 2010
  • Perform migrations during normal business hours without taking users offline

Key features

Administrators can move mailboxes between databases without taking users offline. Users can connect to their mailboxes and send and receive mail while the move is taking place. This reduces user downtime and lets administrators perform system maintenance during business hours, instead of nights and weekends.
With Microsoft Outlook 2007 or greater, Exchange 2010 supports automatic configuration of Outlook mail profiles. Users do not need to know the name of their mail server to set up an email profile. In fact, users who are connected to the corporate network do not need to enter any information—their domain credentials are used to create a complete mail profile automatically. Users connecting remotely using Outlook Anywhere (formerly known as “RPC over HTTP”) need only provide their user name, email address and password.
Embedded in the Exchange 2010 setup process and available through the Exchange Management Console toolbox, the Exchange Best Practices Analyzer proactively examines an Exchange organization for problems and discrepancies that could lead to service outages or reliability problems. Performing more than 2,000 distinct checks and automatically updating via XML, the Analyzer delivers warnings and error messages to the administrator along with information on how to address these problems. When prerequisites change, the Analyzer surfaces these changes to support a smooth installation. The Exchange Best Practices Analyzer has also been updated with readiness checks that can be run against current Exchange Server 2003 or Exchange Server 2007 environments to help prepare for migration to Exchange 2010.
ExRCA is a web-based troubleshooting and diagnostic tool intended to identify the point of failure for Internet-based Exchange Server client connectivity scenarios. It simulates the activities a client must be able to perform to connect and then isolates the exact point of failure. In many cases, ExRCA can point out known configuration issues and provide suggested steps for resolution. The connectivity testing across the Internet (from outside your organization) is performed by a website hosted in a Microsoft datacenter.
The Exchange Deployment Assistant is a Web-based resource which helps organizations, generate custom instructions for installing or upgrading to Exchange 2010. This tool is useful for organizations deploying a new installation of Exchange 2010 as well as those upgrading from Exchange 2003 or Exchange 2007.
Exchange 2010 uses the role-based architecture introduced with Exchange 2007. Server roles organize Exchange 2010 services and features into preset server configurations. Dividing Exchange features among server roles has several advantages.
Using the Microsoft Federation Gateway, Exchange 2010 allows organizations to work with external partners in a convenient and secure environment. These flexible cross-premises scenarios support federated message delivery, calendar sharing, and much more.
For a small or medium-sized company with a limited number of mailboxes, an administrator can install all required roles on one physical server. For a large enterprise with tens of thousands of mailboxes, an administrator can deploy each role on a separate server or multiple servers per role to provide better performance and fault tolerance.
Each server role only installs the binaries and services necessary to perform a specific feature set. Configuring a server with only one or two roles reduces memory, computer processing unit (CPU) and disk space requirements for the server. It also reduces the server’s attack surface.
Upgrades, patches, hot fixes and other server changes that could cause server outage can be isolated to one server role. This reduces maintenance downtime and impact to users. Administrators can install or uninstall roles on a server at any time.
Preset server configurations make installation easier by allowing the mail server to perform role-specific configuration tasks.
32-bit email servers are limited to 4 gigabytes (GB) of memory per instance of an application, restricting the ability to cost-effectively meet growing demands. Exchange 2010 is built on 64-bit architecture, expanding addressable memory to 16 exabytes (EB) (16 billion GB) improving performance and capacity significantly.

The larger memory cache available on 64-bit systems reduces disk drive IO requirements significantly. By reducing IO, Exchange 2010 makes better use of existing storage systems and gives administrators the option of using low-cost storage systems such as Direct Attached Storage (DAS) and desktop-class storage, even in demanding enterprise environments.
Exchange 2010 delivers up to a 70 percent reduction in disk IO over Exchange 2007 and a 90 percent reduction in disk IO over Exchange 2003. This means that more disks meet the minimum performance required to run Exchange, driving down your storage costs. In addition, IO patterns are optimized so that disk writes are less “bursty” and more suitable for SATA disks.
Exchange 2010 adds new options to the menu of Exchange storage choices, including the (SATA) hard-disk drives as well as configurations that can eliminate the need for RAID configurations. Whether you choose Storage Area Network (SAN), DAS, or JBOD configurations, Exchange 2010 can provide users with larger mailboxes at a lower cost without sacrificing system availability.
Using the Microsoft Federation Gateway, Exchange 2010 allows organizations to work with external partners in a convenient and secure environment. These flexible cross-premises scenarios support federated message delivery, calendar sharing, and much more.

Why Microsoft?

Deploy on-premises, in the cloud, or both

Deploy on-premises, in the cloud, or both

Lower IT costs with flexible storage architecture and server consolidation

Lower IT costs with flexible storage architecture and server consolidation

Minimize downtime with Online Move Mailbox

Minimize downtime with Online Move Mailbox

For more reasons why click here
For more reasons why click here

Next Steps

Product Details
Downloads
Contact Us

Related Sites