Sei sulla pagina 1di 10

CHAPTER THREE

DEFINITIVE GUIDE
TO EXCHANGE SERVER
2010 MIGRATION

EXCHANGE 2003
TO EXCHANGE 2010:

MAKING THE
TRANSITION

Planning a move to
Microsoft Exchange 2010?
Keep your email up and running throughout your migration with Mimecast.
Microsoft Exchange 2010 delivers greater deployment
flexibility and reliability than ever before. Its without
doubt the best version of Exchange yet.
But if you are looking to move to Exchange 2010, you
need to identify and assess the additional risks that
may be introduced during the migration process, such
as email downtime, data loss and interruptions to policy
enforcement.

To download your free Three Step Plan,


visit www.mimecast.com/Migrateto2010.

To find out how Mimecast can help you mitigate the risks of migration
visit www.mimecast.com/Migrateto2010 or call us on 1800 660 1194

CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010

Exchange 2003
to Exchange 2010:
HOME

PREREQUISITES
FOR THE MOVE TO
EXCHANGE 2010

REACHING OUT
TO THE
DEPLOYMENT
ASSISTANT

STEPS IN THE
TRANSITION

MAKING THE
TRANSITION
The transition from Exchange Server 2003 to Exchange
2010 is not simple. Skip a step along the way and the whole
process becomes even more complicated.
BY J. PETER BRUZZESE

SHUTDOW:
THE FINAL
STAGES

the process of
moving from Exchange Server 2003
or Exchange 2007 to Exchange
2010 as a transition, not a migration,
as many refer to it. While this may
seem like simple semantics, there is
a reason behind it. A transition
includes a period of time in which
both the legacy Exchange servers
and new versions of Exchange function in a coexistence scenario. The
length of time the coexistence period lasts varies from company to
company and depends on the length
of time it takes to remove the last
legacy Exchange Server.
MICROSOFT REFERS TO

So how does the transition from


Exchange 2003 (or Exchange 2007)
to that perfect state of Exchange
2010 happen? Whats involved?
This chapter explains the complicated transition from Exchange 2003
to Exchange 2010, with a few points
included for Exchange 2007 administrators.

PREREQUISITES FOR THE


MOVE TO EXCHANGE 2010

The first step in moving to Exchange


2010 is to verify that your environment meets the various prerequi-

DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION SEARCHEXCHANGE.COM

CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010

sites. For example, make sure your


existing directory service infrastructure is up to par by checking that
you've met the following criteria:
HOME

PREREQUISITES
FOR THE MOVE TO
EXCHANGE 2010

REACHING OUT
TO THE
DEPLOYMENT
ASSISTANT

STEPS IN THE
TRANSITION

SHUTDOW:
THE FINAL
STAGES

Schema master: Confirm that its


running Windows Server 2003 SP1
Standard, Enterprise or a later edition.
Global catalog server: In every
Active Directory site where you plan
to install Exchange 2010, you need at
least one global catalog server running Windows Server 2003 SP1 Standard, Enterprise or a later edition.
Active Directory forest: The AD
forest functional level must be running Windows 2003 forest functional mode.
Domain controller: AD domain
controllers must be running Windows 2003 SP1 Standard, Enterprise
or a later edition.
Once youve verified this, check
your environment for its readiness
for Exchange 2010. In a smaller
environment, you can check this
manually. In a larger Exchange Server environment, its easier to download and use the free Exchange PreDeployment Analyzer , which runs
an overall topology readiness scan.
With Exchange 2010, in-place
upgrades of an existing server are not
possible. Therefore, youll need to
install Exchange 2010 on its own 64bit server. That server has to run as a

member server of the domain on an


