Re: NT4 and W2K3 Questions

No, the only in-place upgrade path is to install Windows Server 2003 on the
NT4.0 PDC. This does not have to be your present PDC. For example, you
could install NT4.0 as a BDC on your present Windows 2003 machine and then
promote it to PDC; then upgrade to Windows Server 2003. See:

http://support.microsoft.com/kb/326209/en-us

and

http://download.microsoft.com/download/3/6/3/363161ea-f975-47e1-bce0-39d07d0
d175a/NT4toWS03.doc

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"soto" <somethingortheother@xxxxxxxxx> wrote in message
news:1139672946.925059.176060@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello All:

I have 2 NT4 boxes (configured as a PDC and BDC.) I have a new W2K3 to
switch over to.

Is there a way to bring up the W2K3 box (which is right now a stand
alone server in the NT domain), as a "backup" domain controller, with
the eventual goal of it becoming the "primary" for the entire domain
(which will then allow me to demote/shutdown the two NT4 controllers?)

When I run the AD wizard on the W2K3, I choose "Additional domain
controller for existing domain," I then get a prompt for user/pass with
enough priv to install AD on this (the 2K3 box) computer, and I key in
my admin user/pass and click Next..

I then get an error dialog box popup saying:

AD Installation Wizard

An AD domain controller for the domain XYZ cannot be contacted, Ensure
that the DNS name is typed correctly (what DNS name, we're joinging an
NETBIOS/NT4 domain, no?)
If the domain is correct, then click Details for troubleshooting info.

Clicking Details:

The domain name XYZ might be a NETBIOS domain name (it is! it is!) if
this is the case, verifty that the domain name is properly registered
in WINS (huh? how is this done, I don't use WINS in the first place)

Message then proceeds with if you are certain that the name is not
NETBIOS.....so on and so forth

OR, is it not possible to have a W2K3 domain controller in a LAN where
there is already a PDC and BDC running NT4?

The eventual goal is that the W2K3 box will be an AD domain controller
and the NT4 boxen shut down.

Any thoughts/comments would be helpful.



.

Relevant Pages

  • Re: Blank Forest Functional Level - Unable to fix
    ... I would start looking very closely at all DCs to verify that the same DC is set for the PDC master. ... I promoted a Windows Server 2003 SP1 server to a domain controller. ... Anyway, you could be running into something odd when raising the forest functional level and even though it isn't required for R2, I will offer a command line mechanism to do it that will kick out an error message that can be used to work out the issue. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT4 --> 2003 , lmhosts?
    ... if you have PDC and several BDCs ... > With regards to the lmhost, do you mean certain client use lmhost to ... > 4.Upgrade the new PDC to Windows Server 2003. ... and bring it online as an Active Directory domain controller. ...
    (microsoft.public.windows.server.migration)
  • Migration Approach in NT4 to Win2K3 AD
    ... Promote this NT4 Domain Controller to PDC, which demotes the PDC to a BDC. ... Use the Windows Server 2003 Active Directory wizard to turn on the Active Directory service. ...
    (microsoft.public.win2000.active_directory)
  • Re: Problems with Domain Replication
    ... Install Windows Server Support Tools found at your Windows Server CD, ... it will help you to ensure the domain controller is registered. ... > Is the new DC pointing to the other one for DNS and vice versa? ...
    (microsoft.public.win2000.active_directory)
  • Re: Migration to SBS 2003
    ... the PDC to a BDC. ... >Upgrade the new PDC to Windows Server 2003. ... turn on the Active Directory service. ... Active Directory domain controller. ...
    (microsoft.public.backoffice.smallbiz2000)