W2k PDC, W2k3 and adding new W2k3 w/ new domain.

[screach]

Ok so here is my situation (major pain at the moment.)

I have inherited a network which needs fixing in a bad way. I have a W2K Server which is set-up as PDC running DNS and AD. I have a W2K3 server which is set-up as a DC running DNS and AD with full push pull replication with the PDC.

The network of workstations have been setup (all 2k pro machines plus 5 xp pro machines)to use the T1 Router as DHCP server and the ISP's DNS for DNS.

This set-up as I have learned is a disaster for XP machines as it causes them to lose connectivity every 2 hours or so. I even tried pulling them off the router and giving static IP's but with the same results. After a post in the XP Pro forum here I was informed to make 2k3 the DNS and DHCP server.

I now have 2 options as I see it. 1. I can demote the W2k machine to just a good ole fashion server doing nothing but storing files and use my w2k3 server as DNS and DHCP. Question I have on this is what is the best way to do this. Since they replicate AD and DNS and Wins currently.

2. I can launch a new server on a new domain. Setup DHCP and DNS and transfer the needed files to the new domain. Once it is running successfully I can switch users to the new domain.

Any ideas on this is greatly appreciated.

Screach.....the sound of your world coming to an end at the sight of the dreaded BSOD!

 

[mlichstein]

I'm a little confused. You said you already have a DC that is running DNS. Why not just change your DHCP scope options to point the clients to that DC for DNS?

Put the ISPs DNS addresses in the forwarders tab in the DNS console on the DC.

Also, FYI, AD replication is always a pull. Within the same site, replication is controlled by change notification, meaning if a DC has changes it notifies its outbound partners. But it does not push the change.

Between sites, replication is done on a schedule. Every time the schedule opens, the DC contacts its partner and pulls any new changes.