X64-based system running either
Windows Server 2008 Standard or
Enterprise SP2 edition or Windows
Server 2008 R2 Standard or Enterprise edition. Before installing Exchange 2010, both Exchange 2003
and Exchange 2007 must be on SP2.
The next prerequisite is to prepare
the Active Directory schema for an
Exchange 2010 installation, which
you can do in a variety of ways. In
smaller Exchange installments where
administrators are in complete control of upgrade decisions, you simply
start the installation using the graphic setup; behind-the-scenes commands and switches will run at that
point. However, if you are in an environment that requires the process to
be broken down into smaller pieces,
take it one step at a time by running
the following switches:
Setup/PrepareLegacyExchange
Permissions: This command, which
you can enter as /pl, is absolutely
necessary for the transition from
Exchange 2003 to Exchange 2010.
It ensures that permissions are prepared between the two versions.
Setup/PrepareSchema: This command, entered as /ps, will extend
the schema.
Setup/PrepareAD: Entered as /p,
the command runs the other two
commands if you havent started
them yet. This multi-tasked switch

DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION SEARCHEXCHANGE.COM

CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010

will create Exchange security groups


and prepare the local domain for
Exchange.

HOME

PREREQUISITES
FOR THE MOVE TO
EXCHANGE 2010

REACHING OUT
TO THE
DEPLOYMENT
ASSISTANT

STEPS IN THE
TRANSITION

SHUTDOW:
THE FINAL
STAGES

Setup/PrepareDomain or /Prepare
AllDomains: These switches (/pd
or /pad, respectively) create a new
global group called Exchange Install
Domain Servers for the domain.
They also add that group to the Exchange System Objects container
and the Exchange Servers group for
the root domain.
As a final prerequisite, youll need
to do some patchwork changes to
the Exchange 2003 environment to
allow it to communicate and perform
message transport with Exchange
2010. For example, Exchange 2010
creates an Exchange routing group
that is only visible using Microsoft

Exchange Server 2003 Exchange


System Manager. Note: The route
will be named DWBGZMFD01QNBJR.
Exchange also creates routing
group connectors between the
Exchange 2003 bridgehead routing
group and the Exchange 2010 server. Youll also need to create an
Exchange Administrative Group on
Exchange 2003; the group will be
named FYDIBOHF23SPDLT.

REACHING OUT TO THE


DEPLOYMENT ASSISTANT

Before you begin the physical transition to Exchange 2010, you should
seek the help of Microsofts Exchange Server Deployment Assistant.
Dont let the tools initial screen,
shown in Figure 1, distract you. This is

FIGURE 1.

The Exchange Server


Deployment Assistant

DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION SEARCHEXCHANGE.COM

CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010

HOME

PREREQUISITES
FOR THE MOVE TO
EXCHANGE 2010

REACHING OUT
TO THE
DEPLOYMENT
ASSISTANT

the newest iteration of the assistant,


which takes into account companies
that want to coexist with a cloudbased hosted Exchange solution such
as Microsoft Business Productivity
Online Suite (BPOS) or Office 365.
Our focus, however, is strictly on the
on-premises option.
Once you select the "On-Premises
Only" option, you'll need to choose
from a range of options, including
deploying from Exchange 2003 to
Exchange 2007, Exchange 2003 to
2010, Exchange 2007 to 2010 and a
completely new install of Exchange
2010 (Figure 2). The tool asks yes/no
questions to narrow down your needs
during the transition.

STEPS IN THE
TRANSITION

STEPS IN THE TRANSITION


SHUTDOW:
THE FINAL
STAGES

Once youre certain that your com-

panys entire environment can handle the upgrade to Exchange 2010,


you still need to do more prep work.
If your organization has multiple
sites, youll need to install the
Exchange 2010 server onto an
Internet-facing site.
I recommend administrators do a
typical installation of all three key
server rolesclient access server,
hub transport server and mailbox
server. However, some design architectures require that you deploy
servers in stages. In these situations, I recommend using the following order:
1. Client access server (CAS)
2. Hub transport server
3. Unified Messaging server,
which is optional
4. Mailbox server

FIGURE 2.

Exchange 2010
deployment scenario
choices

DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION

SEARCHEXCHANGE.COM

CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010

5. Edge transport server, which is


optional.

HOME

