adprep /domainprep /gpprep fails

Giganews Newsgroups
Subject: adprep /domainprep /gpprep fails
Posted by:  ryguy (ryg…
Date: Mon, 23 Jun 2008

Hey there, thanks for reading my question. I am having problems adding a new
Server 2008 x64 as domain controller in an existing 2003 forest.

The entire situation is a bit embaressing, so I should tell you ahead of
time that I am new to IT, and I've likely made mistakes. Please bear with me.

We have an old 2003 server that functioned as dc. It is not valid, and we
can no longer log into it. (I should mention that I do no support piracy, and
as such, have worked very hard to bring everything here to a professional

We have invested in a brand new 2008 server which I want to replace the 2003
completely. The 2003 is an old unreliable computer, and I do not want it
performing any domain level function anymore.

Since I cannot log into the old 2003 to run adprep, I can't promote the 2008
to dc. My idea to work around this was create a hyper-v virtual machine with
2003, transfer roles to the 2003 virtual machine, and run adprep from there.
I did this, but am stuck with a couple differant issues:

1) After forestprep succeeded, domainprep /gpprep fails
log says
Adprep unable to update domain information
Adprep requires access to existing domain-wide information from the
infrastructure master in order to complete this operation.

-I made sure the sysvol reg key is correct
-this virtual machine dc is infrastructure master, as well as all other fsmo

2) Ignoring this error, I attempted to use dcpromo on 2008 anyway, however
warnings that I do not understand convinced me not to continue without asking
for help. The warning I received says: A delegation for this DNS server
cannot be created because the authoritative parent zone cannot be found or it
does not run Windows DNS server. To enable reliable DNS name resolution from
outside the domain *FQDN*, you should create a delegation to this DNS server
manually in the parent zone. Do you want to continue?

What do I do now???? The old 2003 is still running, serving up dc, and now
I've got a virtual machine 2003 running as another, neither of which are
valid, and I need to get rid of, and 2008 sitting here, just waiting to get a
peice of the action.

Any help is well appreciated! Thanks