Win2k3 and E2k3 migration to SBS 2003

I'm performing a migration from Windows Server 2003/Exchange 2003 to a
Windows SBS 2003 server running Exchange 2003. Since I can't create trusts,
I'm using an identical account with full privileges in both the source and
target forests. I'm using ADMT v3 to migrate group, user, and computer
accounts (in that order) and then using Exchange Migration Wizard (MigWiz)
in clone mode to copy mailbox data.

My research has shown that migrating accounts with ADMT and then using the
MigWiz is the proper way to go. I've done this before using ADMT v2 in
another migration project and the MigWiz matched the accounts to the already
migrated ADMT accounts. This time, however, I get the following message
from MigWiz when I select a user that has already been migrated with the
ADMT:

"One or more users have names that conflict with other directory objects.
Unique names have been chosen and will be presented to you for your
approval."

I'm not sure why MigWiz is not matching to the ADMT migrated accounts. Any
ideas on what I can do to fix this? I didn't notice any references to a
change in behaviour between ADMT v2 and v3 that would affect this...

Thanks for any help.

Kevin



.

Relevant Pages

  • Re: AD merge with exchange 2007 srv, can ADMT do it?
    ... > ADMT will do user and computer account migration. ... > "Exchange cross forest migration" and you will find some documentations. ... I usually do put together step by step docs such as this, to help folks in the newsgroups, but I haven't yet with this procedure because besides being scattered and the procedure having many facets, my notes are customer specific with domain names, user accounts, passwords, etc, that it will take me some time to go through to compile it into one doc, and I do apologize I am short on time to do anything with this at this point. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Most users here have given up on ADMT ... and switched to Swing Migration. ... > Migration Wizard (MigWiz). ... >>>accounts and then using Exchange Migration Wizard ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Migration Wizard (MigWiz). ... property is populated on those ADMT migrated accounts. ... and tested process as a basis for this migration. ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... It seems I'm running up against a Uniqueness Conflict with Exchange Migration Wizard (MigWiz). ... I have confirmed with ADSIEdit that the SIDHistory property is populated on those ADMT migrated accounts. ... I have also seen that I can then use the ADMT to merge with the account created by MigWiz. ... I had performed the process before so had a documented and tested process as a basis for this migration. ...
    (microsoft.public.windows.server.sbs)
  • Interorg Migration problem
    ... My research has shown that migrating accounts with ADMT and then using the ... MigWiz is the proper way to go. ... another migration project and the MigWiz matched the accounts to the already ...
    (microsoft.public.exchange.setup)
Loading