Our Team consists of Highly Qualified Professionals Services

Exchange Server Deployment

Microsoft reached the RTM (Release To Manufacturing) milestone for Exchange Server 2010 on October 8, 2009, and it was officially launched on November 9, 2009.[18] A 120 day trial which is downloadable from Microsoft.[17] Exchange Server 2010 is available in two server editions; Standard edition and Enterprise edition.

Major changes from previous versions of Exchange Server include:

The high availability options for Mailbox Databases (SCC: Single Copy Clustering, CCR: Clustered Continuous Replication and LCR: Local Continuous Replication) and site resiliency functionality (SCR: Standby Continuous Replication) have been replaced by Database Availability Groups (DAGs) in Exchange Server 2010. Major DAG benefits include providing database level high availability (as opposed to server level), support for up to sixteen (16) copies of each database, and flexible configuration (databases copies may be added / removed at will without requiring major server reconfiguration). Each server that runs the Enterprise edition of Exchange Server 2010 can host up to 100 database copies.

High availability for the Client Access Server role in Exchange Server 2010 is provided by using Client Access Server (CAS) arrays. A CAS array can contain multiple Client Access Servers in an Active Directory site and provide a single name endpoint for client connections. CAS arrays cannot span multiple Active Directory sites.

In Exchange Server 2007, a clustered mailbox server could not be combined with any other roles. In Exchange Server 2010, the Mailbox Server Role may be combined with the Client Access Server and/or Hub Transport roles, regardless of whether or not the mailbox server participates in a Database Availability Group. (However, since Database Availability Groups use Windows Failover Clustering, and Microsoft does not support the combination of Windows Failover Clustering and Windows Network Load Balancing on the same server, a multi-role deployment will require the use of a 3rd party load balancer to provide load balancing and fault tolerance for the Client Access Server role).

With the introduction of the RPC Client Access service, all Outlook clients access their mailbox database through the Client Access Server role. This abstraction layer allows for improved load balancing and redundancy and minimal client impact in the event of a database level *-over ("switchover" or "failover") event.

Exchange Server 2010 provides cost savings in required hardware. Storage performance requirements (measured in IOPS: Input/Output operations Per Second) have been reduced by approximately 70% over Exchange Server 2007, and by approximately 90% over Exchange Server 2003. According to a case study, Microsoft IT was able to reduce hardware costs by 75% during the migration from Exchange Server 2007 to Exchange Server 2010.

Exchange Server 2010 extends the large mailbox support introduced in Exchange Server 2007, and also introduces a Personal Archive feature to allow messages to be retained longer without the need for a 3rd party archival system. The Personal Archive is implemented as a secondary mailbox for archive-enabled users, and in Exchange Server 2010 Service Pack 1, the Personal Archive may be located on a different database than the primary mailbox, which may reside on a different disk if desired.

The compliance and legal search features have been enhanced. What was formerly known as the "Dumpster" in previous versions of Exchange (a special storage area for messages which have been deleted from the Deleted Items folder or "permanently deleted" from a regular folder, such as the Inbox) has been evolved into the Recoverable Items folder in Exchange Server 2010. If configured appropriately, the Recoverable Items folder allows for a "tamper proof" storage area (users cannot circumvent the Recoverable Items folder to bypass legal discovery), which also provides a revision history of any modified items.

Administration delegation can now be performed at a granular level due to Exchange Server 2010's implementation of Role Based Access Control (RBAC). Users and administrators can be given extremely fine grained abilities for functions provided both within the Exchange Management Console or Exchange Management Shell and in Outlook Web App. For example, a compliance officer may be given the ability to perform cross mailbox discovery searches within Outlook Web App; a help desk technician may be granted the ability to set an Out Of Office message for other employees within the company, or a branch administrator in a remote office may be granted the permission to perform specific Exchange Management Shell commands that pertain only to the Exchange server in their branch office.

Outlook Web App includes improvements (including, for example, the ability for users to track their sent messages and printable calendar views) and the "Premium" experience is now available across multiple browsers (including Safari and Firefox).

Distribution groups can now be "moderated", meaning that distribution groups can now be configured to allow users to join at will or only with a group moderator's permission, and individual messages sent to distribution groups can now be approved or denied by a moderator.

Exchange Server 2010 introduces a transport concept called "Shadow Redundancy" which protects e-mail messages while they are in transit. If a Hub Transport server or an Edge Transport server fails after it has received a message for processing, but before it was able to deliver it to the next "hop" server, the server which sent the message to that transport server is now able to detect the failure and redeliver the message to a different Hub Transport or Edge Transport server for processing.

In January 2011, Microsoft Exchange Server 2010 won InfoWorld's 2011 Technology of the Year Award for Best Mail Server

EXCHANGE SERVER 2010 FEATURE

Legal hold

Over the last several years, it has become increasingly more common for an organization's email messages to be subpoenaed as part of the litigation process. The problem is that email is dynamic in nature. Messages are constantly being sent, received, and deleted. Likewise, messages in the archives are often set to expire after a specific length of time. All of these factors have made it difficult to comply with litigation-related message retention requirements.

Exchange 2010 offers a new legal hold feature. This feature allows you to preserve the contents of an Exchange mailbox. Users can still use their mailbox in the usual manner, but copies of all items are retained, even if they delete them or if archived content would otherwise have expired

