Re: Migrating NT 4 PDC to Exisitng Win 2000 AD

From: gmickelsen (gmickelsen_at_discussions.microsoft.com)
Date: 08/18/04 

Date: Wed, 18 Aug 2004 01:37:01 -0700

Thanks Dinesh.
There is an exisitng Win 2000 AD on the same LAN as the PDC. What I would
like to do is to merge the NT domain into the new AD domain. I was hoping I
could just upgrade it, and dcpromo it to join the exisiting AD domain. I was
hoping that this would migrate all the users. It seems that this won't work
though from a current PDC. I assume I need to use ADMT to migrate the users
from the PDC to the new domain first?
What would the next step be in moving this NT domain to the AD domain?
I then have other NT domains to migrate to this single AD domain. I assume I
can then follow the same process for each as I do for the first?

Many thanks in advance.

"Dinesh Tashildar" wrote:

> If it is first domain contoller (Windows 2000 enviroment) then it will got
> give you option for "Addtional domain controller for an exisitng domain"
>
> Is it your first domain contoller (Windows 2000 enviroment)?
>
> -Dinesh
>
>
> "gmickelsen" <gmickelsen@discussions.microsoft.com> wrote in message
> news:BBC062EC-4FBB-4A46-A90A-9E73D97E0D9D@microsoft.com...
> >I recently attempted an upgrade from Win NT to Win 2000 on a DELL PowerEdge
> > Server. This server was a PDC for our NT domain. What I intend doing is to
> > make this join an exisiting 2000 AD domain when upgraded.
> > The upgrade to Win 2000 worked fine but then on running DCPROMO, I
> > expected
> > the option: "Addtional domain controller for an exisitng domain" as I had
> > done during testing. I could then have specified the domain I wanted this
> > DC
> > to join. However, I was only given the options "Create a new domain tree"
> > or
> > "Create a new child domain in an exisitng domain tree". These were not the
> > options I expected or wanted.
> > Would anyone be able to offer any advice on why I had these different
> > options?
> > Are there any steps to take before the upgrade from NT to 2000 (e.g. DNS
> > changes...)?
> >
> > Many thanks
>
>
>

Relevant Pages

  • Re: NT4 to Server 2003 Migration
    ... based on everything you've said here, I would hire an experienced consultant, if only to assist you in the planning stage. ... I would not upgrade your current PDC to 2003. ... it's only 4-8 gig, not nearly large enough for 2003 server with SP1, and future service packs & upgrades. ... BDC 1 - RAS, Print Server, File Storage ...
    (microsoft.public.windows.server.migration)
  • Re: Windows Time Service: What if the PDC-role is moved?
    ... NTP - use the time source specified in the NtpServer Value ... I suggest using the w32tm command for modifying the time service parameters rather than directly modifying the registry entries. ... switch that takes priority and tells it to acquire NTP server info ... Doesn't he has to have the PDC DNS-name or IP-address in it? ...
    (microsoft.public.windows.group_policy)
  • Re: wrong time server
    ... It does not query what the local machine's time service is set to use with the domain hierarchy. ... It's rather useless trying to use it to find which server is the client's time service. ... All client desktops select an authenticating domain controller ) as their time source. ... The PDC of the current domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows NT to 2003 Changeover Questions
    ... > PDC, then bring up the potential 2003 PDC and see if we can get the other ... The NT 4.0 PDC is the ONLY server on a NT domain that holds a writeable copy ... How To Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003-Based ... You should also read up on the DNS requirements of AD. AD absolutely must ...
    (microsoft.public.win2000.setup)
  • Re: PDC/BDC problem
    ... Even com away from PDC and BDC. ... So which server from you has which role in the moment? ... I tried everything to reestablish the trust. ...
    (microsoft.public.win2000.networking)