Transition from Exchange Server 2003 to Exchange Server 2010-Part-1

A Brief Overview on Exchange Server 2010 Product

Before the release of Exchange Server 2010, we had deep dive on Exchange Server 2003 Transition to Exchange Server 2007. Now it’s a time to take a ride on transition process from Exchange Server 2003 to Exchange Server 2010.

Transition process from Exchange Server 2003 to Exchange Server 2010 is quite simple for those guys who have already done the transition from Exchange Server 2003 to Exchange Server 2007 because the concept, terminology and Architecture still remain the same, except new features and great improvement in the existing one. So before we could think of transition, it is important to understand Exchange Architecture like New Features, Discontinued Features, Exchange Server Role Concept, Exchange Server 2010 Editions, Supporting Scenarios, Licensing & Pricing and finally Good reason to decide why there is need to go for upgradation,. 1)      New Features Click here

2)      Discontinued Features Click here

3)      Exchange Server Role Concept:

Exchange Server 2010 having the same roles concept what we had in Exchange Server 2007 however technical architect has been changed compare to previous version

a.       Client Access Server: Client Access Server is the main intermediate between the user’s mailbox and Exchange Mailbox Server Role. It helps to access the mailboxes via client protocols like IMAP4, POP3, Outlook Anywhere, Auto discovery, Availability and Web Services. Exchange Server 2010 CAS got one of the important feature which was not in the previous version was MAPI connection will be communicated between user’s mailbox and Exchange Server mailbox Role via CAS only. The main advantage of this, if the mailbox server is down for few seconds users won’t get the pop-up notification stating the mailbox has been disconnected. Best Example Database failover.

b.      Hub Transport Server Role: Hub Transport Server Role is responsible for sending and receiving email within the organization and even for the outside the organization. Apart from the daily task of just sending only mails, it also takes the responsibility of creating a policies & compliance features and optionally Anti-spam & antivirus protection.

The following is a list of new transport and routing functionality included in Exchange 2010:

Shadow redundancy, MailTips, Moderated transport, Federated delivery, Latency service level agreement (SLA) management, End-to-end message tracking, Incremental EdgeSync, Transport rules integration with AD RMS, Transport dumpster improvements & Transport database improvements

c.       Mailbox Server Role: As the name itself it is representing the functionality information. It holds the users and public folder database. Some of the significant changes:

                                                              i.      Database page size has been increased to 32KB

                                                            ii.      Changed the mode of Database High Availability by offering Database Availability Group aka DAG.

                                                          iii.      No more storage group concept, Mailbox databases no longer connected to the server object

                                                           iv.      Ability to move a mailbox while the end user is still accessing it.

                                                             v.      Ability to send mail to recipients from the EMC

d.      Unified Messaging Server Role: This Server role is used for unified communications which will assist you to callup your mailboxes. Some of the new functionality in Exchange Server 2010: 

                                                        i.            Call answering rules

                                                      ii.            Additional language support included in Outlook Voice Access

                                                    iii.            Enhancements to name lookup from caller ID

                                                     iv.            Voice Mail Preview

                                                       v.            Message Waiting Indicator

                                                     vi.            Missed call and voice mail notifications using text messaging

e.      Edge Transport Server Role: This role is used to send and receive email outside the organization. This is optional server role. The function is as same like Hub, only few things we need to take care while deploying the Edge Server – It should be in the DMZ network, it should not be part of Active Directory member (recommended).

4. Exchange Server 2010 Editions – click here

Why you there is a need to Upgrade the existing environment with Exchange Server 2010?

        i.            Reduced Deployment Cost:  

Initially  we need to use third party tool or application for email archiving, mobile e-mail access and voice mail. By implementation of Exchange Server 2010 we can avoid this third party tool.

       ii.            Improved and Simplified High Availability:

High Availability was complex scenario in Exchange Serve 2003, which has been simplified and improved alot in Exchange Server 2007. However in Exchange Server 2010 - This has improved alot by bringing a new feature called as DAG(Database Availability Group) and as we are using Windows Server 2008 SP2 or R2 the cluster performance has been increased. Moreover the disaster recovery process has been improved.

    iii.            Easier Administration

     iv.            Flexibility in access the users mailbox

       v.            Reduced risk of malware and spam

     vi.            Safeguard for Sensitive information

Licensing:

License Types - Exchange Server 2010 on-premise is licensed in the Server / Client Access License (CAL) model in exactly the same way that Exchange Server 2007 was licensed. There are three types of licenses:

i.                     Server Licenses : A license must be assigned for each instance of the server software that is being run. The Exchange Server license is sold in two server editions:

a.       Standard Edition: designed for the mailbox needs of small to medium organizations. Also appropriate for non-mailbox roles in a larger Exchange deployment.

b.      Enterprise Edition: designed for larger organizations that may require a greater number of mailbox databases.

ii.                   Client Access Licenses (CALs) : Exchange requires a CAL for each user or device that accesses the server software.  There are two types of CALs for Exchange:

a.       Standard CAL: designed to help users be more productive from virtually any platform, browser, or mobile device, with new features in Exchange Server 2010 that help manage communications overload and lower helpdesk costs.

b.      Enterprise CAL: designed to allow organizations to reduce the costs and complexity of meeting compliance requirements with new integrated archiving functionality and information protection capabilities, while also helping you cut costs by replacing legacy voice mail systems with Unified Messaging.

The Enterprise CAL is sold as an add-on to the Standard CAL. To enable Standard CAL features for a user, the user must be licensed with just the Standard CAL. To enable Enterprise CAL features, the user must be licensed with one Standard CAL plus one Enterprise CAL. 

Note: Both CALs work with either Server Edition.

iii.                  External Connector Licenses: An External Connector permits an unlimited number of clients to access an Exchange Server in scenarios where the number of CALs is uncertain. Access via the External Connector is limited to non-employees such as partners, suppliers, customers, and retirees.The number of External Connector licenses required corresponds to the number of servers in the organization’s Exchange environment.

Source: Microsoft Exchange Website

For More Information:

Review the Exchange Server 2010 Licensing Overview.

Exchange Server 2010 Cost Savings Calculator:

Although we know that Exchange Server 2010 is going to reduce a cost in many ways but it is very important to know how much can be the approximate cost we can save. For this cost saving Microsoft Came up with a new tool called as “Exchange Server 2010 Cost Saving Calculator” this tool will help us to give out an approximate amount interms of saving.

To access the tool click here:

I am sure after accessing the above link IT engineer can easily persuade or approach  their management by showing the rough estimate of cost saving.

I hope this article is being informative to you all.

Related Articles:

Transition from Exchange Server 2003 to Exchange Server 2010 – A brief overview on Exchange Server 2010 – Part1

Transition from Exchange 2003 to Exchange Server 2010 – Installation of Exchange Server 2010 – Part2

Transition from Exchange Server 2003 to Exchange Server 2010 – Moving Public Folders, System Folders and Mailboxes – Part3

Transition from Exchange Server 2003 to Exchange Server 2010 – Re-routing the mailflow path & decommissioning the Exchange Server 2003 – Part4