Windows Forum

Ask something
Discussion Locked

Building a new PDC

0 helpful
16 replies

by swlabhot

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

Hi,

At the moment we have a PDC and two BDCs in our domain. I would like to replace our exiting PDC with a new higher spec machine. Our PDC has a lot of data on it as it is also a file server and contains the users' home directories. Is this possible without causing too much of a problem as I would like the exiting BDCs to remain as BDCs?

Steve.

16 replies

by curlergirl

The easiest way to do this would be to add the new machine to your existing domain as a BDC. Then you can configure it by installing whatever additional software is on the original machine and copying over the data. All the security info, etc., will be replicated to it normally as a BDC. Then, when you're ready to put it into service, promote it to PDC - this will automatically demote the original PDC to BDC - and you can then remove the original PDC (or continue to use it as a BDC if you want to). Of course, the new PDC will have a different name, so any shared resources will have to be remapped (i.e., the user's home directories) to the new server. This is easily done through login scripts or settings in User Manager, depending on the types of workstations your working with. Hope this helps!

by swlabhot

The crucial thing is that I have to keep the PDC's name the same for many reasons. Obviously when I build it as a BDC, it will have a different name but if I rename it to the original name after promoting it to PDC and taking the original PDC offline, what effect will it have if any to any of the processes (ie,. domain synchronization, authentication, user mappings etc...)?

by ch_thies

First of all, you must install the new computer as a BDC. Be sure to install it plugged to the network so the users database is transferred to the new machine.

When you set up the new machine with all data and settings, you must demote PDC, and when this is finished, promoted the new bdc as a pdc.

by gigelul

In addition to answer1.
If your backup program is capable to save also the permissions for the folders which contain data this is an options which can save time and work.

by gigelul

I don't try the procedure from answer5 but can be OK, it is logic.
About backup: I work with BackUp Exec and in the same domain with the same accounts, is capable to restore data with the same permissions settings in other location/partition/server. I don't speak about shares, only folders and permissions for them. Shares can be easily rebuilt.

by curlergirl

In re: your comment above - This might work OK - supposedly you can do this, and the instructions are supposed to be in the Windows NT Server System Guide - a book which I can't seem to find anywhere, at least not online (!). I believe, though, theonly trick to it is that you need to create a machine account with the new server name as a BDC in Server Manager BEFORE you change the name of the server. Then, I think what actually happens is that you join the domain, the existing account gets upgraded to a PDC and away you go. Hope this helps!

by swlabhot

I will certainly give it a try to see if it works. As there is an substantial amount of data to be migrated, its easier if I build the new PDC into the live network and then transfer the data from the live PDC (soon to be replaced) to the new one. Once done take the old one off line and promoting the new BDC to PDC. My only concern is now after its been promoted to PDC, whether the name change to the original PDC will have undesired results as it will no longer have the same machine ID(eg, SID)as the old one.

by jon pratt

This should be a slam dunk! Copy stuff from PDC that needs to be backed up to network/tape. Promote a BDC to a PDC. Install new server as a BDC with the old PDC's name. Promote new BDC to PDC. Copy stuff from network/tape to new PDC. Pat yourself on back for job well done! =) Good luck.

by curlergirl

In re: your concern about the SID of the machine - PDCs and BDCs in an NT domain all have the same SID - this is how they're identified as domain controllers. So, the SID of the machine is set when you first join the domain as a BDC and will not change when you promote it or change its name. Hope this helps!

by nettek

1. Set up new server as BDC.
2. Promote new server to PDC.
3. Use backup (if it will keep permissions) to transfer files from old to new. OR use scopy.exe (found on resource kit). Scopy will keep permissions.
4. Rename old PDC.
5. Rename new PDCto same name as old PDC. This will keep you from having to change any drive mappings, etc.

Note: In steps 4 and 5, make sure you make the appropriate changes concerning IP addresses and NetBIOS names in WINS or LMHOSTS so that you continue propername resolution.

This discussion is closed to new replies.