Migrating from Win 2000 AD and Ex 2000 to Ex 2003 and Win 2003 AD

From: Essi (Essi_at_discussions.microsoft.com)
Date: 12/28/04


Date: Tue, 28 Dec 2004 07:33:06 -0800

Greetings,

I need your help/consultation, here is the scenario:
We are a midsize/small network with about 200 users, running AD with five
DC’s and a PDC in five different physical locations. Moreover, PDC and a DC
are located in the same branch where the core of the network is located (a DC
for each Brach). We are running Exchange 2000 on the PDC. I was asked to
upgrade the network/AD to Windows 2003 AD and Exchange 2003 keeping the same
domain name.

I was given only one new server to replace the PDC(since it is an older
box). I need to use the existing servers for the rest of the migration. So, I
need to move the PDC and Exchange to the new 2003 box running Exchange 2003
eventually.

My plan was to install Win 2003 on the new serves and promote that server to
AD and then install Exchange2003 and then move the old PDC to that box.

Step 1. run adprep/forestprep adprep/domainprep
Step 2. Promote the new 2003 server to AD
Setp 2.3 Run Exchange forestprep and domainprep
Step 2.5 upgrade existing exchange 2000 server to 2003 on the old PDC (from
step 2)
Step 3. Install Exchange 2003 on the new server, which is now a new DC
Step 4. Move the mail boxes form the existing Exchange server which is
running on the old PDC to the newly introduced Windows 2003/Exchane 2003
server
Step 4.5 Uninstall Exchange from the old PDC and reroute the incoming emails
to the new server.
Step 4.7 configure the client to download messages form the new server
Step 5. Move PDC/FSMO responsibilites to the new server
Step 6. Demote the old PDC and take it off the network
Step 7. upgrade the rest of the 2000 DC to 2003 DC by
Step 8. change AD form Mix mode to 2003 mode

Now here are my questions:

Q 1. I am wondering if it is a good practice running Exchange 2003 on the
same box that is PDC or DC?

Q 2. What will happen when I want to install Exchange 2003 on the newly
promoted Win 2003 DC while another Exchange server is running on the same
AD/domain (on the old PDC)?

Q 3. What is the easiest way to tell Outlook clients to download messages
form the new server? Can it be mixed? Some form the old exchange and some
from the new server.

Q 4. Can I run both Exchange servers parallel for a short period of the time
and set the new Exchange server to be the front head and then it
replicate/sink with the old exchange server for the duration of the client’s
migration?

Q 5. Is there a better/smarter way to do this AD migration?

I thank you a head of time for any suggestions and recommendations to any
part of my question.

Have a happy holiday,

Essi



Relevant Pages

  • Re: Time server
    ... I'm getting a bit confused but, you have to be setting the time on the pdc ... Re-Enter external time source after port 123 is found to be open ... > and this server seems to be syncing externally fine. ... which provides the NIST Network Time service. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 server DNS problems
    ... you would disconnect the BDC not the PDC from the network. ... > server was promoted as a PDC and the original PDC was promoted to a BDC. ... The DNS server is setup as a forwarder and is pointing ...
    (microsoft.public.windows.server.setup)
  • Re: ADMT TcpipClientSupport registry key NT 4.0 to AD
    ... I would take a network trace of the failure and see where it fails. ... > but I keep getting this error message "Either the source> domain's primary domain controller (PDC) has not been re-> started after setting the tcpipClientSupport registry key> to 1 or the PDC could not be contacted." ... > I have discarded the communication problem between the NT> 4.0 server and the Windows 2003 server because when I do> not select "Migrate user SIDs to target domain" the> migration is successful. ...
    (microsoft.public.win2000.active_directory)
  • Migrating win 2000 AD/2000 Exchange to Windows 2003 AD/Exchange 20
    ... DC’s and a PDC in five different physical locations. ... are located in the same branch where the core of the network is located (a DC ... We are running Exchange 2000 on the PDC. ... My plan was to install Win 2003 on the new serves and promote that server to ...
    (microsoft.public.windows.server.migration)
  • Re: Cant join domain: Network path was not found
    ... Your domain name now is hq.infotouchs.sys but your workstation ipconfig points to hq.infotouchsys.com as connection specific suffix. ... So i think you have to change the suffix in your DHCP server options settings to match. ... trying to join the domain 'hq.infotouchsys.com': Network path not ... I have a single server running as the primary domain controller (PDC) ...
    (microsoft.public.win2000.active_directory)

Loading