The approach we took in our environment was: 1. Created 2 way forest trust.
2. Ran Prepare-MoveRequest for the first iteration. 3. Used ADMT with password sync to copy user objects from old domain to new domain (we first confirmed that the users didn't already have existing accounts). 4. Ran New-MoveRequest with the RemoteLegacy switch. This was done afterhours and users had no access to their email during this time. The next morning, we had a mechanism in place to delete their existing Outlook profile, and set up a new Outlook profile that pointed to the new server. We found that bad things happened if we tried to force it to use the same Outlook profile. This worked very well for us. It also maintained the X500 addresses and hence the user's cached email contacts worked correctly afterwards (so it was a relatively seamless transition). It also maintained delegate settings. However, it was important that all of the users are prepped (so it creates a mail user object with the X500 address). If not, then if a user who has moved attempts to email a person who has not been prepped, they will get an undeliverable. -Aakash Shah From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, September 9, 2013 4:31 PM To: [email protected] Subject: RE: [Exchange] Exporting Data from Exchange 2003 to Exchange 2010 Huh. I didn't know about that. Go for it. :) I'm a little concerned about the matching criteria, but since I've never used the cmdlet, I can't speak from experience. It looks promising. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aakash Shah Sent: Monday, September 9, 2013 7:22 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] Exporting Data from Exchange 2003 to Exchange 2010 Michael/Community: Just curious, why couldn't Prepare-MoveRequest and New-MoveRequest with the RemoteLegacy switch be used in this specific scenario by using the instructions at http://technet.microsoft.com/en-us/library/dd876952%28v=exchg.141%29.aspx? I've successfully used this to help migrate users from Exchange 2003 in one forest to Exchange 2010 in a separate forest, but perhaps our scenario was different and so I was curious to learn under what circumstances this approach cannot be used. Thanks! -Aakash Shah From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, September 9, 2013 12:02 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] Exporting Data from Exchange 2003 to Exchange 2010 Without a third-party tool, that is correct. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of John Matteson Sent: Monday, September 9, 2013 2:36 PM To: exchange Subject: [Exchange] Exporting Data from Exchange 2003 to Exchange 2010 Good afternoon all: This is request for a sanity check. I have a customer that is running Exchange 2003 in a separate forest, The forest and Exchange installation is part of an M & A. We currently have co-existence up and running, GAL SYNC via IIFP SP2 and IOREPL. What I need to check is that there is no way to directly migrate Exchange 2003 data into Exchange 2010. It has to have some intermediary form, such as a PST file. For example, I would need to export the data from Exchange 2003 via EXMERGE into a PST file, then import it into a properly prepared mailbox/AD account using a Powershell cmdlet. Comments and suggestions are always welcomed. John M.
