replace w2k dc (+exchange) with 2008 server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi!

I could use some advice on the necessary steps to replace an existing windows 2000 / exchange 2000 installation with a windows 2008 server.

Maybe you have some hints/suggestions/warnings concerning our "roadmap".
Currently we have one windows 2000 server as domain controller for our domain. This server is acting as DNS- and DHCP-Server. Some group policies for the domain are defined and login scripts are distributed by the DC. Additionally Exchange 2000 is installed on this machine
(In the near future we plan to replace exhange with a groupware solution but for the moment exchange is still needed.).

As i said, we plan to replace the domain controller with a windows 2008 server (a virtualized server running on vmware server). The 2008 server already joined our domain as a member server.

So far we did the following tests and preparations:
* DCDiag -> ok
* NetDiag -> ok
* DNS is ADSintegrated

The following steps were succesfully tested on a virtualized copy of the current DC:
* adprep /forestprep
* adprep /domainprep
* adprep /gpprep

So i think we are ready to dcpromo the 2008 server. (Are we? Anything else to consider until this point?)

As i haven't worked with two domain controllers before, i am a bit unsure about the following steps, at least about possible replication-pitfalls.
* DNS should be automatically replicated
* What about DHCP, GPOs and Login Scripts, are they all replicated too? Anything to consider / do manually?
* if the replication works, i move all FSMO-Roles to the new DC, right?

As we'd like to switch to 2008 domain mode after the move, we plan to demote the 2000 server as soon as possible (= after the replication is succesfull). We still need the 2000 server as exchange 2000 depends on it.

Are there any problems demoting the 2000 server Exchange runs on?

As soon as the groupware-replacement for exchange is running we'd like to uninstall exchange.
Is this as simple as it sounds or are is there anything to consider - things like e.g. AD dependencies.

Do these steps make sense? Anything else to consider?

Thanks!
Andreas
.



Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Thoroughly confused SBS 2003 Server
    ... fact I first had SBS running on the box that now has the Server Enterprise ... A year ago or moe I put up the second server and made it a domain controller ... The replication generated an error: ...
    (microsoft.public.windows.server.sbs)
  • RE: The list of servers for this workgroup is not currently available.
    ... Verifing that the local machine exchange, ... Connecting to directory service on server exchange. ... The replication generated an error: ... The last success occurred at 2003-10-22 09:58.47. ...
    (microsoft.public.win2000.active_directory)
  • Re: multiple errors in Active Directory
    ... Connection-specific DNS suffix: ... If this computer is a domain controller for the specified domain, ... DNS server has updated its own host records. ... If this DNS server's Active Directory replication partners do not have the ...
    (microsoft.public.windows.server.active_directory)