Exchange 2010 Migration

Collect Exchange 2010 Server requirement (Exchange 2010 server require x64 bit OS)
Storage groups, routing groups and administrative groups are no longer exist

The sequence for a migration from Exchange 2007 to Exchange 2010 is as follows:
1. Upgrade all Exchange Servers to Exchange Server 2007 Service Pack 2.
2. Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
3. Upgrade at least one Global Catalog domain controller in each AD Site that will house Exchange Server to
Windows Server 2003 SP2 or greater.
4. Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
5. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
To install Ldifde.exe on the local computer
1. Click Start, Run, and in the Open field run 'ServerManagerCmd -i RSAT-ADDS'

6. Install any necessary prerequisites (WWW for CAS server role).
7. Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs
all in one step or separate at the command line.)
8. Install CAS server role servers and configure per 2010 design. Validate function-ality.
9. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
10. Install Hub Transport role and configure per 2010 design.
11. Transfer inbound and outbound mail traffic to the 2010 HT servers.
12. Install Mailbox servers and configure Databases (DAG if needed).
13. Create public folder replicas on Exchange 2010 servers using AddReplicatoPFRe-cursive.ps1or Exchange 2010
Public Folder tool.
14. Move mailboxes to Exchange 2010 using Move Mailbox Wizard or Powershell.
15. Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
16. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
17. Delete Public and Private Information Stores from Exchange 2007 server(s).
18. Uninstall all Exchange 2007 servers.
Note: CAS Role requires SSL certificate and web certificate from Enterprise CA. CAS is placed in perimeter, without
proper certificate (contact Verisign/Godady/Entrust for SSL Certificate) you will not be able to access webmail
properly. Certificate from CA is require to publish CAS in Forefront TMG/ISA. You need just certificate not CA
role installed. CA role is separately installed in other computer placed in internal network.
AD LDIFDE will be installed during Exchange preparation i.e. installation wizard will do it for you if you logged on as
a Schema Admin, Enterprise Admin and Domain Admin. Pls run AD in Win2k8 Native mode before starting
wizard.
Anbu Selvan
Exchange Server 2007 and Exchange Server 2010 are similar in architecture so the transition process is more
straightforward. The following procedure illustrates a typical transition from Exchange Server 2007 to Exchange
2010:
Prerequisite:

Run Dcdiag, Netdiag and check FSMO roles functioning perfect.
All domains in an existing Active Directory forest have to be running in native mode.
The Active Directory forest has to be running on a Windows Server 2008 forest functionality level.
Each site in Active Directory should have at least one PDC, schema master and the Global Catalog server on a
Windows Server 2008 SP2 level. It is recommended to have 64-bit type Domain Controllers and Global Catalog
Servers for optimal performance preferably Windows Server 2008 x64 SP2 or Windows Server 2008 R2
All Exchange Server 2007 servers must have Exchange Service Pack 2 installed.
The Internet facing Active Directory sites must be the first sites that will be migrated to Exchange Server 2010.
Windows Server 2008 SP2 64 bit or Windows Server 2008 R2.
Internet Information Server needs to be installed for CAS.
Web Certificates must be installed in server holding CAS
Windows Remote Management (WinRM) 2.0
PowerShell 2.0 (Windows Server 2008 feature if R2 version)
.NET Framework 3.5 (Windows Server 2008 feature)
Desktop Experience (Windows Server 2008 feature)
Net. TCP Services started and set automatic (services.msc)
Disable TCP/IP6 from Registry (if you use tcp/ip4)
2007 Office System Converter
Better to Prepare a document showing task list and systems build info. Tick one after one when finishing a task
accordingly.
Precautions:
Backup Active Directory global Catalog servers, Exchange servers and Servers that interoperate with Exchange
Server, such as gateway systems or replicated directory servers. It is also a best practice to turn off any replication
to other environments during the transition process, such as Forefront Identity Manager (previously named ILM,
MIIS, IIFP, and MMS).
Please bear in mind that an in-place upgrade to Exchange Server 2010 in any scenario is NOT supported!
Please be aware that Win2k8 AD and Exchange 2010 (HT, MT, CAS, ET Role, Unified Messaging) are based on
64 bit architecture.
Migration from Windows 2003 AD Forest to Windows 2008 AD Forest and Forest Preparation
Create user with domain admin, schema admin and enterprise admin role from existing AD
Log on using new user name
Bring the AD forest and domains to Windows Server 2003 Functional Level
Insert Win2k8 Server DVD into Win2k3 DC
Use elevated command prompt using domain\username (where user name must be above mentioned) Start
Menu>Run type runas /user:domain\username cmd.exe
Provide Password
d:\sources\adprep\adprep.exe /forestprep where d: is DVD ROM
d:\sources\adprep\adprep.exe /domainprep /gpprep
d:\Setup and select upgrade option to use existing DC
Transfer FSMO Roles for a new Win2k8 DC with new Hardware
Make one DC as GC
Replicate AD database, GPO or wait tomstone to replicate
Retire Windows 2003 DC
Run DCPROMO (Uncheck this is last remaining DC)
Raise new Domain Functional level to Win2k8
Insert Exchange 2010 DVD into DC to upgrade AD
Open command prompt and change directory to DVD rom
Type Setup.com /PrepareSchema
Type .\Setup /PrepareAD /OrganizationName:organisation_name

