AD 2003 - moving from 32 bit Ent to 64 bit Ent servers

Discussion in 'Active Directory' started by LKN2PLA, Sep 22, 2008.

  1. LKN2PLA

    LKN2PLA Guest

    I've been reading anything and everything on this issue and it seems I'm
    going in circles.
    What I want to do is Migrate my 2 2003 32 bit AD/DNS/DHCP/WINS to 2 2003 64
    I've setup replication between all 4 and that appears to be working just fine.
    However, as soon as I promote 1 64 bit server and turn down the 32 bit
    servers, the only thing working is DHCP / WINS. AD / DNS stop working.

    I've seen several articals on the ADMT 3.x but it all 'eludes to' a 2003 32
    bit to 2008 64 bit migration.
    Any thoughts?
    LKN2PLA, Sep 22, 2008
    1. Advertisements

  2. What DNS server do the new X64 servers point to for DNS? Is that server up
    and DNS running?

    Danny Sanders, Sep 22, 2008
    1. Advertisements

  3. Hello LKN2PLA,

    Please post an unedited ipconfig /all from all 4 servers.

    Best regards

    Meinolf Weber
    Meinolf Weber, Sep 22, 2008
  4. Jorge de Almeida Pinto [MVP - DS], Sep 22, 2008
  5. LKN2PLA

    Mel K Guest

    Does it matter if the servers are 32 and 64 bit? The way AD and the other
    services function is the same whether it's 32 or 64 bit? I understand that
    64 bit can use more RAM so maybe it can scale better, but I don't think the
    AD/DNS/DHCP/WINS functionality is any different. Can someone confirm this?
    Mel K, Sep 23, 2008
  6. Hello Mel,

    32bit and 64bit can coexist without any problem.

    Best regards

    Meinolf Weber
    Meinolf Weber, Sep 23, 2008
  7. 32 and 64 should be able to comingle nicely, ths sounds more like a
    configuration setting such as dns improperly defined, etc...

    Run diagnostics against your Active Directory domain. I would do this both
    before and after a promotion of one of the 64 bit dc's.

    If you don't have the support tools installed, install them from your server
    install disk.

    Run dcdiag, netdiag and repadmin in verbose mode.
    -> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
    -> netdiag.exe /v > c:\netdiag.log (On each dc)
    -> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
    -> dnslint /ad /s "ip address of your dc"

    **Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
    in the forest. If you have significant numbers of DC's this test could
    generate significant detail and take a long time. You also want to take
    into account slow links to dc's will also add to the testing time.

    If you download a gui script I wrote it should be simple to set and run
    (DCDiag and NetDiag). It also has the option to run individual tests
    without having to learn all the switch options. The details will be output
    in notepad text files that pop up automagically.

    The script is located on my website at

    Just select both dcdiag and netdiag make sure verbose is set. (Leave the
    default settings for dcdiag as set when selected)

    When complete search for fail, error and warning messages.

    Description and download for dnslint
    Paul Bergson [MVP-DS], Sep 24, 2008
    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.