Re: Migrate 2003 users to another 2003 box



Matthew's suggestion is good but I would really suggest that you consider
merging AD forests. The benefits you gain from Exchange consolidation hold
true for AD consolidation and tackling the project as a whole will make it
all simpler.

Nue
"Matthew Wade" <matthew.wade@xxxxxxxxxxx> wrote in message
news:un3H%23drGGHA.2040@xxxxxxxxxxxxxxxxxxxxxxx
> You may want to try to use the ADMT (Active Directory Migration Tool) to
> migrate all the user accounts first. This will populate a SID history
> attribute...then run the mailbox migration utility...which will map the
> mailbox to the AD account using the SID history. We used this approach
> when migration our 5.5 system to a completly seperate 2003 organization.
> It worked great for us.
>
> Matthew Wade
> MCSE+M, MCSA+M
> "gstar" <gary.brett@xxxxxxxxx> wrote in message
> news:1137426721.021620.145740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Hi,
>> After a recent company merge we have decided to merge both Exchange
>> 2003 servers data. The server will host all our merged staffs email
>> accounts, but they will continue to use individual AD servers for
>> there respective domain logons.... Both offices are connected via a
>> leased line VPN connection and I have enabled domain trusts as
>> required, WINS & DNS is resolving fine on both servers.
>> I tried using the Exchange migration tool but the wizard falls over
>> during the "Migration Information / Account Migration section and
>> returns no event log errors. However it does return a "data not valid"
>> error and stops the migration there..
>> Is there an easy way to migrate users accounts or it is simply adding
>> the new users and forwarding all mail from their previous Exchange box
>> to the new one?
>> Thanx
>> G
>>
>
>


.



Relevant Pages

  • Problem sending mail from Exchange 5.5 to Exchange 2003
    ... The difference between this migration ... Exchange 2003 and 5.5 mailbox servers are on the same ... When migrating mailboxes home- and commonareas are ...
    (microsoft.public.exchange.misc)
  • RE: NT4 upgrade to 2k3 Server with WAN
    ... However, in order to keep the thread clean, please open up a new thread and ... Our NT4.0 servers are very outdated ... I have new exchange 2k3 ready to be installed and will ... >> You can use the migration or upgrade method to win2k3 domain. ...
    (microsoft.public.windows.server.migration)
  • Re: reaching the 50 user barrier on SBS 2000
    ... transition pack after that if it looks like we are going to outgrow early... ... we have around 45 user accounts now on the system - but not all of them are ... > The migration pack alone costs more than that + you need to get migration ... > replacement of the servers in that period that I didn't take into account. ...
    (microsoft.public.backoffice.smallbiz2000)
  • NT migration to W2K / E2K Help
    ... The Migration also includes Exchange 5.5 Servers ... The ADC was run and disabled user accounts were created in the ... While I can survive with out the Sid History of the User accounts I ...
    (microsoft.public.exchange2000.setup.installation)
  • Moving user accounts to W2K from NT Need advice badly
    ... The Migration also includes Exchange 5.5 Servers ... The ADC was run and disabled user accounts were created in the ... While I can survive with out the Sid History of the User accounts I ...
    (microsoft.public.win2000.active_directory)