Re: Migrating from exchange 2000 to 2003

From: Steven Halsey [MSFT] (Stevhal_at_Online.Microsoft.com)
Date: 07/02/04 

Date: Fri, 2 Jul 2004 00:00:14 -0700

I'm guessing you want to remove the child domain as soon as possible so I'd
suggest the following:

1) Run Exchange 2003 "Setup /forestPrep" on the Parent DC. This will avoid
KB 314649. Also run Exchange 2003 "Setup /domainPrep" on the parent DC.
2) Run Windows 2003 "adprep /forestPrep" on the Parent W2k DC.
3) Run Windows 2003 "adprep /domainPrep" on the Parent W2k DC.
4) Install the Windows 2003 DC in the parent domain Corp, and do the
DCpromo
5) Install the Windows 2003 DC for the remote Site. You may want to
consider building the Windows DC in the corp and shipping to the remote site
or there is a method with Windows 2003 where you can take a backup of your
Corp Windows 2003 DC and use it to do the DCpromo at the remote site. These
methods would just avoid you having to do initial replication between the
corp and remote site for the parent domain. Check out
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/dssbl_dfr_txor.asp
for information about installing the second DC from media.
6) Once you have the 2 Windows 2003 DCs up install Exchange 2003 on the
remote DC and move the mailboxes/Public Folders/roles from the child
Exchange to the new Exchange server.
7) Uninstall Exchange 2000 from the child Domain Controller
8) Migrate whatever other data is on the Child Domain to the parent domain
and remove the child Domain by running DCpromo on the child domain.
9) Install Exchange 2003 on a member server in corp and move the
mailboxes/Public Folders/roles to the corp Exchange Server
10) Uninstall Exchange 2000 from the Windows 2000 Corp DC
11) Remove the Windows 2000 Corp DC by running DCpromo.

If removing the child domain is not your first priority, you could install
the member server Exchange and migrate the Corp Exchange server first by
insterting steps 9, 10 and 11 above step 5. Or if you want to use Exchange
2003 in the Corp office sooner you could move Steps 9 and 10 above step2,
before you install the Windows 2003 Domain Controllers. 

-- 
Steven Halsey
Stevhal@online.microsoft.com
Microsoft Exchange
Please do not send email directly to this alias.  This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"dan" <danmeam@yahoo.com> wrote in message
news:efe2fb28.0407010543.fdaef31@posting.google.com...
> Thanks for the reply.
>
> This our current config
> Abc.org: DC/GC Exchange server (corp office)
> 123.abc.org: DC Exchange server (remote location)
>
> > So a couple of questions for you:
> >    Do you intend to run Exchange all on member servers or on Domain
> > Controllers as well?
>
> We will have a member server for exchange, but exchange will also be
> installed on a DC which is at a remote location for failover.
>
> >    Do you intend to replace all the hardware (By my count 2 DC/Exchange
> > currently, will this become 3 DCs, 2 member Exchange servers)?
>
> Yes, we want to replace all the old hardware (2 compaq p3 500's) with
> 2 new DCs (one which have exchange installed) and 1 member server for
> exchange
>
> Config I'd like (I want to eliminate the child domain and move those
> users into the parent domain. its only 12 or so users).
>
> Server 1/ Abc.org: DC/GC (corp office)
> Server 2/ Abc.org: DC, Exchange server (remote location)
> Server 3/ Abc.org: Member server/Exchange server (corp office)
>
> >    Will all the old hardware be removed completely such that upgrading
of
> > servers would only be a temporary solution, in which case I'd skip the
> > upgrades and just go to moving mailboxes and roles to new hardware?
>
> All the old hardware will be removed.
> I'd like to skip the upgrades but I have been getting confused on what
> I'm allowed to do and in what order.
>
> >    Do you have a preference for moving Exchange first or Windows first?
>
> What ever works best, currently our active directory is only a user
> shell (about 130 users) with no groups, GP's, permissions, etc. its
> really only there for exchange (Migrating from a NetWare file server
> to a w2k3 file server after I get exchange and the Windows Domain
> squared away).
>
> Thanks again,
> Dan

Relevant Pages

  • Re: domain migration issue
    ... I recently created a child domain, let's call it child.company.local as a ... delegation to our root domain, ... domain - it says 'exchange server is not available'. ...
    (microsoft.public.windows.server.active_directory)
  • Re: domain migration issue
    ... Made the server that was failing in the RUS connection into a GC. ... ipconfig /all from the DC's in root and child domain. ... Doing the exchange domainprep worked fine. ... from the exchange in the root domain just fine and also nslookup is ...
    (microsoft.public.windows.server.active_directory)
  • Re: Rename Domain
    ... offices acting as DC, DNS, DHCP, FS and PS. ... Renaming a domain with Exchange in the picture is not a pretty thing and I ... Why a child domain, just out of curiosity? ... How will this affect the exchange server? ...
    (microsoft.public.exchange.admin)
  • RE: windows 2003 migration from windows 2000
    ... users are in both domains sharing one exchange server. ... domain b users over and i dont want to create a child domain. ... > the Windows 2000 domain and allow them to access the Exchange server in the ... It can maintain the two domains in an AD domain tree. ...
    (microsoft.public.windows.server.migration)
  • Disable NetBIOS and NTLM on Windows 2003 Domain Controllers and Exchange 2003?
    ... Is it possible to safely DISABLE NetBIOS and/or NTLMv1/LM on all Windows ... 2000 and Windows 2003 Domain Controllers and/or Exchange 2003 servers ... We are a child domain in a single forest, ...
    (microsoft.public.exchange.admin)