Migration and Consolidation

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

genius54m - 15 Sep 2006 17:52 GMT

I am in the process of consolidating three separate forests with 3 different
exchange organizations. (2 exchange 2003 deployments and 1 exchange 5.5.) We
are consolidating to one 1 root domain , three child domains, and one
exchange deployment. What is the best solution to migrating all three
separate exchange deployments to 1 exchange 2003 deployment?

Reply to this Message

Paul Robichaux [MVP-Exchange] - 15 Sep 2006 18:35 GMT

> I am in the process of consolidating three separate forests with 3 different
> exchange organizations. (2 exchange 2003 deployments and 1 exchange 5.5.) We
> are consolidating to one 1 root domain , three child domains, and one
> exchange deployment. What is the best solution to migrating all three
> separate exchange deployments to 1 exchange 2003 deployment?

I admit to being biased, but you should probably start by reading the MS
solution accelerator for Exchange consolidation and migration at
<http://www.robichaux.net/blog/2006/09/exchange_migration_solution_accele
rator.php>. That should give you a pretty good start.

Cheers,
-Paul

Reply to this Message

genius54m - 15 Sep 2006 22:59 GMT

hey Paul, I made a bit of a mistake in the details. The migration was going
to be targeted to 1 roort domain, 1child. All existing orgs would be inserted
into an OU structure. "If this changes your outlook and opinion" :) Thanks
for the direction. I am currently researching the accelerator, I will give
you my feedback once I am done.

> > I am in the process of consolidating three separate forests with 3 different
> > exchange organizations. (2 exchange 2003 deployments and 1 exchange 5.5.) We
[quoted text clipped - 9 lines]
> Cheers,
> -Paul

Reply to this Message

John Fullbright [MVP] - 19 Sep 2006 20:55 GMT

I think Paul is leading you down the right path. As you travel that route,
be aware of what synchronization tools are currently in place. Phase one of
a consolidation effort is really directory synchronization, and this is
probably the most difficult. You may want to look at third party vendors
that specialize in exchange migrations, like Quest, for tools/services. If
you use Quest tools, there is one tool for migrating from 5.5, and another
for migrating from Echange 2003. Careful planning that takes into account
the current directory replication strategy and tools is required to ensure a
successful outcome. I use Quest as an example because I most familiar with
that toolset, however the general advice should apply to other vendors as
well.

good luck

John

>I am in the process of consolidating three separate forests with 3
>different
[quoted text clipped - 3 lines]
> exchange deployment. What is the best solution to migrating all three
> separate exchange deployments to 1 exchange 2003 deployment?

Reply to this Message

genius54m - 19 Sep 2006 22:03 GMT

I appreciate your reply. I am so happyu that I have found an expert who has
utilized quest software. I am actuall y utilizing this software product for
this particular migration. Do you have any best practices or strategies for
its usage. Also, as in the post, we are going to be consolidating to 1 root,
1 child. Do you have any info to support this config. Your help is extremely
beneficial. again thanks for the input

> I think Paul is leading you down the right path. As you travel that route,
> be aware of what synchronization tools are currently in place. Phase one of
[quoted text clipped - 19 lines]
> > exchange deployment. What is the best solution to migrating all three
> > separate exchange deployments to 1 exchange 2003 deployment?

Reply to this Message

Al Mulnick - 19 Sep 2006 23:53 GMT

Something that's missing from the conversation is your list of goals before,
during, and after the migration. What I'm saying is that you should have
some sort of list of goals to achieve in your migration knowing that some
states (coexistence) are temporary while end state is much more important.
For example, what is the goal of the coexistence state with regards to the
end user? Should that user know that they have been migrated? Should it be
partially incumbent on the end user to absorb some of that? Or should it be
so seamless the most common comment is "what migration?"
What needs to occur for that goal to happen? Are there user maps (identity
from source to identity in target that need to be mapped?)

After the migration, what should the users see? Should they be able to have
the exact same mail in their inbox? Should they be able to reply to a piece
of email and should it be able to be routed as if nothing ever happened?

What needs to occur for these goals to be realized? Are they important?
What other goals are there? What about F/B time? OWA access? All during each
stage?

And so on.

>I appreciate your reply. I am so happyu that I have found an expert who has
> utilized quest software. I am actuall y utilizing this software product
[quoted text clipped - 38 lines]
>> > exchange deployment. What is the best solution to migrating all three
>> > separate exchange deployments to 1 exchange 2003 deployment?

Reply to this Message