none
How to migrate exchange 2007 Sp3 to exchange 2010 with all the step to step?

    Question

  • How to migrate exchange 2007 Sp3 to exchange 2010 with all the step to step?
    Wednesday, January 04, 2012 5:14 AM

Answers

  • I have described all the steps here: http://windowsadmin.info/viewtopic.php?f=20&t=181&sid=f035bf30a61b78769f099b28280dbf76
    Regards from www.windowsadmin.info | www.blog.windowsadmin.info
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Wednesday, January 04, 2012 5:46 AM
    Moderator
  • Hi

    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.

    To install prerequisite follow the below link

    http://msunified.net/2009/10/30/exchange-2010-prerequisites-on-server-2008-r2/

     

    Regards

    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Wednesday, January 04, 2012 6:58 AM
  • How would i confiuge below details:

     

    1. Install CAS server role servers and configure per 2010 design. Validate function-ality.
    2. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 5:11 AM
  • The steps for introducing Exchange 2010 into the environment are:

    Note: These steps do not discuss how to set up your CAS2010 servers in a load balancing array. 

    1. In order to support external client coexistence with CAS2010 and legacy Exchange in your "Internet Facing AD Site", you will (potentially) need to acquire a new commercial certificate.  As a best practice, Microsoft recommends utilizing a certificate that supports Subject Alternative Names; however, you can utilize a wildcard certificate as well.

    This commercial certificate that will be leveraged by external clients will contain at a minimum three SAN values (note that other scenarios may require you to add additional values):

    1. mail.contoso.com (your primary OWA/EAS/OA access URL)
    2. autodiscover.contoso.com
    3. legacy.contoso.com (your OWA/EAS namespace for legacy mailbox access)

    Prior to Windows Vista SP1, the Windows RPC/HTTP client-side component required that the Subject Name (aka Common Name) on the certificate match the "Certificate Principal Name" configured for the Outlook Anywhere connection in the Outlook profile. Therefore, as a best practice, you should ensure that mail.contoso.com is listed as the Subject Name in your certificate unless you plan on changing the configuration which can be achieved by using the Set-OutlookProvider cmdlet with the -EXPR parameter as described in http://msexchangeteam.com/archive/2008/09/29/449921.aspx.

    2. Ensure all Exchange 2007 CAS within the organization are at Service Pack 2, all Exchange 2003 servers (if they exist) are at Service Pack 2, and that all Exchange 2007 Mailbox, Hub Transport, and Unified Messaging servers are at Service Pack 2 in the "Internet Facing AD Site". Also, ensure you meet all the forest/domain pre-requisites.

    3. Install CAS2010 and configure it accordingly:

    • During the installation of CAS2010 you have the option to enter the external namespace that will be used for the virtual directories. You can enter this value in both the graphical user interface or the command-line setup:
      • For the graphical user interface setup experience of CAS2010 you are asked to configure a Client Access external domain. At this point you canter the domain name of mail.contoso.com.
      • If installing via the command line, you can utilize the setup property /ExternalCASServerDomain and specify mail.contoso.com
    • If you haven't already done so, install the RPC over HTTP proxy component.  You can do this utilizing the ServerManagerCmd tool: ServerManagerCmd.exe -i RPC-over-HTTP-proxy
    • Configure your OWA settings appropriately (e.g. forms based authentication vs. basic authentication). For the purpose of this document, the default OWA settings are assumed.
    • Configure your EAS authentication settings appropriately (e.g. Basic vs. certificate authentication). For the purposes of this document, the default authentication mechanism, basic authentication, is assumed.
    • Enable Outlook Anywhere (for the purposes of this document, the default authentication settings are assumed): Enable-OutlookAnywhere -Server: -ExternalHostName:mail.contoso.com -SSLOffloading $false

    4. If you chose to not specify the external domain name for CAS during setup, you will need to enable the following ExternalURLs to ensure that clients that leverage Autodiscover function correctly:

    5. To ensure that Outlook Web Access functions correctly, you will need to enable the following URLs:

    6. If you have Exchange 2007 deployed in "Non-Internet Facing AD Sites" then you must copy the Exchange 2007 OWA binaries to CAS2010:

    • On the CAS2010 server(s), establish a connection to the CAS2007 server's drive that contains the Exchange binaries and navigate to the \Client Access\OWA directory (e.g. \\cas2007\c$\Program Files\Microsoft\Exchange Server\Client Access\Owa).
    • Copy the highest version folder (e.g. 8.2.140.0) from the CAS2007 to CAS2010 Exchange binaries \Client Access\OWA directory (e.g. C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa).
    • Execute IISReset on all the CAS2010 machines.

    7. For your Outlook clients, you can configure CAS2010 to participate in an RPC Client Access Service array:

    • Create a load balancing array for CAS2010, if one has not already been created.
    • Create a DNS entry in your internal DNS infrastructure that resolves to the Virtual IP Address (VIP) of the CAS load balancing array. The DNS entry, for example, could be outlook.contoso.com.
    • Configure your load balancing array to load balance the MAPI RPC ports:
      • TCP 135
      • TCP 1024-65535
    • Run the following cmdlet to create the Client Access Service array: New-ClientAccessArray -Name outlook.contoso.com -FQDN outlook.contoso.com -Site "Internet Facing AD Site"

    Regards

     

    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 5:20 AM
  • I would recommend you to read about these articles:

    Exchange 2007 - Planning Roadmap for Upgrade and Coexistence

    http://technet.microsoft.com/en-us/library/dd638158.aspx

    Understanding Upgrade from Exchange 2007 to Exchange 2010

    http://technet.microsoft.com/en-us/library/ff805041.aspx

    Transitioning Client Access to Exchange Server 2010

    http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx


    Jack Zhou
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 6:30 AM
    Moderator
  • Hi,

     

    Step by Step procedure of migrating Exchange 2007 to Exchange 2010 is as follows,


    How to Upgrade Single Server Exchange 2007 to Exchange 2010

    - PREWORK
    - EXCHANGE 2010 CORE INSTALL
    - CONFIGURE EXCHANGE 2010 & MIGRATE YOUR DATA
    - MOVING AN EXCHANGE 2007 CERTIFICATE TO EXCHANGE 2010
    - ANTISPAM
    - DECOMMISSION OLD EXCHANGE 2007
    - VERIFICATION

    Check out the following link for detail steps,

     

    http://www.commodore.ca/windows/exchange/how_to_upgrade_exchange_2007_to_exchange_2010_in_2hours.htm

     

    Regards,


    Rashid Kamal, MCP, MCSA, MCTS - Exchange, JNCIA, JNCIS (If you find it useful, mark this 'As Answer', so that it can be helpful to other community members reading the thread)
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 10:15 AM

