Re: Moving NT4 based PDC and BDC to Win2k

From: David Brandt [MSFT] (nospam_at_microsoft.com)
Date: 02/05/04


Date: Thu, 5 Feb 2004 10:52:15 -0600

The "easiest" way to move to AD is to just upgrade your pdc. In your case
with the new hw, you'd install one of those boxes as an nt4 bdc, promote it
to pdc, and then upgrade to 2k. You can also create a "new" win2k domain,
set up trust/s between that 2k domain and your nt domain, and then use
ADMTv2 to migrate to the 2k domain. The upgrade route is the
quickest/easiest though I believe. However I'd encourage you to read up on
the info from the following links if you haven't already, as 2k is a bit
different from nt.

http://search.microsoft.com/search/results.aspx?st=b&View=en-us&na=82&qu=admt

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/ad/windows2000/plan/migntw2k.asp

note; there is a ton of info on the web site that covers just about anything
you'd need.

-- 
David Brandt
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
"Dale" <anonymous@discussions.microsoft.com> wrote in message
news:ac2501c3ec05$cc3569b0$a501280a@phx.gbl...
> We are totally Win2k with the exception of our PDC and BDC
> servers which are NT4 and have remained in place only for
> this function.  We are planning on retiring these servers
> (2) and not upgrading the hardware, but instead move the
> functions either to a new dedicated AD box or to another
> existing Win2k server.  Not sure if a dedicated AD box is
> needed or recommended.
>
> What is the easiest way to move to AD with a Win2k server
> handing the DC functions, and retire these old NT4 servers?
>
> In our environment users do not log directly into Win2k
> servers but rather authenticate to eDirectory.  Win2k
> servers are used for applications rather than
> file/print/authentication which is handled by NetWare.
>
> Thx
> Dale


Relevant Pages

  • Re: NT4 to Win 03
    ... Easies is to upgrade your existing PDC. ... you have to set the AD domain in Native mode. ... If you upgrade you do not have to set your AD domain in native mode. ... > assume i will install the new 2003 servers one at a time. ...
    (microsoft.public.windows.server.migration)
  • Re: NT4 to Win 03
    ... > users access to NT 4.0 file/application servers, ... In other words, if I upgrade my ... replication between NT 4.0 BDCs and AD DCs in the same domain. ... > the NT domain to the AD domain, or upgrade, by upgrading the NT PDC first. ...
    (microsoft.public.windows.server.migration)
  • Re: NT Server 4.0 to Server 2003 deployment
    ... > Of these seven servers one is my PDC and the other is my BDC. ... > have done research and one of the common methods is to install ... To upgrade your domain see the post I posted somewhere else. ...
    (microsoft.public.win2000.setup_deployment)
  • Re: NT Server 4.0 SP6a to Server 2003
    ... > Of these seven servers one is my PDC and the other is my BDC. ... > have done research and one of the common methods is to install ... To upgrade your domain see the post I posted somewhere else. ...
    (microsoft.public.win2000.setup_upgrade)
  • Re: Moving NT4 based PDC and BDC to Win2k
    ... I agree with your upgrade ... introduce a newer hardware NT4 machine, ... create several DC's on other existing Win2k servers so ... necessary (nothing runs on the existing NT4 servers except ...
    (microsoft.public.win2000.active_directory)