I don't have any documentation online, but here is an overview (I am using the
built in Exchange cmdlets, so there may be someone else that has documented
this online):
1. Exchange Migration
a. A few days before actual migration:
i. Run
Exchange Prepare-MoveRequest cmdlets on ALL production mailboxes (if you don't
do all, users will have issues sending to users who were not included in this
"prep").
ii. Use ADMT
to sync their passwords (we are not migrating a lot of their older settings and
hence don't need to sync any other attributes - this will differ from your
scenario).
b. Production night(s)
i. Run
Exchange Remote-MoveMailbox cmdlet on the mailboxes that are being moved that
evening.
c. Client Side
i. Remove
old Outlook profile, add new Outlook profile to point to new server. Do you
attempt to reconfigure the server settings in the existing Outlook profiles.
From what I recall when we first did this about 2 years ago, it caused both
client side and server issues (client side mailbox kept "flickering" and
showing and deleting folders, and server logs ballooned - not sure what exactly
was the problem, but we stopped attempting to reconfigure the existing profile
and haven't had any problems since).
2. AD Migration
a. Resources will be migrated to new domain.
b. When the users get their new Win7 computers, they will be logging into
new domain and will have access to their old resources.
The Exchange migration part we have done since we've been doing that for some
time now successfully (both Exchange 2003 and Exchange 2007 sources). The AD
migration part is something we are still formulating now - our task has been to
vacate the existing Exchange servers in each forest first, and then work on the
rest of the AD migration part next.
There are likely other ways to approach this too, but this is the approach that
we happen to be using.
-Aakash Shah
From: [email protected] [mailto:[email protected]] On
Behalf Of Ken Cornetet
Sent: Monday, February 24, 2014 5:27 AM
To: [email protected]
Subject: [NTSysADM] RE: ADMT & Exchange
Can you provide pointers to the documentation you are using to do this?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Aakash Shah
Sent: Friday, February 21, 2014 10:56 PM
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] RE: ADMT & Exchange
Unless I misunderstood your question, yes, this is possible. We are doing
something similar now with a Win7 upgrade project. We are moving their
mailboxes first (we're currently in this phase), and will then be setting up
the users on the new forest with their Win7 computers after we've migrated
their file server resources over.
-Aakash Shah
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Ken Cornetet
Sent: Friday, February 21, 2014 11:15 AM
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] ADMT & Exchange
I'd think this would be a common question, but my google-fu has failed me.
Here's my situation:
Given a forest with users with Exchange mailboxes, I need to migrate the users
to a new forest and move their mailboxes to new Exchange servers in the new
forest.
My question is: Is there any way to NOT do both migrations at the same time? In
other words, can I move their mailboxes the weekend before I do the user
migration? Or vice-versa - move the mailboxes the weekend after the migration?
All of the documentation I can find on using ADMT to migrate exchange enabled
users talks about moving mailboxes coincident with moving the user.
As part of a company spin-off, I have several locations with hundreds of users
each where I need to migrate users to a new forest. I doubt I'll be able to get
more than a weekend at each location to complete the user migration, so I'd
prefer to do the mailbox migration done either before or after the user
migration.
I understand there will be GAL sync issues to address - I can handle that.