PREREQUISITES
FOR THE MOVE TO
EXCHANGE 2010

REACHING OUT
TO THE
DEPLOYMENT
ASSISTANT

STEPS IN THE
TRANSITION

SHUTDOW:
THE FINAL
STAGES

To secure external access with a


CAS, you need digital certificates. Its
recommended that you obtain a subject alternative name certificate from
a reputable certificate authority (CA).
Since you will be running a coexistence environment, you will need at
least three different namespaces
one for the current namespace, one
for the legacy namespace and one for
autodiscover. If your company connects to its mail through mail.companyname .com, which is one fully qualified domain name (FQDN), you
should also register autodiscover.company name.com and legacy.companyname.com. Finally, youll need to install
the certificate on the legacy Exchange
2003 servers.
If youre trying to expedite the
transition or plan to move all
Exchange mailboxes over in one fell
swoop, you dont need to be concerned with legacy host names.
Youll need only a subject alternative
name certificate for the current
namespace and autodiscover.
During the transition to Exchange
2010, one users mailbox may
reside on Exchange 2003 while
another resides on Exchange 2010.
With the legacy namespace, all
usersno matter which server version their mailboxes reside on
need to type only one thing to
access Outlook Web App or
ActiveSync services.

Prep Outlook Address Book and


directories. Depending on how
users access the email environment
in off-site situations, you may want
to enable Outlook Anywhere, configure the Outlook Address Book
(OAB) and Web Services virtual
directories or configure Exchange
ActiveSync settings. Youll also need
to change the OAB generation server to Exchange 2010.
Once you are ready to move the
OAB to Exchange 2010, go to Properties and choose Web-based distribution from the Distribution tab. This is
the modern method for Exchange
2007 and Exchange 2010 servers, so
you dont need public folders or public folder distribution. From the
Actions pane, choose Move and then
the Exchange 2010 server that will
host the OAB.
Transition inbound/outbound
mail flow. Now youll need to
reroute outbound Internet mail flow
from Exchange 2003 to Exchange
2010. With the implementation of
the edge transport server role, Send/
Receive connectors will work out of
the box because the edge transport is
automatically configured to send and
receive email. However, if you forego
installing the edge transport server
role, youll need to make some configuration changes to the hub transport
server. In addition, youll need to
change Send connectors and Receive
connectors on the hub transport server. Receive connectors are created by

DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION SEARCHEXCHANGE.COM

CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010

HOME

PREREQUISITES
FOR THE MOVE TO
EXCHANGE 2010

REACHING OUT
TO THE
DEPLOYMENT
ASSISTANT

STEPS IN THE
TRANSITION

SHUTDOW:
THE FINAL
STAGES

default; theyre not configured to


allow anonymous inbound mail flow.
Exchange users can send mail internally but cannot receive external mail
unless Receive connectors are properly configured.
To configure Receive connectors,
go to the Server Configuration node
and locate Receive connector settings under the hub transport server
side. Then go to the Permissions
Groups tab and select Anonymous
Users to allow Internet-based email
to enter the organization.
Clean up public folders. If your
organization is using public folders,
youll need to set up a public folder
database in Exchange 2010 and
create replicas of the data. Then
remove legacy Exchange servers
from the list of replicated folders so
that all content resides on Exchange
2010. Set aside plenty of time for
this step; replicating public folders
especially if your public folder tree
has sprawled out of controlis a
time-consuming process. You might
even want to set aside a day for this
and perform a few tests afterward
to be sure all data moved.
Move Exchange 2003 mailboxes.
When you move a mailbox from
Exchange 2003 to Exchange 2010,
you must take the mailbox offline.
So, plan to move mailboxes after
regular business hours. This is different when you upgrade from
Exchange 2007 to Exchange 2010

mailbox moves can occur simultaneously. To move them, open the


Exchange Management Console
(EMC) and use the New Local Move
Request. Once youve moved all
mailboxes, go back and convert
them to resource mailboxes for
rooms or equipment, as needed.

