Re: Upgrade of 2003 member server in NT domain



"ReadyForThis??" <ReadyForThis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8FEC0EC9-3922-4A81-A1D5-6BA1E8384930@xxxxxxxxxxxxxxxx
>I currently work for an organisation that has an NT domain consisting of 1
>NT
> PDC, 2 NT BDC's and 1 Windows Server 2003 member.
>
> The PDC and BDC's have nothing on them. They are only there to
> authenticate
> user logins.
>
> They tried to install NT on the 2003 machine but it wouldn't take it so
> they
> made it a 2003 member of the NT domain.

That is highly unlikely -- any hardware that will run
Win2003 is almost guaranteed to work with NT (with
the possible exception of some drivers which can usually
be worked around.)

BUT, if it is really the case then you need a machine that
can become a WinNT BDC (then promote to PDC) and CAN
be upgraded to Win2003. You only need this machine to
remain temporarily and their is plenty of obsolete hardware
for very little money that can do this.

> The 2003 server is the file/print machine with all user shares and data
> files stored on it along with all network printers.
>
> I need to upgrade the 2003 machine to become the DC and install AD on it
> but

You cannot do that. There is no path to upgrade a non-DC under
WinNT nor is their way to upgrade an NT domain EXCEPT by
upgrading the PDC.

Everything else involves a 'migration' to a NEW domain which
is almost always less desirable than the (true) upgrade you
are (correctly) trying to perform.

> I don't want to destroy the files or printers already installed. This will
> then allow me to turn off the NT boxes (I hope)!
>
> How can I go about this without causing too much, if any disruption to the
> users?

Get a machine that will run NT AND will run Win2003. Maybe the
current NT PBD (or BDCs) will do that.

If it is a new machine, install NT4 as a BDC (only way to get a DC
into a WinNT domain is to do it at install time.)

If it is a BDC, promote it to PDC.

Once you have a PDC that can run Win2003, perform the upgrade.

NOW the other Win2003 Server can also be promoted (DCPromo)
to another Win2003 DC.

At that point you may keep or remove the original (PDC upgraded)
DC.

Be carefull to make sure the 5-FSMO roles, the GC, and your DNS
are transferred or working on the remaining DC before you do that
though.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

>
> Gary


.



Relevant Pages

  • Re: DNS replication when installing new DC in domain
    ... > and a Broadcom ethernet NIC is impossible, as there are no drivers for NT4 ... "promote offline to PDC" that is from this line of your original ... then upgrade to Win2k3 SP1 on that temp machine. ... prefer -- either right after install or later. ...
    (microsoft.public.windows.server.dns)
  • Re: Upgrade of 2003 member server in NT domain
    ... > installing AD during the upgrade. ... > is complete I can turn off the upgraded machine (original BDC)? ... >>> The PDC and BDC's have nothing on them. ... >>> They tried to install NT on the 2003 machine but it wouldn't take it so ...
    (microsoft.public.windows.server.migration)
  • Re: Upgrade of 2003 member server in NT domain
    ... Can I not promote a BDC to PDC and then upgrade that machine to 2003, ... >> I need to upgrade the 2003 machine to become the DC and install AD on it ...
    (microsoft.public.windows.server.migration)
  • Re: NT PDC can no longer administer users it its own domain but can in others.
    ... Yes WINS is installed on the BDC and has been running fine. ... >> The PDC also had the NT Gateway for Netware service installed, ... However I get the same error message every time I try to select ... >> install process, it gave me an error message.. ...
    (microsoft.public.windows.server.general)
  • Re: Suggested reading nt4 to server2003
    ... i will then be migrating the pdc to a fresh win2k3 server with ad. ... compatible with the new pdc until i load up and migrate the new bdc, exchange ... > If you want to perform an in-place upgrade on BDC with Exchg 5.5 installed, ...
    (microsoft.public.windows.server.migration)