RE: Windows NT to 2003 Migration Question

From: Gordon (Gordon_at_discussions.microsoft.com)
Date: 10/28/04 

Date: Thu, 28 Oct 2004 16:16:02 -0700

hi tony,

i would recommend sticking to your NT4 plan migration to w2k3. i read thru
your insert on the microsoft info and i don't understand all of it.

i have just completed a very similar upgrade path from NT4 to w2k3. i
purchased new server, installed nt4 sp6 as a BDC. upgrade BDC to PDC.
upgrade PDC to w2k3 with AD installed. i chose mixed mode w2k3 to be
backwards compatible with my other BDC and NT member servers. all is working
fine. i worked thru the MS post install test script and made sure that i had
an offline BDC just incase of i had to backup off the w2k3 install.

you are right about the size limitation, i am stuck for the time being with
the 4GB limit. i am going to get partition magic but i also have to
re-assign the first DC roles to another server before proceeding with
re-sizing the original 4GB.

good luck and check all the info before proceeding.

"Tony Scarola" wrote:

> Hello!
>
> We are in the process of planning our NT 4.0 to Windows 2003 network
> migration. We plan to perform an in-place upgrade, however our
> existing PDC is not capable of supporting Windows 2003. We have
> purchased two new beefy servers that will ultimately become root and
> second Domain Controller. From past Windows 2000 migration experience,
> to perform this type of upgrade, I have simply installed NT 4.0 on the
> new hardware as a BDC, then perform a role-reversal on existing PDC to
> BDC, move users/data, then upgrade new hardware to Windows 2000 and
> Active Directory. The problem I have run into with this type of
> upgrade is that the new hardware is becoming increasingly
> non-supportive of NT 4.0. Plus, there's the 4GB boot/system partition
> limitation that requires 3rd party software to expand after the
> initial install - something I'd rather not do.
>
> Upon researching this further I came across an article that Microsoft
> published in a document entitled "Upgrading from Windows NT Server 4.0
> to Windows Server 2003" in April of 2003. In this document, Microsoft
> states the following on page 13 in the section entitled "Performing
> In-Place Upgrades for Domain Controllers":
>
> "Domain controllers can be upgraded without implementing Active
> Directory, running the Windows Server 2003 servers in Windows NT 4.0
> compatibility mode. Because Windows Server 2003 Server is designed to
> support mixed networks with full interoperability, you do not have to
> upgrade all servers in a domain to take advantage of Windows Server
> 2003 features. Upgrading your PDC can simply be the fir st stage in
> the process-you gain additional, incremental benefits by upgrading
> your BDCs, and then your member servers. Once the network has been
> upgraded to Windows Server 2003, Active Directory can be implemented,
> but it isn't required."
>
> Also, on page 18 in the "New Hardware Replacement Deployment Scenario"
> section, Microsoft states:
>
> "New Hardware Replacement for Domain Servers
>
> When introducing new hardware for domain servers, you load the
> computer with Windows Server 2003, setting it for Windows NT 4.0
> compatibility mode, copy the user accounts from the Windows NT 4.0
> domain controller, and introduce the new server to the domain. An
> alternative is to completely build your Windows Server 2003
> infrastructure and then migrate user accounts to the directory."
>
> Can anyone explain what this means? From what it sounds like, I may be
> able to install the new hardware (that will ultimately become root and
> 2nd DC) as Windows 2003 and perform an upgrade without initially
> installing Active Directory?? How would we be able to maintain and
> migrate the SAM in this environment??
>
> Should I just stick with my original plan and install the new hardware
> as NT 4.0, then upgrade this to 2003?
>
> Any help would be appreciated.
>
> Thank you and regards,
>
> Tony Scarola
>

Relevant Pages

  • Re: Basic NT4 to w2k3 migration questions
    ... > The easiest way and the least disruptive is to upgrade your existing PDC ... If you can't do that then use the "advice". ... >> hardware and then upgrading it to w2k3 which sounds a bit idiotic to me. ... This includes a Windows 2003 Exchance server. ...
    (microsoft.public.windows.server.migration)
  • Defect in installer for Antivirus Corp Ed 9.0.1.1000 when upgrading from 9.0.0.x
    ... antivirus solution and have Windows XP desktops you'd like to upgrade to XP ... SP2 and wish to have the most recent build of SAV 9 that is XP SP2 compatible. ... to install to servers & PCs to provide XP SP 2 compatibility. ... Once you upgrade your Primary Server to 9.0.1.1000 and attempt to ...
    (NT-Bugtraq)
  • Re: 2008 or 2003
    ... To install a 2008 DC in a 2003 domain the schema has to be upgraded to version 44. ... The schema is the same in your complete domain, the schema upgrade will add additional AD objects which are needed for 2008. ... 2008 ad schema instead of setting it up as a 2003 AD server I need all ...
    (microsoft.public.windows.server.setup)
  • RE: DNS Question on NT4 to AD upgrade
    ... With the dell you can install NT4.0 it is just is not supported by dell. ... Then perform your upgrade on the NT 4.0 Machine although this ... pointing to the new WINS server on the first dhcp scope. ...
    (microsoft.public.win2000.active_directory)
  • Re: Exchange SP1 stopped all smtp traffic
    ... Cannot upgrade virtual server http://stargate:80. ... al server to a new virtual server extended with Windows SharePoint Services. ... Installation fails and mail flow stops when you install Exchange Server 2003 ...
    (microsoft.public.windows.server.sbs)