Windows Forum

Ask something
Discussion Locked

Changeing the DC

0 helpful
8 replies

by voldar 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have to change the DC of a company. The situation is:
- there is one single DC which is W2K Server system based
- the server is going to be removed
- there are 50 computer clients with W2K Pro/XP Pro
The problem is the following:
- I have created the text file that contains the users information so that it's ready for ldifde use
- I will "re-built" the new DC as it was before (beside the installation of Exchange) but I will have problems with the SID of the computers.

What can you suggest me to do? If I do a backup of the existing DC it will backup also the exchange features (and I don't want).
How can I do so that I will not be forced to re-construct for each computer the proper SID? (I want not to re-join the computers on the network one by one - it's gonna be hard for me, I am looking for a tool/advice about how avoiding this).
Thank you all.

8 replies

by rabbit_runner

You do have a problem. Because what you desire will indeed change the SID for each item in the Active Directory database.

Here is a suggestion. Find another computer that the customer can allow you to use. This system should meet the requirements for Windows 2000 server. Install 2000 server on this box, do a DCPROMO and make it another Domain Controller. Make certain that DNS is transfered to this temporary server. Also transfer all 5 FSMO's from the original server to this temp server. To do this, find the KB article 255690 in the Knowledge Base of Microsoft's web site. This give detailed instructions.
Now that everything has been transfered, then on the original DC, do a DCPROMO to remove it as a Domain Controller. By doing this, you have maintained all AD users and their SID's.
Then rebuild the original server and install or change what you need. Once it is ready, then DCPROMO it back to a DC, transfer the FSMO's, then DCPROMO the temp server down and remove it from the network.

Really, the best way is to find a temporary computer and make it a domain controller. This will maintain all SID's and Active Directory information. Just use a temporary server.

Hope this helps

by voldar

Thank you for the answer - I thought about that too, but the problem is: I have to do that in less than a day (in weekend) and I can't use both servers in the same time - don't ask why not:).

by rabbit_runner

This does create a problem for you. I now have a couple of questions.
1. When are you planning on doing this task? This weekend, or next weekend? If it is next weekend, then you would likely have ample time to create a temporary server. You could build a bare bones 'temp server' in about 2-3 hours. And have the FSMO' transfered in another 30 minutes.
2. Unless you find a way of keeping all the data in the Active Directory database, you will be creating a log of additional work for yourself. If you lose the AD database, then you will be required to re-add each workstation, re-add each user, re-create all shares with correct permissions. Without that database, you will multiply your work 10 times over.

Other than the above suggestion, there is not an easy answer.

Best of luck

by curacao_dejavu

Buggs bunny is correct, if you don't want to go to the workstations you will have to create a secondary server with AD etc etc,

Leopold

This discussion is closed to new replies.