questions creating a backup domain controller

[dpsmith]

Hello,
Background: small company, about 40 W2K users, 1 old slow W2K DC using DHCP/DNS and it's also used as a fileserver and Terminal application server AND FTP server. (I know)
It also has some DNS problems and Office2K issues too.

The server is divided into two partitions.
C: Are OS and apps
D: is all data (Access2K mostly)

I want to add a new server and make it the new DC.

Please help me with some concepts on the new server:

I create two partitions.
I install the OS on C:
Copy the data from the old DC onto D:
Run dcpromo.
How do I get the new server to handle DHCP requests?

Ideally, I want to shut down the old DC, wipe it clean and reinstall W2K server to handle DHCP request and other minor uses.
I want the NEW server to have all the same data locations.
How can this be done and not have all 40 users in my company freak out about all their shortcuts to programs on the DC being gone?

I know this is a pant load of questions but any help would be appreciated.

(Warnings too about any problems to look for!)

Thanks

 

[snootalope]

Ok..

Setup the new PC with the 2k and AD installed.. Join the Domain.. (This is what I would do)

1. Make the new server a DC, preferably a BDC, they should automatically see each other. They'll replicate..
2. Setup your new DHCP scope (DNS, WINS, bla bla bla) KEEP IT DISABLED FOR RIGHT NOW!! I'd make sure everything replicates first (Sysvol, etc).

hhhmmm...

** Do you have a log inscript that maps the drives (i'm assuming thats your shortcuts) for them? Hope so, that would make it easier.. Simply change server1 to server2, or whatever you got, in thier login script after replication!

3. Then, stop the DHCP service on the old server. As long as thier lease time is 8 days (by default) your fine.. They'll hold those address for, well, 8 days!

4. Activate (& Authorize, of course) the DHCP scope on the new Server. **From my experience** Reserve the portion of address that are already in use!!! Say they range from XXX.1 - XXX.100, I'd make the new server's scope assign addresses from XXX.110 to XXX.254, I hope you see why cause I'm not going to right a story trying to explain it!!

5. After a week or so, the scope on the new server should be full of leased addresses!

*** TO DO ***

(this might have already been done)
In AD User's and Computer's, Right click the Domain that you have and hit Operations Master! This will enable you to set the new server as PDC, RID, Infastructure master (that's important)

I'm going to stop for now, my fingers hurt. I hope you understand this, if so, tell me and I'll keep going! GOOD LUCK!! "tis better to be thought of as a fool then open your mouth and remove all doubt" Mark Twain

"I should of been a doctor.." Me

 

[FilthPig]

Couple additions/corrections.
Setup the new PC with the 2k and AD installed.. Join the Domain.. (This is what I would do)

1. Make the new server a DC, preferably a BDC, they should automatically see each other. They'll replicate..

AD isn't installed until you run dcpromo, and it becomes a DC, not a BDC. Just wanted to clarify that point.

Also, make sure you run DCPROMO on your old DC before removing it from the network so that FSMO roles get transferred to your new DC.

As far as people's shortcuts not working, that's one that'll be harder to tackle. For your 2k/xp clients, you could remove the old server's host record and create a cname in DNS with the name of the old server pointing to the new server's IP. You only want to do that if you've taken the old server off the network.

Marc Creviere