Transition Sequencing:
Once you have finished prerequisite, you have to take the installation order of the Exchange Server 2010 servers
into account to minimize the impact:
Exchange Server 2010 Client Access Server. The Client Access Server can work with an Exchange Server 2007
Mailbox Server as well as an Exchange Server 2010 Mailbox Server.
Exchange Server 2010 Hub Transport Server (New Internal and External Connector). Documents all the policies
you have in existing HT and apply same in new HT server.
Exchange Server 2010 Mailbox Server. After you have installed the Mailbox Server role and established a
proper Public Folder replication between Exchange Server 2007 and Exchange Server 2010, you can start moving
mailboxes to the new Exchange 2010 Mailbox Server. Of course, the Public Folder replication needs only be
configured when Public Folders are used in Exchange Server 2007.
The Edge Transport Server can be installed at any time, since an Exchange Server 2010 Edge Transport Server
can be subscribed to an Exchange Server 2007 SP2 Hub Transport Server. Use Export and Import option for all
policies applied in previous ET server.
Finally Unified Messaging

Transitioning from Exchange Server 2007 to Exchange Server 2010
1. Prepare Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010
2. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
3. Install necessary prerequisites (WWW for CAS server role) including web certificates.
4. Install CAS server role servers and configure per 2010 design. Validate functionality.
5. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
6. Install Hub Transport role and configure per 2010 design.
7. Transfer inbound and outbound mail connector to the new 2010 HT servers.
8. Install mailbox servers and configure Databases (DAG if needed).
9. Create public folder replicas on Exchange 2010 servers using Exchange 2010 Public Folder tool.
10. Move mailboxes to Exchange 2010 using Move Mailbox Wizard.
11. Re-home the Offline Address Book (OAB) generation server to Exchange Server 2010.
12. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder stores.
13. Delete Public and Private Information Stores from Exchange 2007 servers.
14. Remove Exchange 2007 Edge Transport subscription
15. Uninstall all Exchange 2007 servers.
Test Procedure:
Double check Exchange Roles and services are started
Check event logs
Check internal and external connector
Test OWA and Email using test user
Run BPA
Verify with the system build info you created at beginning to check what you might have missed out or not!
Key Factors:
The following key factors differentiate a 2007 to 2010 transition from a 2003 to 2010 transition:
Exchange admin groups and routing groups are already out of the picture.
The Recipient Update Service is no longer part of the transition process.
The public folder hierarchy does not need to be re-homed. Indeed, because public Folders are not required for
Exchange Server 2007, they might not even be part of the transition.
One added advantage of transition from Exchange Server 2007 to Exchange Server 2010: if Outlook clients are at
2007 levels or above, the move mailbox process does not result in downtime, making the end user transition
experience completely transparent.
Exchange 2007- 2010 Transition
In my last blog post I covered the migration process from Exchange 2003 to Exchange 2010. In this post, Im going
to outline the sequence and provide tips, tricks, and best practices to look forward to in the migration process
from Exchange 2007 to Exchange 2010.
Since Exchange 2010 is similar if not almost identical to Exchange 2007 in terms of server roles (CAS, Hub
Transport, Mailbox, Edge), if you implemented Exchange 2007 in a manner that suits the needs of your
organization, then your transition to Exchange 2010 will be pretty straight forward. Effectively, you would add
Exchange 2010 server roles to mirror the Exchange 2007 server roles you have today (ie: if you have 2 CAS/2007
servers today, youd likely build up 2 CAS/2010 servers in the Exchange 2010 environment, etc).
The sequence for a migration from Exchange 2007 to Exchange 2010 is as follows:
1. Upgrade all Exchange Servers to Exchange Server 2007 Service Pack 2.
2. Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
3. Upgrade at least one Global Catalog domain controller in each AD Site that will house Exchange Server to
Windows Server 2003 SP2 or greater.
4. Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
5. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
6. Install any necessary prerequisites (WWW for CAS server role).
7. Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup
runs all in one step or separate at the command line.)
8. Install CAS server role servers and configure per 2010 design. Validate function-ality.
9. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
10. Install Hub Transport role and configure per 2010 design.
11. Transfer inbound and outbound mail traffic to the 2010 HT servers.
12. Install Mailbox servers and configure Databases (DAG if needed).
13. Create public folder replicas on Exchange 2010 servers using AddReplicatoPFRe-cursive.ps1or Exchange 2010
Public Folder tool.
14. Move mailboxes to Exchange 2010 using Move Mailbox Wizard or Powershell.
15. Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
16. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
17. Delete Public and Private Information Stores from Exchange 2007 server(s).
18. Uninstall all Exchange 2007 servers.
One of the areas of change that youll make with your transition to Exchange 2010 that is different than in your
Exchange 2007 implementation is the high availability and disaster recovery functions of your Mailbox server role.
Because the concepts of Single Copy Clusters, Cluster Continous Replication (CCR), and Standby Continous Replicaton
(SCR) no longer exist in Exchange 2010, youll be transitioning your mailboxes off of Exchange 2007 that has these
functions to Exchange 2010 that users Database Availability Groups (DAGs). Of course if you are just migrating to a
single Exchange 2010 Mailbox server with no high availability or disaster recovery, then you will just have mailbox
databases that youll be moving your mailboxes to. However for organizations implementing high availability and
disaster recovery, the DAGs provide replication of mail (of up 16 copies) from server to server. When you setup your
Exchange 2010 Mailbox servers to prepare them for the transition of mailboxes, setup your DAG replication and test
your failover and failback of Exchange 2010 Mailbox servers, and then move your mailboxes to the DAG(s).
Another area of change between Exchange 2007 and Exchange 2010 is that ALL client connections go through the CAS
server(s). Unlike Exchange 2007 and prior where OWA connections went through the CAS server but Outlook
(2003/2007) connections actually communicated directly over MAPI to the backend Mailbox servers. However with
Exchange 2010, client systems no longer communicate directly to the backend Mailbox servers. Instead, the client
MAPI connections hit the CAS server(s) that then communicate with the Mailbox servers on the backend. So just like
in the shift to Hub Transport servers in Exchange 2007 where all mail routes through the Hub Transport servers
(incoming mail, outgoing mail, user to user mail between servers, and even user to user mail between users on the
same server), with Exchange 2010, all clients go through the CAS server(s). As such, the CAS servers take on more of a
performance load and need to be beefed up a little. Our recommendations for CAS to Mailbox in Exchange 2007 was
1 CAS servers for every 2 Mailbox servers. For Exchange 2010, our recommendation is now 3 CAS servers for every 4
Mailbox servers. Most organizations have at least 2 CAS servers in their environment for redundancy, and because
you can virtualize the CAS role plus have 2000, 3000, even 5000 mailboxes on a single Mailbox server, we typically
find this 3:4 CAS:MBX ratio hasnt been a showstopper for organizations in terms of a design change.
Also important to note is that all 2007 server roles (CAS, Hub Transport, Mailbox) in Exchange 2007 need to remain
until all users are migrated to Exchange 2010. Exchange 2010 CAS, Hub Transport, and Mailbox servers are not
backwards compatible with Exchange 2007, so in order for a user to access Outlook Web Access on Exchange 2007,
they need to still hit the Exchange 2007 CAS servers to access their mailbox on the Exchange 2007 Mailbox server.
After their mailbox is migrated to Exchange 2010, then the user will hit the Exchange 2010 CAS server and access their
mailbox on the Exchange 2010 Mailbox server. Because Exchange 2010 has a proxy service on the CAS server, your
external URL for OWA can point to the Exchange 2010 CAS server and if the users mailbox is still on Exchange 2007,
the CAS/2010 server will automatically redirect the client connection to the CAS/2007 server for OWA.
Lastly, after moving mailboxes off of Exchange 2007 to Exchange 2010, leave the Exchange 2007 infrastructure in
place for a couple (2) weeks. By leaving the old Exchange 2007 server(s) in place, when an Outlook client tries to
connect to the old Exchange 2007 server for its mail, the old Exchange 2007 server will notify the Outlook client
software that the users mail has been moved to the Exchange 2010 server and will automatically update the user s
Outlook profile with the new destination server information. Thereafter, when the Outlook client is launched,
Outlook will access the users mailbox on the new Exchange 2010 server. By leaving the old Exchange 2007
infrastructure in place for a couple weeks, pretty much all of your users will launch Outlook to have the profile
automatically changed thus requiring no client system intervention during the migration process. The only users you
will likely need to manually reset their Outlook profile are users who are on extended leave and had not accessed
their Outlook mail during the 2 week time that you had the Exchange 2007 environment still in place.
Hopefully these steps are helping in providing you guidance in your migration from Exchange 2007 to Exchange 2010.
I cover the migration process in much more detail (including specific steps and step by step processes for cutting over
CAS, Hub Transport, and Mailbox server roles) in my book Exchange 2010 Unleashed from Sams Publishing. The
book was written from 2-yrs of early adopter experience working with Exchange 2010 and will hopefully provide more
detailed guidance on the migration process from Exchange 2007 to Exchange 2010.
Ive been ask to blog information about the new Hub Transport Shadow Redundancy process that provides fault
tolerance to the routing of mail through Hub Transport servers, as well as Ive been asked to blog about the new
Exchange 2010 Unified Messaging (voicemail), so Ill put together my thoughts on those areas upcoming