[Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Migrate from Exchange '07 to Exchange '07

I am in the process of consolidating four Exchange (three '07 and one '03) systems (as in Organizations in separate AD forests) into a new Exchange 2007sp1 system in a different forest/AD.  Three of the four systems are small (<75 users each ) and we have already established a complete trust between those three forests.

The other organization is being split off of a system after a merger with the company hosting the new Exchange '07 system I'm building and they are telling me that they will only export all of the user messages, calendar, contacts, etc. to .PST files...there will be a little over 2,000 of these .PST files.

Short of manually importing all of the "stuff" from each .PST file into the corresponding AD/Exchange user in our new target system, is there any sort of scripting or utility I can use to "suck" all of the contents from the 2,000+ user .PST files into my new Exchange.  I've suggested giving the .PST files to the users (who are already in the target AD forest) and let them open those .PST files but that was not accepted.

Thanks in advance for assistance!
  • 3
1 Solution
Well if export / import is the only way, you could use ExMerge to send all the stuff back into the requiste mailboxes on the new Exchange 2007 server. Of course this assumes their exchange directory names/aliases match between the old and new AD domains.
ZENandEmailguyAuthor Commented:
If I can get the source company with the 2,000 mailboxes to cooperate and let us create a complete trust relationship between the source forest and the target forest and assuming the AD names/aliases match what utility to migrate the mailboxes between source E2K7 and target E2K7 do you recommend/use?

ZENandEmailguyAuthor Commented:
We got a ruling finally from the company "owning" the 2,000 mailboxes.  They are going to provide .PST files only...no trust relationship.  So now we have an issue that is two fold:

1) The exported .PST filename needs to match the AD alias in our AD ("target company") so we're planning to write a script that will query a file with an AD export from our AD and match it up to the .PST file we're provided for each user.  It will then change the filename.PST.  From everything we're finding, a PowerShell script will import the contents of the .PST files as long as the .PST file matches the AD alias name.

2) For a period of potentially several months, the users from the "owning" company will continue to use the AD and Windows file/print of the "owning" company but use the "target company" Exchange system/mailboxes.  We're not sure how Outlook 2007 clients will behave since the user profile will be pointed to the "owning" domain but yet need the mailbox out of the "target company" domain.  OWA will be easy as we just send a link to our OWA servers.

ZENandEmailguyAuthor Commented:
An additional question that goes along with this post:

I built the Exchange organization with Exchange 2003 to support a gateway between GroupWise 7.x and Exchange.  I will need to remove the gateway at some point and as such remove Exchange 2003 server from the Organization, making it only Exchange 2007sp1.

Is it easy to remove the server that was used to build/create the Exchange org?

I'll award points asap on this.

Thanks for the help!


Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

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