Re: Upgrading from NT 4.0 to 2000 server

From: Danny Sanders (Danny.Sanders_at_NO-SPAMcpcmed.org)
Date: 12/08/04


Date: Wed, 8 Dec 2004 11:26:19 -0700

Or, you could just bring
> your windows 2000 member server up as a backup domain controller, then
> promote it to the pdc, and remove the old ones.

This will not work.

There is no such thing as a Win 2k BDC. DCs in AD operate in the multimaster
mode. Except for the 5 FSMO roles that can be transferred between them, all
AD Dcs are equal.

In NT 4.0 the NT 4.0 PDC is the only DC that carries a writeable copy of the
SAM, You MUST upgrade the existing NT 4.0 PDC to AD first in order to carry
this copy of the SAM into the Win 2k Domain. Upgrading or promoting *any*
*other* BDC/member server to Win 2k and AD will create a new copy of the
SAM. New SAM = new domain. You will have to add each user to the new domain,
new profiles will be created.

If you can not upgrade your existing PDC first I would suggest you remove
Win 2k from the new server and install NT 4.0 on it as a BDC while connected
to your existing domain (SAM is replicated to this BDC in read only form).
Promote to PDC (SAM becomes writeable) upgrade to Win 2k and AD.
See:
How to Upgrade Windows NT Server Version 4.0 to Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;298107

Or you can set up the two domains side by side on the same wire and use ADMT
to move users from the NT domain to the AD domain.
See:
How to Set up ADMT for Windows NT 4.0 to Windows 2000 Migration
http://support.microsoft.com/default.aspx?scid=kb;en-us;260871

The ADMT requires a trust between the two domains. You can not creat a trust
between two domains with the same name. If you need to keep the same domain
name this may not be your best bet. If you MUST use ADMT I would suggest
renaming the NT domain to something different. You can't really rename a Win
2k domain easily.

In order for AD to work you MUST have DNS set up correctly.
See:

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

For Internet access See:
How to configure DNS for Internet access in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

hth

DDS W 2k MVP MCSE

"bob" <gbob@bob.com> wrote in message
news:pan.2004.12.08.18.03.07.555737@bob.com...
> On Wed, 08 Dec 2004 09:53:04 -0800, Traci wrote:
>
> > I am purchasing a new server and will have 2000 server on it and I need
to
> > know how to backup up my domain information from NT 4.0 so I can
transfer it
> > to my new server? I didn't want to have to reenter all the members and
> > permissions on the new server. Any information would be greatly
appreciated.
>
> You can use the active directory migration tool. Or, you could just bring
> your windows 2000 member server up as a backup domain controller, then
> promote it to the pdc, and remove the old ones. you need to get dns sorted
> out before them. This is a topic that can not be fully explained in depth
> in one email. There are white papers/guides on www.microsoft.com/technet.
> There is also a "certification" upgrading windows nt to 2000 that will
> have the basic info for you.
>
>



Relevant Pages

  • RE: fallback solution for NT 4.0 upgrade
    ... Regarding the backup of SAM database, I would like to suggest some ... Using REGBACK will copy the records from the SAM into a new file. ... BACKUP directory already exists on drive C, and Windows NT is also ... | I have an NT 4.0 server I'd like to upgrade to 2000. ...
    (microsoft.public.windows.server.migration)
  • Re: Cannot Use System Infomation Function
    ... Most welcome, Sam. ... Scroll down to Server and make sure it is started. ... Troubleshooting Windows XP ... > I should mention also that when I close the System Information program, ...
    (microsoft.public.windowsxp.general)
  • Re: Restoring Trusts between client workstations and Domain Contro
    ... copying and pasting a backup of their "Windows Special Folder"? ... >> the server without the benefit of recent backup of SAM and SID's. ... >> go about restoring communication between the client workstations (they ...
    (microsoft.public.windows.server.general)
  • Re: NT4 > Win 2003 Server
    ... When two different Windows NT Advanced Servers or Windows NT Servers in a ... I think the most convenient upgrade solution is install Windows NT BDC on ... the new server, promote it to PDC and then inplace-upgrade it to Windows ...
    (microsoft.public.windows.server.migration)
  • RE: NT4 to Server 2003 Migration
    ... Windows 2003 but the new hardware will not support Windows NT 4.0. ... It will only be used as a transition server. ... | functions, too), 1 PDC, and a few member ...
    (microsoft.public.windows.server.migration)