Re: Installing New Domin Controller

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

Hello Dan,

Did you upgrade to a SP1 server?
http://technet2.microsoft.com/windowsserver/en/library/bc5ebbdb-a8d7-4761-b38a-e207baa734191033.mspx?mfr=true

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

gpprep also ????

"Meinolf Weber" wrote:

Hello Dan,

First you have to upgrade the schema on the 2000 DC, for that use the
2003

install disk and use the adprep command from the i386 folder, in your
case

adprep /forestprep and adprep /domainprep:

http://technet2.microsoft.com/WindowsServer/en/library/bc5ebbdb-a8d7-
4761-b38a-e207baa734191033.mspx?mfr=true

Install the new one with 2003, promote it to DC and move the FSMO
roles,
here about the moving:
http://support.microsoft.com/kb/324801
In the Event viewer Dircetory services look for a succesful entry for
the
moving of the roles and with the moving give it a bit time.
Make the new server also a Global catalog:
Open Active directory site and services, go to Sites, default first
site
name, servers, choose the server, right click NTDS settings, open
properties
and checkmark Global catalog (check event viewer after it, in
Directory service
you must find event id 1110 and 1119)
DNS is easy, is it running as Active directory integrated zone on the
old one? If not make so, then it will replicate automatically to the
new one if you installed DNS on the new server. Make sure the new
server is only pointing to the old server for DNS on the NIC. Give it
time for replication. After replication change the clients settings
to the new DNS server, via DHCP options and also the settings for the
old one to the new as pimary DNS on the NIC.

Check with dcdiag and netdiag for errors.

For DHCP check this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;325473
If everthing runs fine, demote the server with dcpromo to remove it
correctly. It will appear under computers after demotion and then you
can safely delete it. If you just shut it down you will get a lot of
replication errors.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
Existing DC= Windows 2000 with integraed AD and DNS New Dc = Win2k3

As of now the Win2k DC is not replicating and is the only DC in the
Domain so it has all roles on the one box...

I need a roadmap on which utilities to run (in what order) to
"copy/migrate " everything that would be needed to get the new DC to
"take over" in the smoothest possible manner then I will work
on getting some replication in place

thanks



.

Relevant Pages

  • Re: how do i move primary DC from one machine to another
    ... Test omitted by user request: DNS ... Connecting to directory service on server WIN2003DC. ... Replication Site Latency Check ...
    (microsoft.public.windows.server.general)
  • Re: error 8254 DNS Lookup failure
    ... FYI, I repointed the DNS to one server, deleted the contents of _MSDCS ... > in the same site, Replication has been fine up until yesterday, the ... > Starting test: CrossRefValidation ...
    (microsoft.public.win2000.dns)
  • Re: WINS and DNS issue
    ... When I said the that DNS server is configured to to replicate to all other ... Ive had a look at the options under replication, ... It says to set this if you want a 2000 server to load the zone. ...
    (microsoft.public.win2000.dns)
  • Re: WINS and DNS issue
    ... > When I said the that DNS server is configured to to replicate to all other ... > properties for our forward lookup zone - We dont actually have another ... replication if you have only one DNS server. ...
    (microsoft.public.win2000.dns)
  • Re: Still strange not fully working DNS server
    ... Best regards ... "Meinolf Weber" wrote: ... Readd it's own ip address to the NIC as preferred DNS. ... Is the new server Global catalog? ...
    (microsoft.public.windows.server.dns)