Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2014-12-13
3
Medium Priority
?
222 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
[X]
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
  • 2
3 Comments
 
LVL 18

Assisted Solution

by:irweazelwallis
irweazelwallis 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 17

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:
irweazelwallis 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

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

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

New style of hardware planning for Microsoft Exchange server.
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

721 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