From: John Cuccia 

A 180-day evaluation copy should work for the upgrade.

The  Windows 2000/2003 analog to promoting a machine to PDC is assigning
all FSMO roles to it:
http://support.microsoft.com/kb/324801

Once satisfied that the new server is working, be sure to demote (using
DCPROMO) the old BDC before taking it off-line, to prevent an orphaned
entry in the new Active Directory domain;
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/prod
docs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/p
roddocs/en-us/sag_ADdemoteDC.asp

And, of course, make sure you can restore your NT4 domain should something
go awry.  You could build a new NT4 BDC, make sure the database is
replicated to it, then take it off-line for safekeeping. If the upgrade
fails, you can unplug the failed upgrade, plug in the backup, and promote
it to PDC.

You'll need to pick a DNS name for the domain, so will have to decide if
you want to use a real domain name (your company's?) or a dummy. Windows
Server 2003 Administrator's Companion (ISBN 0-7356-1367-2) by Microsoft
Press, is an excellent reference.  Look in particular at Chapter 6,
"Upgrading to Windows Server 2003" and Chapter 13,
"Installing and Configuring Active Directory".

On Mon, 28 Feb 2005 18:17:29 -0500, "Geo"  wrote:

>I'd upgrade the NT4 machine (PDC) to 2003 then I'd bring the new 2003 server
>online and promote it to PDC then take the old machine offline. I think you
>can get away with that if you never activate the upgrade machine.
>
>Geo.
>
>"Richard B."  wrote in message
>news:n42721huv2nd2p78mfa37egd9u4fhrmv53{at}4ax.com...
>> I'm going to replace my NT4 PDC with a new Windows 2003 box in a month
>> or so.  I want the new machine to be the new DC.
>>
>> I also currently have a single NT4 BDC and a mix of standalone
>> 2000/2003 servers.  I have one of the latter in a remote office.
>>
>> What would be the best way to do this?
>>
>> TIA,
>>
>> - Richard
>

--- BBBS/NT v4.01 Flag-5