All replies

  • I have described all the steps here: http://windowsadmin.info/viewtopic.php?f=20&t=181&sid=f035bf30a61b78769f099b28280dbf76
    Regards from www.windowsadmin.info | www.blog.windowsadmin.info
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Wednesday, January 04, 2012 5:46 AM
    Moderator
  • Hi

    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.

    To install prerequisite follow the below link

    http://msunified.net/2009/10/30/exchange-2010-prerequisites-on-server-2008-r2/

     

    Regards

    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Wednesday, January 04, 2012 6:58 AM
  • How would i confiuge below details:

     

    1. Install CAS server role servers and configure per 2010 design. Validate function-ality.
    2. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 5:11 AM
  • The steps for introducing Exchange 2010 into the environment are:

    Note: These steps do not discuss how to set up your CAS2010 servers in a load balancing array. 

    1. In order to support external client coexistence with CAS2010 and legacy Exchange in your "Internet Facing AD Site", you will (potentially) need to acquire a new commercial certificate.  As a best practice, Microsoft recommends utilizing a certificate that supports Subject Alternative Names; however, you can utilize a wildcard certificate as well.

    This commercial certificate that will be leveraged by external clients will contain at a minimum three SAN values (note that other scenarios may require you to add additional values):

    1. mail.contoso.com (your primary OWA/EAS/OA access URL)
    2. autodiscover.contoso.com
    3. legacy.contoso.com (your OWA/EAS namespace for legacy mailbox access)

    Prior to Windows Vista SP1, the Windows RPC/HTTP client-side component required that the Subject Name (aka Common Name) on the certificate match the "Certificate Principal Name" configured for the Outlook Anywhere connection in the Outlook profile. Therefore, as a best practice, you should ensure that mail.contoso.com is listed as the Subject Name in your certificate unless you plan on changing the configuration which can be achieved by using the Set-OutlookProvider cmdlet with the -EXPR parameter as described in http://msexchangeteam.com/archive/2008/09/29/449921.aspx.

    2. Ensure all Exchange 2007 CAS within the organization are at Service Pack 2, all Exchange 2003 servers (if they exist) are at Service Pack 2, and that all Exchange 2007 Mailbox, Hub Transport, and Unified Messaging servers are at Service Pack 2 in the "Internet Facing AD Site". Also, ensure you meet all the forest/domain pre-requisites.

    3. Install CAS2010 and configure it accordingly:

    • During the installation of CAS2010 you have the option to enter the external namespace that will be used for the virtual directories. You can enter this value in both the graphical user interface or the command-line setup:
      • For the graphical user interface setup experience of CAS2010 you are asked to configure a Client Access external domain. At this point you canter the domain name of mail.contoso.com.
      • If installing via the command line, you can utilize the setup property /ExternalCASServerDomain and specify mail.contoso.com
    • If you haven't already done so, install the RPC over HTTP proxy component.  You can do this utilizing the ServerManagerCmd tool: ServerManagerCmd.exe -i RPC-over-HTTP-proxy
    • Configure your OWA settings appropriately (e.g. forms based authentication vs. basic authentication). For the purpose of this document, the default OWA settings are assumed.
    • Configure your EAS authentication settings appropriately (e.g. Basic vs. certificate authentication). For the purposes of this document, the default authentication mechanism, basic authentication, is assumed.
    • Enable Outlook Anywhere (for the purposes of this document, the default authentication settings are assumed): Enable-OutlookAnywhere -Server: -ExternalHostName:mail.contoso.com -SSLOffloading $false

    4. If you chose to not specify the external domain name for CAS during setup, you will need to enable the following ExternalURLs to ensure that clients that leverage Autodiscover function correctly:

    5. To ensure that Outlook Web Access functions correctly, you will need to enable the following URLs:

    6. If you have Exchange 2007 deployed in "Non-Internet Facing AD Sites" then you must copy the Exchange 2007 OWA binaries to CAS2010:

    • On the CAS2010 server(s), establish a connection to the CAS2007 server's drive that contains the Exchange binaries and navigate to the \Client Access\OWA directory (e.g. \\cas2007\c$\Program Files\Microsoft\Exchange Server\Client Access\Owa).
    • Copy the highest version folder (e.g. 8.2.140.0) from the CAS2007 to CAS2010 Exchange binaries \Client Access\OWA directory (e.g. C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa).
    • Execute IISReset on all the CAS2010 machines.

    7. For your Outlook clients, you can configure CAS2010 to participate in an RPC Client Access Service array:

    • Create a load balancing array for CAS2010, if one has not already been created.
    • Create a DNS entry in your internal DNS infrastructure that resolves to the Virtual IP Address (VIP) of the CAS load balancing array. The DNS entry, for example, could be outlook.contoso.com.
    • Configure your load balancing array to load balance the MAPI RPC ports:
      • TCP 135
      • TCP 1024-65535
    • Run the following cmdlet to create the Client Access Service array: New-ClientAccessArray -Name outlook.contoso.com -FQDN outlook.contoso.com -Site "Internet Facing AD Site"

    Regards

     

    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 5:20 AM
  • I would recommend you to read about these articles:

    Exchange 2007 - Planning Roadmap for Upgrade and Coexistence

    http://technet.microsoft.com/en-us/library/dd638158.aspx

    Understanding Upgrade from Exchange 2007 to Exchange 2010

    http://technet.microsoft.com/en-us/library/ff805041.aspx

    Transitioning Client Access to Exchange Server 2010

    http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx


    Jack Zhou
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 6:30 AM
    Moderator
  • Hi,

     

    Step by Step procedure of migrating Exchange 2007 to Exchange 2010 is as follows,


    How to Upgrade Single Server Exchange 2007 to Exchange 2010

    - PREWORK
    - EXCHANGE 2010 CORE INSTALL
    - CONFIGURE EXCHANGE 2010 & MIGRATE YOUR DATA
    - MOVING AN EXCHANGE 2007 CERTIFICATE TO EXCHANGE 2010
    - ANTISPAM
    - DECOMMISSION OLD EXCHANGE 2007
    - VERIFICATION

    Check out the following link for detail steps,

     

    http://www.commodore.ca/windows/exchange/how_to_upgrade_exchange_2007_to_exchange_2010_in_2hours.htm

     

    Regards,


    Rashid Kamal, MCP, MCSA, MCTS - Exchange, JNCIA, JNCIS (If you find it useful, mark this 'As Answer', so that it can be helpful to other community members reading the thread)
    • Marked as answer by Gautam Ji Friday, January 06, 2012 1:26 PM
    Thursday, January 05, 2012 10:15 AM
  • Is there any updated steps for Exchange Server 2007 to 2013 ?

    /* Server Support Specialist */

    Tuesday, November 05, 2013 7:11 AM