When you have to backtrack and downgrade a DC
- From: CryptiniteDemon <CryptiniteDemon@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 May 2008 04:39:01 -0700
Okay, so I have this book from Microsoft that's basically a guide to get from
NT 4.0 to Server 2003.
Of particular interest is the section where they talk about going back to an
NT DC if there's and installation error or something. Now basically the
procedure is:
Keep a BDC off line just in case.
When something goes wrong, take all 2003 DCs off the network
Promote the BDC to a PDC.
And I would imagine this works fine if no computer had ever logged on to the
new domain. But say you got everything up and running just fine on 2003 and
a few days later decided you needed to go back to NT for some reason.
This is the scenario I'm trying to simulate. And whenever I do this
simulation, I can indeed put the domain back to the NT machine, but any
computer that's 2000 or newer that has logged onto the new domain will not
log back into the NT version. (specifically because it adopts the DNS naming
structure of my new domain name). NT machines, of course, do revert back to
the old domain with no problems that I can see.
So is there any particular way to get one of these machines that's logged in
to the 2003 domain to revert back to the NT domain without having to manually
rejoin the domain on each computer?
.
- Follow-Ups:
- Re: When you have to backtrack and downgrade a DC
- From: Danny Sanders
- Re: When you have to backtrack and downgrade a DC
- Prev by Date: Re: Anyone running Java on WS 2008?
- Next by Date: Re: important case study for a client
- Previous by thread: Re: Anyone running Java on WS 2008?
- Next by thread: Re: When you have to backtrack and downgrade a DC
- Index(es):
Relevant Pages
|
