Re: Fallback to NT4 - Clients won't talk to Domain
From: CJ (chrisj_at_illicom.net)
Date: 07/09/04
- Next message: Brian Desmond [MVP]: "Re: disable and disconnect user(s)"
- Previous message: Greg: "disable and disconnect user(s)"
- In reply to: Paul: "Re: Fallback to NT4 - Clients won't talk to Domain"
- Next in thread: CJ: "Re: Fallback to NT4 - Clients won't talk to Domain"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 09 Jul 2004 02:49:31 GMT
Guys, forget the registry entry, just see my solution.
It is exactly what I did when going from an AD system back to NT domains.
"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
> >
> >
> >.
> >
- Next message: Brian Desmond [MVP]: "Re: disable and disconnect user(s)"
- Previous message: Greg: "disable and disconnect user(s)"
- In reply to: Paul: "Re: Fallback to NT4 - Clients won't talk to Domain"
- Next in thread: CJ: "Re: Fallback to NT4 - Clients won't talk to Domain"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|