NT 4 Exchange 5.5 to AD and Exchange 2003

From: Gary R (anonymous_at_discussions.microsoft.com)
Date: 08/11/04


Date: Tue, 10 Aug 2004 21:04:27 -0700

First Step
>From a NT 4 domain exchange 5.5 environment to AD 2003 I
have completed migration of user accounts, sid histories,
groups, and computers using ADMT. Test's confirm succesful
migration.
Second Step
Installation of Exchange 2003 in AD domain on new server
to co-exist with 5.5 site.
I follow the phased process with the Exchange server
deployment tools using ADC to create connectors to 5.5 and
exchange 2003.
This is suucessfull as I can sign on as a test user to the
AD domain configure the mail account to receive mail as I
did in NT4 5.5 environment.
I have two questions
1. During the setup of exchange for 2003, it prompts for a
location to put 5.5 mail from 5.5 to 2003. I setup an ORg
in AD for a holding location. Setup then moves these
accounts to this location in a sub org called recipients.
In the root org is also a sub org called users to which it
is not populated.
The accounts that reside now in this new container were
disabled as a result of telling the ADMT tool to disable
them after they were migrated to AD. I am not sure of this
step. I need some explanation of this procedure.
Secondly, once I have completed all migrations for mail,
how do I sever the connection and insure that individual
mail boxes, public folders and all associated objects from
5.5 get re-located into AD? Ultimatley, my desire is to
complete these steps and decommision the 5.5 Nt4 domain



Relevant Pages

  • Re: Install new hardware for SBS 2003
    ... I agree Cliff and having done a Swing migration myself I can attest to the ... his plan would not work. ... then the new accounts would obviously cause a mismatch...and ... have to get the current Exchange mail over too. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 5.5
    ... stuff cause the builtin accounts aren't migrated and all seemed ok. ... then you have no upgrade path. ... It's strictly a migration. ... > and want to upgrade Exchange but migrate the Windows accounts, ...
    (microsoft.public.exchange.setup)
  • Re: Integrating a newly acquired subsidiary of a big corporation.
    ... I wouldn't use CSVDE because of delimiter problems, but LDIFDE is ... accounts, so groups should be migrated after the accounts. ... because of GUID ties to the source exchange ... I found when I used the exchange migration wizard on the source ...
    (microsoft.public.windows.server.active_directory)
  • 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: Install new hardware for SBS 2003
    ... The plan will work. ... create new user accounts and computer accounts with the *exact* same names ... Personally I'd recommend a "swing" migration. ... have to get the current Exchange mail over too. ...
    (microsoft.public.windows.server.sbs)

Loading