Dear All My NT primary domain controller is giving problems. So I want to rebuilt it from scratch. It consists of around 230 user accounts. I need to know the files and folders which should I backup. Please tell me all the important files and folders which i should copy somewhere else so that all user accounts with their passwords can be restored easily and users dont get any authentication problems. Thanks for your guidance Learner

I would suggest installing a Backup Domain Controller on the network. This would automatically replicate the sam database from the PDC to the BDC as part of the installation. I would then check your PDC to ensure that any services on the PDC e.g. DHCP, DNS, WINS, file and print etc. etc. are setup on the BDC. You can then take the PDC offline, promote the BDC to be the PDC (this is found in server manager) and then you still have a working network and you can repair the problematic offline former PDC. Hope this helps....

see the step by step how to below http://www.winnetmag.com/Articles/Index.cfm?ArticleID=19877

Thanks Mick and Wanderer. Your replies have really been helpful. And I am going to follow the steps you have mentioned because this is the safest way to build a new server. But , just for knowledge , is there any way to do this without making a BDC ? I mean if there are any files of sam database and other important files which can help to make another pdc without making any bdc. Have you done this just for experimental purpose? Thanks once again Learner

The method they suggested is recognised as the correct method. The machine you use as an initial BDC doesn't have to be a 'real' server, any decent PC will do. Install NT4 Server on it and introduce it as a BDC. As Mick said above, note all the services that run on the PDC and replicate them to the BDC. If you have tape backups of the server (i.e. home and shared folders etc) make sure that they are up-to-date and OK. Test the BDC but shutting down the PDC, you should still be able to log users in, DHCP, WINS etc should work ok. Obviously they won't find their home and shared folders but as long as the BDC can run the LAN it is then safe to promote it to PDC. Next, rebuild your old server and introduce it as a BDC. Basically repeat the above. I.e. make sure everything replicates to the 'new' BDC. Install any software needed i.e. backup software and restore the home & shared folders etc. Shut down the temporary PDC and test the network is ok with only the 'old' server running as BDC. If all looks ok you can then promote that back to PDC. Don't bring the temporary PDC back up on the LAN once the proper server is re-established as the PDC. Keep your fingers crossed and good luck.

To answer your question Learner, you would need a third party software called Upromote if you did not want to use the native method of SAM replication. This is due to the fact that the PDC and all BDCs in the domain have the same SID [security identifier]. This is not a file or folder you can copy. This is also why a standalone or member server can't become a BDC or PDC without being reinstalled since this sid replication only happens during install.

Thankyou so much MauriceReed and Wanderer. You have been really helpful. Regards, Learner