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

Posted on 2011-03-16
Last Modified: 2012-05-11
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
Question by:lbeach94
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 28

Expert Comment

ID: 35150911
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: - Prepare Active Directory and Domains

This link has information about supported coexistence scenarios and requirements for directory servers and some recommendations. - Exchange 2010 System Requirements

This link has information about prerequisites required before installing exchange. - Exchange 2010 Prerequisites

Here you can download EXPDA (Exchange Pre-Deployment Analyzer) - Exchange Pre-Deployment Analyzer
We can use the Exchange Pre-Deployment Analyzer to perform an overall topology readiness scan of your environment - Install Exchange 2010 in an Existing Exchange 2003 Organization - 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 - What's New in Exchange 2010 – 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 - 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 - Exchange 2010 Mailbox Server Role Requirements Calculator - Reduce hardware needs and ease administration with Exchange 2010 - Discontinued Features and De-Emphasized Functionality - Overview of Exchange 2010 Server Roles - Understanding Server Role Ratios and Exchange Performance
Understanding Mobile Phones
Exchange ActiveSync Mobile Phones and Compatible Features

Author Comment

ID: 35166759
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
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

LVL 28

Expert Comment

ID: 35166875
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   substituting in my info.
LVL 28

Expert Comment

ID: 35923846
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.

Accepted Solution

ee_auto earned 0 total points
ID: 36001481
Question PAQ'd and stored in the solution database.

Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

626 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question