How do I promote a BDC to a PDC? 3

[sbruce66]

Hello,
Recently we had a hardware failure on our PDC and we would like to promote our BDC to the PDC until our new hardware arrives. Can yanyone tell me step by step on how to do this. I see articles talking about using server manager. I'm using 2000 server where is SERVER MANAGER located. Thanks,

Scott

 

[mlichstein]

I'm confused. Are you talking about NT servers? There is no PDC/BDC in 2000, and there is no server manager in 2000.

 

[sbruce66]

I guess I am confused, we just had our Primary Domain Controller (win 2000 server go down). I have a secondary domain controller and want to promote it to a primary. How do I do this so I can rebuilt our primary domain controller and restore our data to it.

Scott

 

[mlichstein]

First you need to seize the 5 FSMO roles to the new server:

http://support.microsoft.com/?id=255504

Then you need to do a metadata cleanup of the old server:

http://support.microsoft.com/?id=216498

 

[dearingkr]

In Windows2000, there is no PDC or BDC, they are all just called DC's.

Follow the link that mlichstein has provided above.

MCSE CCNA CCDA

 

[sbruce66]

You mean their is no way to promote my secondary to a primary and then rebuild the primary that failed and let replication occur.

 

[Davetoo]

There is no Primary or Secondary domain controller in a Windows 2000 environment. There are only DC's that handle specific roles. If a DC has failed that handled any of the FSMO roles, then you need to follow mlichstein's post to seize those roles by a second DC.

You can rebuild your dead DC, bring it into the environment and then dcpromo it back into the AD and then transfer the roles back if you wish.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[taval]

Hi,

I have a domain with two DC's on Windows 2000 Advanced Server. The Primary DC has gone done, the hard drive has been totally corrupted. I'm now trying to make the other DC (BDC) act as the primary. I followed the steps in:

http://support.microsoft.com/?id=255504

But when trying to tansfer roles , I got the errors "THe request FSMO operation failed, The current FSMO holder could not be contacted". The reason why it can't find the current FSMO holder is because it is not on the netowrk since the hard drive got corrupted. So how do I make the promote the BDC?

Any help is appricated, I am a novice and totally lost right now.

 

[chrissie1]

You need to follow the seize roles steps not the transfer roles steps.

Christiaan Baes
Belgium

If you want to get an answer read this FAQ faq796-2540
There's no such thing as a winnable war - Sting

 

[taval]

Hi, I followed the seize roles, is there any way to check if the DC is now the main DC (PDC). I have tried connecting other computers to the domain but without success. Thanks.

 

[mlichstein]

dcdiag will show who holds the PDCe role. You can also run 'netdom query fsmo', but you need to install the support tools to get netmon.

 

[taval]

I installed the support tools on the DC and ran 'netdom query fsmo' it shows the computer is the owner of all the 5 FSMO roles. I then ran dcdiag, the results are shown below. File replication was taking place before with another DC, until it failed, which is the reason I had to promote this other DC in the first place. If File Replication failed, would the domain still function? How would I disable file replication on the DC?

-----------------------------------------------------

C:\Program Files\Support Tools>netdom query fsmo
Schema owner tpin6.tpin.com
Domain role owner tpin6.tpin.com
PDC role tpin6.tpin.com
RID pool manager tpin6.tpin.com
Infrastructure owner tpin6.tpin.com
The command completed successfully.

C:\Program Files\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\tpin6
Starting test: Connectivity
......................... tpin6 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\tpin6
Starting test: Replications
[Replications Check,tpin6] A recent replication attempt failed:
From tpin1 to tpin6
Naming Context: CN=Schema,CN=Configuration,DC=tpin,DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-26 15:56.27.
The last success occurred at 2005-04-21 13:16.24.
136 failures have occurred since the last success.
The guid-based DNS name 7e428687-c96a-4d4d-9c08-f2db06e8ed0c._msdcs.
tpin.com
is not registered on one or more DNS servers.
[tpin1] DsBind() failed with error 1722,
The RPC server is unavailable..
[Replications Check,tpin6] A recent replication attempt failed:
From tpin1 to tpin6
Naming Context: CN=Configuration,DC=tpin,DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-26 15:56.27.
The last success occurred at 2005-04-21 13:16.23.
136 failures have occurred since the last success.
The guid-based DNS name 7e428687-c96a-4d4d-9c08-f2db06e8ed0c._msdcs.
tpin.com
is not registered on one or more DNS servers.
[Replications Check,tpin6] A recent replication attempt failed:
From tpin1 to tpin6
Naming Context: DC=tpin,DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-26 15:56.27.
The last success occurred at 2005-04-21 13:16.23.
163 failures have occurred since the last success.
The guid-based DNS name 7e428687-c96a-4d4d-9c08-f2db06e8ed0c._msdcs.
tpin.com
is not registered on one or more DNS servers.
......................... tpin6 passed test Replications
Starting test: NCSecDesc
......................... tpin6 passed test NCSecDesc
Starting test: NetLogons
......................... tpin6 passed test NetLogons
Starting test: Advertising
......................... tpin6 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... tpin6 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... tpin6 passed test RidManager
Starting test: MachineAccount
......................... tpin6 passed test MachineAccount
Starting test: Services
......................... tpin6 passed test Services
Starting test: ObjectsReplicated
......................... tpin6 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... tpin6 passed test frssysvol
Starting test: kccevent
An Information Event occured. EventID: 0x4000051C
Time Generated: 04/26/2005 16:01:49
(Event String could not be retrieved)
......................... tpin6 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x8000003E
Time Generated: 04/26/2005 15:46:11
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00004E8A
Time Generated: 04/26/2005 15:56:56
Event String: Unable to add the interface Internal with the
An Error Event occured. EventID: 0x8000003E
Time Generated: 04/26/2005 15:57:12
(Event String could not be retrieved)
......................... tpin6 failed test systemlog

Running enterprise tests on : tpin.com
Starting test: Intersite
......................... tpin.com passed test Intersite
Starting test: FsmoCheck
......................... tpin.com passed test FsmoCheck

-------------------------------------------------------