?
Solved

Exchange 2007 resource forest migration, back to account forest, with Exchange 2013

Posted on 2014-12-13
3
Medium Priority
?
227 Views
Last Modified: 2014-12-21
Hi everyone,

i have a question regarding exchange 2007 resource forest migration, back to account forest.

Situation is:
Forest "source.com" is account forest, with all users accounts.
Forest "exchange.com" is resource forest, in wich exchange 2007 is hosted. There is a 2 way forest trust, and users from "source.com" forest are using linked mailboxes.

Plan is to install exchange 2013 sp1 in "source.com" and to bring those mailboxes, public folders, etc, back to that forest. Remove forest trust and stay on new exchange.
So this is kinda mix od resource forest and cross forest migration.

What i am not shure of is:
1. User accounts. Users in source.com are already created, and cant be deleted. What tool/procedure should i use to prepare them, so that mailboxes can be attached to them?
      I was thinking on using ADMT, but i already have accounts. Prepare-moverequest.ps1 wont work on non-mail enabled accounts. Should i create mailboxes on new exchange and then use that script to prepare accounts? Will that allow me to migrate mailbox conntent from 2007 to 2013?
      Any idea :)
2. Public folders. As i read, cross-forest PF migration is not supported in 2013. Guess i can install 2007 or 2010 source.com to migrate them, and after that export them to pst and import into new exchange 2013?
      Any idea :)
3. If procedure 1 for user account works, and creating mailboxes for users, and using script works, will users be able to access their mailbox when migration is in process?
4. In any way PF will be unavailable untill migration is over?

All in all, has anyone done this, any nice links. tips or so to share?

Regards,
0
Comment
Question by:Ivan
  • 2
3 Comments
 
LVL 18

Assisted Solution

by:Chris
Chris earned 1500 total points
ID: 40498327
Do you have a shared name space on the two exchange orgs?
There are some complications around that

I am in the process of doing a similar migration and have a plan which is export and import. Basically give the user a new mailbox to their account and get them working and dealing with new mail and in the background have the old mail data getting imported.
We have done away with public folders so have no issues with that, the main problem we have come across is shared mailbox access and that because of the number of users, too many to move in one go.
0
 
LVL 18

Author Comment

by:Ivan
ID: 40498351
Hi,

same domain name will be used on both, when new exchange is deployed, that is until everything is migrated to 2013. Then forest trust will be removed. Guess I can create send/ receive connectors so that mail is forwarded from 2007 to 2013 until everything is migrated? Like internal relay domain..

If I create new users then I would have to manually grant group membership and such? This is 150 users, so not rely much, but not little as well :)

PF are pain..still not sure how will I migrate them. Client ofc would like that there is no user interaption.
0
 
LVL 18

Accepted Solution

by:
Chris earned 1500 total points
ID: 40498615
With 150 users you could do in one go over a weekend which is much easier than trying to maintain multiple exchanges.
If you don't go in one then...
Things you need to think about is distribution lists and there membership
Send as, send on behalf and full mail box access
Free busy, a shared name space means it's not possible
I
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Question has a verified solution.

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

This article describes Top 9 Exchange troubleshooting utilities that every Exchange Administrator should know. Most of the utilities are available free of cost. List of tools that I am going to explain in this article are:   Microsoft Remote Con…
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses
Course of the Month6 days, 12 hours left to enroll

594 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