Re: When you have to backtrack and downgrade a DC

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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.


The only reason you would need to "go back" is if you had an application
that needed NT 4.0. If you keep the domain in Win 2k mixed mode it will
support a NT 4.0 BDC or member server that you can run the application on.
See:
http://support.microsoft.com/kb/322692/en-us
If the application MUST run on a NT 4.0 PDC, you would have that application
now so this domain would not be a candidate for upgrade. In this scenario
you would create a separate AD domain and create a trust between the AD
domain and the NT 4.0 domain. Of course in either case you should be
actively working to replace the application that only runs on an un
supported platform..


hth
DDS


"CryptiniteDemon" <CryptiniteDemon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:AC9C82DF-16B1-40B9-A41A-FE22F3FD3DEE@xxxxxxxxxxxxxxxx
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?


.

Relevant Pages

  • Re: When you have to backtrack and downgrade a DC
    ... The only reason you would need to "go back" is if you had an application ... Keep a BDC off line just in case. ... NT machines, of course, do revert back ... So is there any particular way to get one of these machines that's logged ...
    (microsoft.public.windows.server.general)
  • When you have to backtrack and downgrade a DC
    ... NT 4.0 to Server 2003. ... Keep a BDC off line just in case. ... NT machines, of course, do revert back to ...
    (microsoft.public.windows.server.general)
  • Re: Macs no longer overpriced - InfoWorld
    ... There was absolutely no relevance or reason for him to have divulged ... generic Windows box...or scrimping longer for the Mac Pro box. ... Mac by running it in Windows, ... gap between machines and a number of people would like to be somewhere in ...
    (comp.sys.mac.advocacy)
  • Re: Need tutorials, guides... However...
    ... The main reason for me to learn assembly is that i want to make ... performance loss you'll get from an OS like Windows or Linux. ... machines out there have gone off in many different directions. ... expect to find certain hardware at certain addressess. ...
    (alt.lang.asm)
  • Re: With Tiger is OS 9 pointless?
    ... >> No-one on this thread has given a reason to place OS X and OS 9 in separate ... >> partitions on machines which can't boot OS 9. ... > Or perhaps the users have no apps which need Mac OS 9, ...
    (comp.sys.mac.system)