Re: AD does not start



Nerd <Nerd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> I am trying to setup a lab for my exchange migration with a duplicate
> AD domain controller, but AD and DNS do not start. I took an image of
> an existing DC and imaged an identical (h/w) server in the lab. First
> of all the server takes a long time to come up to the login screen no
> errors though. However, once the server is up DNS has an X and does
> not start, I can browse the evetn viewer though. Other management
> tools do not open-says does not find domain however, if I specify the
> server anme I am able to open users and comp, sites etc.
> I get a bunch of erros in evetn viewer , 4000, 4013, 537, 1053, 1054,
> 40960, 53258 etc. Please note DNS is active directory integrated and
> the TCP/IP is configured to look internally to resolve any DNS
> requests. It seems that when the server start it does not find DNS or
> AD or both. How can I resolve this issue?

Srarting with an image of an existing DC, is not the way I would go.
If you want to do this with your existing domain, you can do that.
Install Windows server, promote it as a replica DC in your existing domain,
disconnect it, do a meta data cleanup on your production DCs to remove the
newly installed DC from AD.

Then take the server to your lab, seize all 5 FSMO roles, do a metadata
cleanup on it to remove the other DCs from its AD. Then you can do your
upgrades install exchange or anything else you want on it.

You won't be able to reintroduce it back to the existing production domain,
but there is no telling why AD and DNS won't start on this one. Since AD
won't start you can't do a metadata cleanup on it and seize the FSMO roles.


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


.



Relevant Pages

  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
    ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... you can check the version with "schupgr" in a command prompt. ...
    (microsoft.public.windows.server.setup)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... dynamic updates and create PTR records in DNS. ... tracking is easier from the server. ... I don't install dhcp on the servers, ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... The only time I have seen the connectcomputer error you mentioned about DNS ... I don't install dhcp on the servers, ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
    ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... and "netshell dhcp restore" command ...
    (microsoft.public.windows.server.setup)