Re: Fallback to NT4 - Clients won't talk to Domain

From: Herb Martin (news_at_LearnQuick.com)
Date: 07/07/04


Date: Wed, 7 Jul 2004 10:38:25 -0500

The registry entry is the one he mentioned and is apparently
only useful BEFORE the upgrade.

-- 
Herb Martin
"Paul" <country-air@news.postalias> wrote in message
news:27ecc01c4640a$ea789c80$a501280a@phx.gbl...
> Herb - did you have that registry entry, please? Or did
> the message from MS scupper it?
>
> Paul
>
>
> >-----Original Message-----
> >"Paul" <country-air@news.postalias> wrote in message
> >news:25e6001c4627f$57765d00$a601280a@phx.gbl...
> >> We have been experimenting in the lab with the UPGRADE
> >> route for converting our NT4 domain to Active Directory.
> >> One of the reasons we were attracted to this route was
> the
> >> claimed ability (in the Migration Cookbook) to fallback
> to
> >> the original domain by removing the new W2K DCs and
> >> replacing with the stored NT4 PDC. This all works OK,
> >> except...
> >>
> >> Any WXP client which has logged in to the new AD doesn't
> >> want to play with the 'fallen'back' NT4 domain. It says
> >> that it can't find a [NT4] domain controller. Indeed,
> the
> >
> >There is a feature/setting in XP that causes it to "latch
> onto"
> >Win2000+ DCs.
> >
> >It's a registry entry to put it back -- someone will post
> it
> >today or tomorrow in this thread, but you can look it up
> on
> >the MS website through search Google with something like:
> >
> >    [ site:microsoft.com  XP 2000 | 2003 DC BDC | PDC
> registry]
> >
> >I don't know if that will get it to the top but it will
> likely be in
> >there somewhere.
> >
> >Oh, and it's a "feature" because this lets the news
> clients get
> >their Group Policy and full AD benefits.
> >
> >-- 
> >Herb Martin
> >
> >
> >"Paul" <country-air@news.postalias> wrote in message
> >news:25e6001c4627f$57765d00$a601280a@phx.gbl...
> >> We have been experimenting in the lab with the UPGRADE
> >> route for converting our NT4 domain to Active Directory.
> >> One of the reasons we were attracted to this route was
> the
> >> claimed ability (in the Migration Cookbook) to fallback
> to
> >> the original domain by removing the new W2K DCs and
> >> replacing with the stored NT4 PDC. This all works OK,
> >> except...
> >>
> >> Any WXP client which has logged in to the new AD doesn't
> >> want to play with the 'fallen'back' NT4 domain. It says
> >> that it can't find a [NT4] domain controller. Indeed,
> the
> >> client's domain name has 'automatically' changed to the
> >> name of the AD domain and also the preferred DNS server
> >> has been altered. The event log says specifically that a
> >> downgrade is being attempted, and it is necessary for
> the
> >> client to rejoin the NT4 domain.
> >>
> >> Have we missed something? The Cookbook seems quite
> >> insistent that you can fall back in this manner! Is
> there
> >> an easy way to move all the clients back to the NT4
> domain
> >> without visiting them all?
> >>
> >> Incidentally, if we did find a way to rejoin the NT4
> >> domain for all our clients, then presumably we wouldn't
> be
> >> able to re-migrate them to AD without starting from
> >> scratch, because the upgraded W2K DC would no longer
> have
> >> valid machine accounts for the clients (different SIDs)?
> >>
> >> Paul
> >
> >
> >.
> >


Relevant Pages

  • Re: DNS replication when installing new DC in domain
    ... > and a Broadcom ethernet NIC is impossible, as there are no drivers for NT4 ... "promote offline to PDC" that is from this line of your original ... then upgrade to Win2k3 SP1 on that temp machine. ... prefer -- either right after install or later. ...
    (microsoft.public.windows.server.dns)
  • Re: Anmeldevorgang in einer Misch Umgebung (inplace Upgrade NT4 --> W2003)
    ... WOHER zum teufel erfahren die Clients in der Zweigstellt und wie vro allen ... es wird ja NT4 PDC emuliert. ... Die melden sich gegen den BDC an ... Der PDC in der Zentrale ist niemals abgeschottet. ...
    (microsoft.public.de.german.win2000.active_directory)
  • Re: Fallback to NT4 - Clients wont talk to Domain
    ... >> We have been experimenting in the lab with the UPGRADE ... >> route for converting our NT4 domain to Active Directory. ... >> an easy way to move all the clients back to the NT4 ...
    (microsoft.public.win2000.active_directory)
  • ** Please Advise ** NT4 -> 2003 Upgrade Plan !!
    ... Going to upgrade NT4 domain to 2003 AD. ... All was ok except the fallback test with a laptop from the NT4 domain. ... includes PDC and one BDC in main office. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT4 Single Domain to 2K3 Active Directory
    ... I just did the steps you outlined for upgrading the NT4 to win 2003 .. ... > still a PDC emulator which acts like a PDC for NT4 clients and does some ... these will be the servers your clients point to for DNS. ... >> We're planning an upgrade for a client with a single domain. ...
    (microsoft.public.windows.server.migration)