Microsoft Exchange 2010 Migration

Posted by Bhavesh Joshi On Thursday, May 23, 2013 0 comments
Microsoft Exchange 2010 Migration
Microsoft Exchange business email helps increase user productivity while protecting business data. Exchange Server consists of a mail server, calendaring software, and contact manager. It is a server program that runs on Windows Server and is part of the Microsoft Servers line of products. As part of the Exchange Server product line, Microsoft Exchange Server 2010 adds a number of innovative features, technologies, and services to the product line.

Beneficial features of Microsoft Exchange 2010 include: DAG (Database Availability Groups), Client Access Server (CAS), Mailbox Server Role may be combined with the CAS, RPC Client Access, cost savings in required hardware, Personal Archive, and enhancement of compliance and legal search features. As well, clients benefit from: Administration delegation, improvements in Outlook Web App, distribution groups can be configured to allow users to join at will or only with a group moderator's permission, as well as ‘Shadow Redundancy’ which protects e-mail messages while they are in transit.

Exchange 2010 Migration can seem like a difficult task, however with the right step-by-step approach, the process can be much easier.  The following outlines the steps involved with Exchange 2010 Migration:

Step 1. Planning: The first step involves identifying all of the critical technical and business details that will guide the overall direction of migration. You can use such tools as the Exchange Pre-Deployment Analyzer and Exchange Profile Analyzer, but you should talk to others in the business about the processes they rely on email for. The gathered information is used with Microsoft’s website guidance to create the design of your Exchange 2010 environment.

Step 2. Deployment: The second step entails installing each of the Exchange 2010 server roles in your environment, and then configuring them according to your design. There should not be a problem completing the deployment stage  when you know about the specific risks and take the appropriate steps to avoid those risks.

Step 3. Testing: This is a critical step because it will make known any problems before they have a chance to negatively affect end users or production systems. Testing should include the business and technical requirements that were identified during the planning step. One essential test that must be performed is Exchange 2010 backup and recovery. It is important to ensure that fully functioning backups are in place for the Exchange 2010 servers before any production mailbox migrations occur.

Step 4. Migration: You can choose between two migration approaches. The first migration approach is called Co-Existence which involves the mailbox data being migrated over a period of days, weeks, or sometimes months. This requires additional set up steps, such as configuring the legacy namespace in order that remote access methods such as ActiveSync and Outlook Web App (OWA) work for users with mailboxes on both versions of Exchange during the migration. The second migration approach is a full migration which can take place in one weekend.This can be done for smaller environments. If the full migration can be performed in a single window of time you may not need to set up co-existence.

Step 5. Decommission: Decommission consists of a series of required steps to make sure that features such as the Email Address Policies and Offline Address Book work correctly. To make sure no legacy issues remain, the old Exchange servers must be removed from the environment. After decommissioning has been completed, Exchange 2010 Migration has been successfully performed.

Microsoft Exchange Server 2010
There are many good reasons to migrate to Exchange 2010. In terms of disk read/write performance, the Exchange Server 2010 database engine is up to 70% more efficient than Exchange Server 2007. This means it is possible to deploy bigger databases with bigger mailbox quotas on cheaper and larger disks. Exchange Server 2010 also has one high availability option for Mailbox servers which is the Database Availability Group. Moderated Transport permits distribution lists and mailboxes to be moderated by a non-admin user. As well, the ‘Mail Tips’ feature, when used with Outlook 2010, will warn clients of such email mistakes as doing a‘reply all’ to a large group, or sending sensitive emails to external parties. Exchange 2010 Migration is much easier and less complex when you understand the steps involved in the migration process.


Post a Comment