• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 591
  • Last Modified:

Request for solution on migrating Exchange 2003 and 2007 to Exchange 2010

Migrating multiple AD forest/Exchange environment into single AD Forest/exchange 2010. Following is a brief description: Exchange 2003 SP2/window 2003  and 2007 SP1/windows 2003 SP2 (64 bit) migrating to Exchange 2010/Windows 2008 . Most of existing Exchange 2003 servers are running Mixed mode,while Exchange 2007 SP1 is running Native mode. One of the 2003 AD is running in "Interim" mode, while other AD 2003 are running in "Native" mode. All users AD migration to 2008 is complete via ADMT tool

Looking for following migration details for this complex environment.
1) During coexistance how calendering/free busy could be avialable unitl migration is complete. (Any free 3rd party tool. Can't use Quest Software)
2) For moving users mailboxes using Move-Request cmdlet, are there any pre-requisties ?. for Example, during coexistance does Exchange 2010 to be installed in Mixed mode
3)Using Move-Request cmdlet in Exchange 2007, Does Exchange 2007 require SP2 upgrade
4)Any Exchange upgrades required for sharing calendar/freebusy during migration  
5) Can the Move-Request cmdlet be scripted to run for list of users (Cross-Forest move)
6) After mailbox move,any issues accessing legacy mail/calendar items in new Exchange/AD forest ?
7) After mailbox move, any issues responding to legacy mail/calendar items from new Exchange environment ?
8)If there are issues what are the work around for 6) & 7)
9)Tool(s) to migrate DL's/Contacts
10)Any issues migrating DL's, Does DL retains all members and does DL and members email address changes to reflect new email address
11)Tool(s) to migrate Calendar resources/rooms and retaining owners
Assistance, direction and recommendation will be appreciated
1 Solution
We're in the process of doing this now.  I worked with a MS rep who gave me lots of good documentation:

First step would be to prepare domain. Please see link below:
http://technet.microsoft.com/en-us/library/bb125224.aspx - Prepare Active Directory and Domains

This link has information about supported coexistence scenarios and requirements for directory servers and some recommendations.
http://technet.microsoft.com/en-us/library/aa996719.aspx - Exchange 2010 System Requirements

This link has information about prerequisites required before installing exchange.
http://technet.microsoft.com/en-us/library/bb691354.aspx - Exchange 2010 Prerequisites

Here you can download EXPDA (Exchange Pre-Deployment Analyzer)
http://www.microsoft.com/downloads/details.aspx?FamilyID=88b304e7-9912-4cb0-8ead-7479dab1abf2&displaylang=en - Exchange Pre-Deployment Analyzer
We can use the Exchange Pre-Deployment Analyzer to perform an overall topology readiness scan of your environment

http://technet.microsoft.com/en-us/library/dd638130.aspx - Install Exchange 2010 in an Existing Exchange 2003 Organization

http://technet.microsoft.com/en-us/library/aa998604.aspx - lists the scenarios in which coexistence between Exchange 2010 and earlier versions of Exchange are supported and information about upgrading your organization to Exchange 2010

http://technet.microsoft.com/en-us/library/dd298136.aspx - What's New in Exchange 2010
http://www.microsoft.com/exchange/2010/en/us/licensing.aspx#ExServCom – Below are the topics within this link.
License Types
Exchange 2010 Server
Comparison to Earlier Versions
Prerequisites for Exchange 2010 Server
Exchange 2010 Client Access Licenses (CALs)
Comparison to Earlier Versions
Prerequisites for Exchange 2010 Client Access Licenses (CALs)
Next Steps - Evaluation, Volume Licensing, Pricing

http://technet.microsoft.com/en-us/library/ee681665.aspx - Exchange 2010 Deployment Assistant
Microsoft Exchange Server 2010 introduces the Exchange Deployment Assistant or ExDeploy, a new Web-based tool that can help you with your Exchange deployment. ExDeploy asks you a few questions about your current environment and then generates a custom checklist and procedures that help simplify your deployment.
You can use ExDeploy for the following scenarios:
Upgrade from Exchange Server 2003
Upgrade from Exchange 2007
Upgrade from mixed Exchange 2003 and Exchange Server 2007
New installation of Exchange 2010
http://msexchangeteam.com/archive/2009/11/09/453117.aspx - Exchange 2010 Mailbox Server Role Requirements Calculator
http://blogs.techrepublic.com.com/datacenter/?p=1380 - Reduce hardware needs and ease administration with Exchange 2010
http://technet.microsoft.com/en-us/library/aa998911.aspx - Discontinued Features and De-Emphasized Functionality
http://technet.microsoft.com/en-us/library/dd298026.aspx - Overview of Exchange 2010 Server Roles
http://technet.microsoft.com/en-us/library/dd346701.aspx - Understanding Server Role Ratios and Exchange Performance

Understanding Mobile Phones
Exchange ActiveSync Mobile Phones and Compatible Features
lbeach94Author Commented:
Hi Waleeda & jhyiesla, thanks for the response back and links.

Can either of you share your experiences during migration which pertains specifically to mailbox moves which contain legacy domain emails and calendar. Are there any issues accessing/responding to legacy domain emails or calendar meetings.

Still not clear on prereqs of Move-Request cmdlet ,assuming the complexity of my environment. Do you have any Move-Request cmdlet prereqs requirement for its usage?,thx
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

We haven't fully rolled this out in production so I can't speak to the actual migration.

In my test environment I set up a DC, an Exchange 2003 server and an Exchange 2010 server as well as a workstation. I tried to emulate my current production environment as much as possible, but with only a small number of users and mailboxes. Within that environment I really didn't have any problems having the both up at the same time and before, during, and after migration I was able to get emails from any user with both Outlook and OWA without issue no matter where the mailbox was and email to and from users also worked well.

One thing I couldn't test, since it was a sandbox environment, was connectivity to the Internet and how the whole external DNS and MX record thing will work. I think I know what to do, but it will be a guess until I actually do it.

One command that I found that I had to do before CAS would work in both directions between the old and new servers was:

Set-OWAVirtualDirectory -identity "CASSServer\owa (default web site)" -Exchange 2003URL https://legacymail.contoso.com/exchange   substituting in my info.
I don't think his questions were totally answered, but the detailed step by step that I gave him should be a great starting point for his basic premise and that's moving from 2003-2010.
Question PAQ'd and stored in the solution database.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now