Solved

Using Quest to migrate mailboxes between Exchange orgs

Posted on 2010-08-31
1
886 Views
Last Modified: 2013-11-25
Hi All

We are soon going to start work on the following project and I was hoping someone could provide me with some background info help us kick off :)

Basically, we are running Exchange 2003/AD 2003 and are migrating to Exchange 2010/ AD 2008. We have created a new AD forest running 2008 DC's with 2010 Exchange servers.

Now I am looking at how we're going to move the mailboxes from 2003 to 2010. AFAIK, Exchange does not support mailbox moves between different orgs. I understand Quest has tools that can carry this out well.

Question1: When Quest 'moves' the mailbox from the 2003 org to the 2010 org, does anyone know how that is carried out? Does it make a copy in the new org then delete the original once all the data has copied over? Or is it a bit more complicated than that?

Question2: Rather than migrate the AD accounts, we are creating new AD accounts in the second forest and re-ACL'ing. I'm curious - when Quest migrates the mailboxes, how does this affect the msExch attributes of the two AD accounts?

0
Comment
Question by:smith1974
[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
1 Comment
 
LVL 4

Accepted Solution

by:
MONSTA2008 earned 500 total points
ID: 33573002
Having done this in the past with Quest's solutions the best thing is that Quest will copy the contents of the mailboxes, its permissions and settings to the new target in pretty seamless fashion.  You will definately need to configure your environment so that Quest can map the SIDs between the source and target objects.  This is pretty well spelled out in their product documentation.  

The other cool aspect of their stuff is that it makes the migration process pretty seamless for difficult tasks such as maintaining the user's desktop and Outlook profiles as well as re-ACLing any servers you need to migrate between the two worlds.

The only bit of advice I can give is to seriously consider engaging Quest's professional services for this type of work - at least to help you develop and validate the process as it can become quite complex at the end of the day.  Once you have the process down you can tear through doing the bulk of the migration work on your own.  However, that initial investment in the Quest professional services was invaluable towards the success of our past projects.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
how to add IIS SMTP to handle application/Scanner relays into office 365.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

688 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