Fix Win2K3 server so it's a PDC not a BDC - or killit/reset up

[Guest Mark Hripko]

I had a Windows 2000 Adv Server PDC running (it was upgraded from an NT4 Adv Server PDC way back when), and recently added a Windows 2003 Server machine and got it to be the BDC. Now, before I could switch the PDC/BDC computers so the Win2K3 server would take charge of everything, the old PDC (the Win2000AdvServer lost it's disk and got wiped clean. No backup, no way to recover, no way to fix. Without giving any lectures on that aspect, I need to know HOW to FORCE the Win2K3 Server with it's AD to become the sole surviving in charge machine and have it authenticate everything. Right now, shares and permissions and user id's can't be updated, added, deleted because the machines on the network all say that no domain controller could be found to authenticate the request. The win2k3 server is my DNS, WINS, ActiveDir, for the 4 machines on the network. Truthfully, if I could "upgrade" the Win2K3 server and make it FORGET it was ever part of the old domain, I'd desire to rebuild it, give it a new domain name that it's solely in charge of, and have the 4 computers on the network join ITS new domain name and I'd go from there. But I can't seem to get the Win2K3 server to allow me to do this. I want it out of PDC/BDC mode and I want it to operate in AD 2003 mode. I don't care if I have to reinstall Windows Server 2003 on it, if I can get all of the functionality.

 

Any thoughts.

 

Either I want

1) Force the "BDC" (a w2k3 server) with ad on it to ACT and takeover as the PDC forever, and forget it ever knew about the original PDC - (even taking out of that PDC/BDC mode would be great) or

 

2) Make the Win2K3 server set itself up as a new domain controller for a new domain that it will be in charge of, and then join the other 4 computers on the network to it.

 

Mark

 

EggHeadCafe - .NET Developer Portal of Choice

http://www.eggheadcafe.com

[Guest Ryan Hanisco]

RE: Fix Win2K3 server so it's a PDC not a BDC - or kill it/reset up

 

RE: Fix Win2K3 server so it's a PDC not a BDC - or kill it/reset up

 

Hi Mark,

 

I know you said no lectures, but I'll say this quickly before everyone else

piles on... In the 2k/2k3 world there are no real PDC/BDC relationships.

Instead all DCs are equal -- just some are more equal than others. These

"special" DCs hold the FSMO roles. With the symptoms you are describing, you

have misplaced some of these -- the PDCe in particular. You may also have

some DNS issues as well.

 

To resolve your issue, I would:

1. Clean up any records pointing to the old DC out of DNS. This will be a

pain, but it must be done. If you notice that you don't see all of the

correct SRV records for the new one in there, restart its netlogon service to

re-register.

2. Seize the FSMO roles to bring them back to life. You can find directions

here: http://support.microsoft.com/default.aspx/kb/255504

3. Delete the computer account in ADU&C if it still is showing up

4. Perform a metadata cleanup to get rid of traces of the old DC in the AD:

http://technet2.microsoft.com/windowsserver/en/library/012793ee-5e8c-4a5c-9f66-4a486a7114fd1033.mspx

5. Force replication if you have other DCs in your domain/ forest

6. Perform an AD health check:

http://techsterity.com/blogs/bestpractices/archive/2007/10/07/active-directory-health-check.aspx

 

This should get you back in working order.

--

Ryan Hanisco

MCSE, MCTS: SQL 2005, Project+

http://www.techsterity.com

Chicago, IL

 

Remember: Marking helpful answers helps everyone find the info they need

quickly.

 

 

"Mark Hripko" wrote:

> I had a Windows 2000 Adv Server PDC running (it was upgraded from an NT4 Adv Server PDC way back when), and recently added a Windows 2003 Server machine and got it to be the BDC. Now, before I could switch the PDC/BDC computers so the Win2K3 server would take charge of everything, the old PDC (the Win2000AdvServer lost it's disk and got wiped clean. No backup, no way to recover, no way to fix. Without giving any lectures on that aspect, I need to know HOW to FORCE the Win2K3 Server with it's AD to become the sole surviving in charge machine and have it authenticate everything. Right now, shares and permissions and user id's can't be updated, added, deleted because the machines on the network all say that no domain controller could be found to authenticate the request. The win2k3 server is my DNS, WINS, ActiveDir, for the 4 machines on the network. Truthfully, if I could "upgrade" the Win2K3 server and make it FORGET it was ever part of the old domain, I'd desire to rebuild

it, give it a new domain name that it's solely in charge of, and have the 4 computers on the network join ITS new domain name and I'd go from there. But I can't seem to get the Win2K3 server to allow me to do this. I want it out of PDC/BDC mode and I want it to operate in AD 2003 mode. I don't care if I have to reinstall Windows Server 2003 on it, if I can get all of the functionality.

>

> Any thoughts.

>

> Either I want

> 1) Force the "BDC" (a w2k3 server) with ad on it to ACT and takeover as the PDC forever, and forget it ever knew about the original PDC - (even taking out of that PDC/BDC mode would be great) or

>

> 2) Make the Win2K3 server set itself up as a new domain controller for a new domain that it will be in charge of, and then join the other 4 computers on the network to it.

>

> Mark

>

> EggHeadCafe - .NET Developer Portal of Choice

> http://www.eggheadcafe.com

>