Re: Win2k3 and E2k3 migration to SBS 2003

Hi Kevin

If you are a Registered Partner you might have better luck in the
microsoft.private.directaccess.smallbizserver2003 newsgroup where the MS
engineers will answer your question. Most users here have given up on ADMT
and switched to Swing Migration. Alternately you might want to put in a
support call to PSS for help.

--
Frank McCallister SBS MVP
COMPUMAC
"Kevin" <donotemail@xxxxxxxxxx> wrote in message
news:esNUlyhJGHA.1424@xxxxxxxxxxxxxxxxxxxxxxx
> Susan,
>
> Thank you for your reply.
>
> I've heard a lot about the swing kits and I look forward to trying them in
> future projects. At the moment though, I'm going with what has worked for
> me in the past. Granted, it's not working the way I expect now but rather
> than bailing and redesigning from the beginning (and learning a new
> process), respectfully, I'm seeking insight on my original post. I hope
> you understand.
>
> It seems I'm running up against a Uniqueness Conflict with Exchange
> Migration Wizard (MigWiz). I'm just not sure why in this case. Where
> SIDHistory has been migrated, it is my understanding that the MigWiz will
> match based on SID. I have confirmed with ADSIEdit that the SIDHistory
> property is populated on those ADMT migrated accounts.
>
> I have found that if I migrate using MigWiz first, it will create an
> account, mail enable it, and copy mailbox data. I have also seen that I
> can then use the ADMT to merge (including SIDHistory) with the account
> created by MigWiz. I can deal with this but I would like to understand
> why when all the documentation that I've uncovered in my research has
> indicated that you generally use ADMT first, then MigWiz. It has worked
> that way in past migrations that I have performed with great success,
> using MS tools and scripts that I had written. This is why I went the
> same route this time. I had performed the process before (though slightly
> different in that before I moved from Exchange 5.5 instead of from
> Exchange 2003) so had a documented and tested process as a basis for this
> migration.
>
> Do you have any further insight?
>
> Thanks.
>
> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
> wrote in message news:O1MCtZhJGHA.2212@xxxxxxxxxxxxxxxxxxxxxxx
>> Uh ...try www.sbsmigration.com or
>>
>> http://support.microsoft.com/kb/884453/en-us
>>
>> ADMT isn't the way to go
>>
>> Kevin wrote:
>>
>>>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
    ... 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)
  • Win2k3 and E2k3 migration to SBS 2003
    ... 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.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)