SHUTDOWN: THE FINAL STAGES

When youre certain that youve


moved all mailboxes over to
Exchange 2010and you must be
certain because you cannot leave
anything behind in a storage
groupyou can move the Recipient
Update Service (RUS) to Exchange
2010. This step is a bit of an anomaly since Exchange 2010 doesnt
actually use the RUS. You cannot
uninstall Exchange Server 2003
from an environment if its the only
server running the RUS. First youll
need to use Exchange System Manager to enable the RUS on another
server. Moreover, you cant uninstall
Exchange Server 2003 from an environment server if its the only server
in a mixed-mode architecture thats
running Site Replication Service
(SRS). Youll have to enable SRS on
another Exchange Server first.
After you create the Recipient
Update Service , you may need to
enable Site Replication Service on a
second Exchange server. Be sure to
clear away all bridgehead information and routing group data before
you try to uninstall RUS.

DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION SEARCHEXCHANGE.COM

CHAPTER 3: EXCHANGE 2003 TO EXCHANGE 2010

HOME

PREREQUISITES
FOR THE MOVE TO
EXCHANGE 2010

REACHING OUT
TO THE
DEPLOYMENT
ASSISTANT

STEPS IN THE
TRANSITION

SHUTDOW:
THE FINAL
STAGES

Once youre completely confident


that all mailboxes have been moved to
Exchange 2010, youve replicated all
public folder databases and and
you've taken care of other odds and
ends such as the RUS, the last step is
to click Add or Remove Programs on
Exchange Server 2003 and uninstall it.

here are fewer steps involved


in removing Exchange 2007
simply because you don't have to
worry about items like the Recipient Update Service (RUS) and Site
Replication Service (SRS). You
simply have to remove Exchange
2007 from the Add or Remove
Programs (in Windows Server
2003) or from Programs and Features (in Windows Server 2008).

At this point, verify that your


Exchange configuration is correct.
Several tools are available to help
test external connectivity to the
new Exchange environment, including the Exchange Best Practices
Analyzer (ExBPA) and the Exchange
Remote Connectivity Analyzer
(ExRCA).
J. Peter Bruzzese, Triple-MCSE, MCT, MCITP:
Enterprise Messaging, is an Exchange MVP,
an Exchange Instructor for Train Signal and the
co-founder of ClipTraining.com. He is a technical
author for Que Publishing, has produced hundreds of articles and videos about Exchange
Server, and speaks at a variety of conferences.
He is a frequent contributor for TechTargets
SearchExchange.com and InfoWorld. Follow him
on Twitter.

Cathleen Gagne
Editorial Director
cgagne@techtarget.com

Matt Gervais
Site Editor
mgervais@techtarget.com

Michelle Boisvert
Senior Managing Editor
mboisvert@techtarget.com

Linda Koury
Director of Online Design
lkoury@techtarget.com

Marc Laplante
Publisher
mlaplante@techtarget.com

TechTarget
275 Grove Street
Newton, MA 02466
www.techtarget.com

2011 TECHTARGET. ALL RIGHTS RESERVED.

DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION SEARCHEXCHANGE.COM

RESOURCES FROM OUR SPONSOR

See ad page 2

A Three Step Plan for Migrating To Microsoft Exchange 2010


Basic Energy Services Deploys Mimecast SaaS-Based UEM: Achieves Email Continuity
and Greater Security and Compliance and Saves on Cost
IDC Vendor Spotlight: Using Cloud-Based Email Management to Integrate Archiving,
Security, and Business

About Mimecast:
Mimecast (www.mimecast.com) delivers cloud-based email management for Microsoft
Exchange, including archiving, continuity and security. By unifying disparate and fragmented
email environments into one holistic solution that is always available from the cloud, Mimecast
minimizes risk and reduces cost and complexity, while providing total end-to-end control of
email. Founded in 2003, Mimecast serves approximately 4,000 customers worldwide and
has offices in Europe, North America, Africa and the Channel Islands.

Potrebbero piacerti anche