Transitioning from Exchange 2007 to Exchange 2010—-Step by Step

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.

Further Study

Transition from Exchange 2003 to Exchange 2010 

Watch TechNet Video on Transition from Exchange 2007 to Exchange 2010Exchange 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.

Further Study

Transition from Exchange 2003 to Exchange 2010 

Watch TechNet Video on Transition from Exchange 2007 to Exchange 2010