Backup Domain Controller

Hi there,

I want to add a Windows Server 2008 R2 as Back-Up Domain Controller to a Domain which has a Windows Server 2003 R2 as Primary Domain Controller.I've all the FSMO roles on this single 2003 primary domain controller.
So when I'm trying to prepare this Existing 32-bit Windows Server 2003  Domain Controller for the setup, and when I issue an "adprep32 /forestprep" command, I'm getting the error
" Forest-wide information has already been updated.
[Status/Consequence]
Adprep did not attempt to rerun this operation "

And the same happens when I issue an "adprep32 /domainprep" command,that is  Im getting the following error
" Domain-wide information has already been updated.
[Status/Consequence]
Adprep did not attempt to rerun this operation

How can I fix this please ?

Thanks,
Clement
LVL 2
Clement PAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Clement PAuthor Commented:
Sorry the primary DC is a Microsoft Windows Server 2003 for Small Business Server with SP2 server
.
Seth SimmonsSr. Systems AdministratorCommented:
it means the schema has already been extended; adprep only needs to be done once when you are introducing a domain controller of a newer operating system

you should be able to promote the 2008 R2 server

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Lee W, MVPTechnology and Business Process AdvisorCommented:
Agree with Seth.  

The message is telling you what's going on. "Forest-wide information has already been updated."  If it's already done, you don't need to do it again.

ADPREP = AD Prepare

You are PREPARING AD for a newer version of Windows Server.  Once it's been prepared, it's done.  It never needs to be done again for that version of Windows or earlier.
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Clement PAuthor Commented:
Thank you both.

I successfully installed a New Backup DC on 2008 R2.
However I've couple of questions please.

1) My Primary DC is 192.168.10.2 - I've my primary DNS, DHCP running on this
 So now I've New 2nd Domain Controller in the  Domain as 192.168.10.8 and for this  the preferred DNS server would be 192.168.10.8 and Secondary as 192.168.10.2 ...isn't it ?

Also 2) How should I Configure DHCP on this New Back-up DC for Failover please ?

Thanks,
Clement
Lee W, MVPTechnology and Business Process AdvisorCommented:
You would need a split scope - your first DHCP server would have a range of, for example, 192.168.10.51-125 and the new server would provide 192.168.126-200.

DNS doesn't matter too much - I'd have each DC point to themselves with the other as secondary.  The clients don't matter much.  DNS (and AD) replicate with each server.
Clement PAuthor Commented:
Ah okay.

So with regards to DHCP - Splitting the scope is the only option ? Because lets say if my primary DC goes down and the BDC kicks in and authenticates users however it would through a new set of ips isnt it ?  I man the PC which was getting an IP as 192.168.10.100 from PDC, may get a new one from the BDC ? Isnt it ?  
Is there any solution where the IP's remain same irrespective of  PDC or BDC running please?

Thanks
Lee W, MVPTechnology and Business Process AdvisorCommented:
There is no such thing as a BDC or PDC in Active Directory.  That's 15 year old terminology that expired with NT4.  

The only solution for preserving thee DHCP assignments is a clustered DHCP server.  WAY overkill.  Why do you care what IPs the workstations get as long as they get IPs?  You could create reservations for each DHCP server and always get one address or the other.  Or set all your addresses statically - then you aren't using DHCP and IPs never change.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.