NT4 to 2003 upgrade - client setup

Discussion in 'Active Directory' started by drzaius2000, Feb 16, 2010.

  1. drzaius2000

    drzaius2000 Guest

    I am performing an upgrade from NT4 to 2003 and have done a bit of testing
    but I am still unsure of the behavior of workstations and servers when they
    suddenly find themselves on an upgraded domain.

    Currently, the plan is this:

    1. Take a NT4 BDC on a virtual machine and upgrade it to 2003. Add
    NT4Emulator key.
    2. Configure DNS, etc. Verify everything transferred over. Remove
    NT4Emulator key.
    3. Reboot.
    4. Configure clients to use new DNS server.
    5. Shutdown all other NT4 BDCs.

    Im uncertain at what happens between steps 3 and 4. Will the workstations
    continue to be able to authenticate on the domain before I change their DNS?
    On my test machine, it looks like hung up, so I was forced to reboot it
    before it accepted being a member of the AD domain. I could see its domain
    name changed from "domain" to the FQDN I chose "domain.local".

    Are reboots required? Will there be interruption of service?

    drzaius2000, Feb 16, 2010
    1. Advertisements

  2. Hello drzaius2000,

    See the answer in microsoft.public.windows.server.migration and pleaase avoid
    multiposting, use crossposting instead with a newsreader like outlook express
    or windows mail.

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Feb 17, 2010
    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.