same domain name in migrating from Win Nt4 to Win 2K3

Discussion in 'Windows Server' started by Jack, Jun 24, 2004.

  1. Jack

    Jack Guest

    Hi All,

    I am preparing to migrate our current Win NT4 PDC to Win
    2K3 using ADMT2 for migrating accounts etc. I want to know
    whether I can set up the new DC with the same domain name
    in migration from Windows NT4 to Windows 2003. That is to
    say when I run the AD wizard, I want to select DC in a new
    domain and use the name of the current domain. I want to
    do this so that there would not be much changes to user
    logon, etc. I cannot upgrade because the current server
    does not meet the requirements. Any help is appreciated
    before I blow it up.

    Thanks for your assistance.

    Jack.
     
    Jack, Jun 24, 2004
    #1
    1. Advertisements

  2. If you are happy with the design of your current NT4 doamin, then you
    should:

    - Install your new server as Wndows NT4 BDC.
    - Promote your new server to become PDC
    - Disconnect your old NT4 DC from network. This is now your old BDC and you
    will use it in case you need to fail back to old configuration. Don't
    connect it to the network again.
    - Upgrade your new server to Windows Server 2003. During the upgrade process
    it will become domain controller in Active Directory domain in mixed mode.
    - When you upgrade all NT4 domain controllers in your domain to be at least
    Windows 2000, you may raise domain level to Windows 2000 native mode.
    - When you upgrade all domain controllers in your domain to run on Windows
    Server 2003 (ie, no NT4 or Windows 2000 DC's), you may raise forest level
    and domain level to Windows 2003 level.

    Dusko Savatovic
     
    Dusko Savatovic, Jun 24, 2004
    #2
    1. Advertisements

  3. Jack

    Guest Guest

    Thanks Dusko,

    Well, I thought about this but I have a couple of
    questions along this route:
    - currently I dont't have DNS installed on the NT4 PDC
    and at what stage would I have to intall it for the AD to
    work well during upgrade?
    - Do I just run dcpromo on the newly installed NT4 BDC to
    promote it to a PDC without doing anything to the PDC, or
    it has to be offline?

    With clarity on these issues I will follow your route.

    Thanks for your time and saving another folk his job.

    Jack.
     
    Guest, Jun 24, 2004
    #3
  4. Jack

    Jack Guest

    Thanks Dusko,

    Well, I thought about this but I have a couple of
    questions along this route:
    - currently I dont't have DNS installed on the NT4 PDC
    and at what stage would I have to intall it for the AD to
    work well during upgrade?
    - Do I just run dcpromo on the newly installed NT4 BDC to
    promote it to a PDC without doing anything to the PDC, or
    it has to be offline?

    With clarity on these issues I will follow your route.

    Thanks for your time and saving another folk his job.

    Jack.
     
    Jack, Jun 24, 2004
    #4
  5. Inline
    If dcpromo does not detect valid DNS service, it will offer to install it.
    On simple networks it is just best to let it do all the work automatically.
    You cannot run dcpromo on NT4. Sorry, my NT4 memory is somewhat rusty, but
    somewhere in Server Manager (or is it User Manager for Domains?) you should
    say that you wish to promote your current BDC (your future 2k0/2k3 box) to
    PDC. This process will automaticaly demote your current NT4 box to BDC role.
    Having done that you disconnect old NT4 box from the network and you don't
    connect it anymore. With this setup you have frozen state of your network
    that existed at the time when BDC was disconnected.

    On your new box, you then start upgrade install of Win2k/2k3 Server. The
    upgrade process detects that you are running on PDC and will invoke dcpromo
    somewhere along the route.

    Good luck,
    Dusko Savatovic
     
    Dusko Savatovic, Jun 24, 2004
    #5
  6. Something more about DNS.

    Primary name resolution on NT4 networks is NetBIOS (with WINS).
    Primary name resolution on Win2k/2k3 networks is DNS.
    For backward compatibility Win2k/2k3 still supports NetBIOS.

    If your NetBIOS domain name was BRANDX, when you upgrade to Win2k/2k3 you
    would have to add DNS domain name too. If your domain name is private, you
    would typically name your domain BRANDX.local.

    The diferrence between NT4 DNS and Win2k/2k3 DNS is that Win2k/2k3 DNS is
    used to locate services (SRV resource records). NT4 does not support SRV
    records. Hence, you cannot use NT4 DNS for Active Directory domains.

    DNS in Win2k/2k3 can also be dynamic. This means that you don't need to
    enter any SRV resource records manually, but the system will do it
    automatically (if you let it).
    If something goes wrong, the typical steps would be.

    a) Install DNS on Win2k/2k3 server.
    b) point all hosts on the network to use your new DNS server.
    c) On DNS, install forward lookup zone. Name it BRANDX.local
    d) Adjust properties on BRANDX.local to allow automatic updates.
    e) From command prompt, run:
    ipconfig /registerdns
    net stop netlogon
    net start netlogon
    f) Observe records in your BRANDX.local zone. You should be getting SRV
    records for dc, gc, keberos, ldap etc.

    There's more

    Dusko Savatovic
     
    Dusko Savatovic, Jun 24, 2004
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.