Voice mail transcription

In Exchange 2007, the unified messaging feature caused voice mail messages to be saved as email message attachments. While that seemed to work out fine most of the time, it did sometimes make life difficult for road warriors who didn't always have the ability to play the message.

Exchange 2010 uses a speech recognition engine to automatically transcribe voice mail messages. Users still receive the voice message as an email attachment, but the email message also contains a written transcript of the voice message. Users can check their voice messages even when they don't have access to a sound card. More important, the transcription feature allows the contents of voice messages to be indexed along with traditional email messages.

Multi mailbox search

A complementary feature to legal hold is the new multi mailbox search feature. This feature makes it a lot easier for organizations to perform E-discovery. As the name implies, multi mailbox search allows a designated person to perform organization-level searches across users' mailboxes. The search interface is designed to allow administrators to search for multiple keywords or phrases simultaneously.

Personal archive

In Exchange 2010, each user can now have two mailboxes — a primary mailbox and an archive mailbox. By using an archive mailbox, users can keep their primary mailboxes uncluttered. They're free to browse their archive mailbox at will, and items can be automatically moved from their primary mailbox to their archive mailbox using retention policies.

Exchange Control Panel

The Exchange Control Panel is a new management tool built into Exchange 2010. While the Exchange Control Panel isn't designed to take the place of the Exchange Management Console or the Exchange Management Shell, it is definitely a welcome addition. The Exchange Control Panel is integrated into OWA. It allows users to perform a few basic self-service tasks, such as changing their contact information. For administrators, the Exchange Control Panel provides a way of performing some of the more common management tasks remotely using a Web interface.

Database availability groups

Exchange 2007 provided several high availability features, such as Cluster Continuous Replication. Exchange 2010 takes things a step further with database availability groups. Database availability groups allow you to designate multiple servers to host copies of individual databases. In the event of a failure, Exchange can automatically recover. Databases are no longer server specific, so you are free to mix and match the database replicas that are hosted on each mailbox server.

Call answering rules

In Exchange 2007, the auto attendant provides voice prompt menus for the organization's primary phone number. For example, an auto attendant might be used to ask callers to press 1 for English or 2 for Spanish and then route calls accordingly. In Exchange 2007, the auto attendant is an organization level feature.

In Exchange 2010, though, each user has his or her own personal auto attendant, which Microsoft refers to as the Call Answering Rules feature. Call answering rules allows users to create their own call routing options. So, for instance, an important call might be forwarded to a user's cell phone, while a less important call might go straight to voice mail.

Database-level failover

In previous Exchange Server cluster implementations, a failure required an entire cluster node to fail over. This meant that if a server was hosting multiple databases, and the disks associated with a single database were to fail, the entire server would have to fail over — which would be disruptive to users whose mailboxes weren't even stored on the failed disks.

In contrast, Exchange 2010 supports database-level fail over. That way, if a failure affects only a single database, that database can fail over without disrupting the other databases on the server

Retention policies

Retention policies allow messages to be tagged in a way that reflects their useful lifespan and what should happen when they expire. For example, you could specify that items in one folder should be deleted after 30 days, while items in another folder should be moved to the archives after five years. Users can also apply retention policies to individual messages that are separate from folder-level policies.

Role-based access control

Exchange 2010 uses a new access control model called role-based access control. Now, administrators can perform delegation based on the role that the delegate will be performing. This means that rather than guessing which permissions the delegate will need, the administrator can simply tell Exchange which tasks the delegate will be performing.

EXCHANGE SERVER VERSION

Features Exchange Server
2003
Standard Server
Exchange Server
2003
Enterprise Server
Exchange Server
2007
Standard Server
Exchange Server
2007
Enterprise Server
Exchange Server
2010
Standard Server
Exchange Server
2010
Enterprise Server

Mailbox Databases

1-2

3-20

1-5

6-50

1-5

6-100

Database Storage Limit

75GB

None

16TB

16TB

16TB

16TB

Single Copy Cluster

No

Yes

No

Yes

No

No

Local Continuous Replication

No

No

Yes

Yes

No

No

Standby Continuous

No

No

Yes

Yes

No

No

Replication

Cluster Continuous Replication

No

No

No

Yes

No

No

Mailbox Resiliency

No

No

No

No

Yes

Yes

Keep in mind you also need client access licenses or CAL's. The are sold in standard and enterprise edition. The enterprise however is just an add-on to the standard license. So for one enterprise user you must have a standard CAL and enterprise CAL. The main difference between the two is unified messaging which enterprise gives you the rights to.

EXCHANGE SERVER 2010 HARDWARE REQUIRMENT

Memory Minimum of 4 Gigabyte (GB) of RAM per Server Plus 5 Megabyte (MB) of RAM recommended for each Mailbox. Disc Space

  • Atleast 1.2 GB on the drive used for installation.
  • An additional 500MB of avail disk space for each Unifield Messaging(UM) language pack that you plan to install.
  • 200MB of Available disk space on the system drive.
  • Drive-DVD-ROM drive, Local or Network - accessible.
  • File - Format - Disk Partitions formatted as NTFS file Systems.
  • Monitor- Screen Resolution 800*600 Pixels or higher.

To Call us for Free Consultation to Deploy & Maintain the Exchange Server.