Is it OK to have PDC on SP2 and BDC on R2 SP2

Microsoft Windows server 2003 r2 for win...
July 29, 2009 at 13:56:55
Specs: Windows 2003 Server
I have a Domain Controller running on a box with
Windows 2003 SP2 installed. I would like to create a
failover domain controller on a separate box running
Windows 2003 Server R2 Standard Edition. Does it
matter that the two domain controllers are running
different versions of Windows Server 2003? If yes, is
there a way to upgrade the non R2 box to R2 without
doing a reinstall?

Thanks in advance for any advice.


See More: Is it OK to have PDC on SP2 and BDC on R2 SP2

Report •

July 29, 2009 at 15:47:29
There is no PDC/BDC relationship in Active Directory. Using those terms tends to show you are appling NT4 knowledge to AD which will only get you into trouble.

What do you mean by "failover DC"? Those terms have a couple of meanings.

if you just mean an additional domain controller there is no problem having one DC on 2003 and another on R2.

What you DO need to do is run adprep from the 2nd R2 cd on the 2003 server so your schema is updated to accept the new objects R2 brings to the schema.

Report •

July 30, 2009 at 06:24:15
Thanks for the prompt reply. Sorry about the confusing
terminology. You are correct - I just want to create a second
DC to use in the event the main one goes down. That is what
I meant by 'failover'.

I never run adprep before. I see it on the second R2 disc. Is
it just a question of running the exe file, following a wizard
and restarting or is there more to it?

Thanks again,

Report •

July 30, 2009 at 07:53:50
google adprep 2003 r2 for the MS how tos and info

Report •

Related Solutions

July 30, 2009 at 08:53:31
Thanks. I did a search and found guides on running adprep.
Unfortunately, I've run into an issue that that no google
search has provided me a definitive answer for.

I am getting the following error when I run adprep on the
schema master running w2k3 sp2:

ADPREP was unable to extend the schema.

The schema master did not complete a replication cycle
after the last reboot. The schema master must complete at
least one replication cycle before the schema can be

[User Action]

Verify that the schema master is connected to the network
and can communicate with other domain controllers. Use the
Sites and Services snap-in to replicate between the schema
operations master and at least one replication partner. After
replication has succeeded, run ADPREP again.

Considering that I am doing all this just to create a second
domain controller, how can I replicate the schema if I don't
have another DC to replicate to? Is there a way to bypass

I am running adprep on disc 2 of w2k3 R2.

Thanks again for any help.

Report •

July 30, 2009 at 09:45:26
Have you ever had a second DC? Perhaps one that died or was only brought on as temp?

Report •

July 30, 2009 at 09:53:12
No, not that I am aware of but I just took over for a guy who
suddenly left. According to the tech support guy who worked for
the guy who left, there has never been a second domain
controller in the environment.

Based on your response, I am guessing there is no workaround
for this other than reinstalling Windows Server 2003 SP1 on the
box I was going to use as a second domain controller so it
matches the schema master.

Report •

July 30, 2009 at 10:41:21
No. That would not be the solution.

The message indicates possible metadata corruption. It appears AD thinks there is another DC its supposed to be replicating with.

Follow this article to the point of listing what AD sees as DCs. If you see an unknown DC then you do have metadata corruption. Continue to clean it up.

You should review this article first

Report •

July 31, 2009 at 10:01:47
Thanks for those links. I followed the directions and managed
to clear out the remains of a replica domain controller the
previous guy must have tried to set up.

Thanks again,

Report •

Ask Question