Adding target domain on source domain's workstation for migration

Discussion in 'Server Migration' started by Curtis Fray, Aug 25, 2004.

  1. Curtis Fray

    Curtis Fray Guest

    Hi,

    I was having trouble migrating computers across to a new domain until I
    found the source workstations need to be able to resolve the full domain
    name of the new 2003 domain (ie, abc.com). I can resolve this by specifying
    the target domain's DNS server as the source workstations primary DNS
    server. However, due to the amount of workstations I have to do this isn't
    really practical. Does anyone know if it's possible to specify the full DNS
    domain name in HOST or LMHOST files?

    I have already set the target domain's NETBIOS domain name in the lmhost
    file of the client machine, but this doesn't appear to be sufficient for its
    migration. It seems to require the full DNS domain name.

    Thanks,

    Curtis.

    ====================================
    When replying by email please remove the X
    ====================================
     
    Curtis Fray, Aug 25, 2004
    #1
    1. Advertisements

  2. Hi Curtis,

    Thanks for your posting here.

    I would like to recommend that you point your Windows 2003 DC to the NT
    WINS server and createa a secondary zone on Windows NT DNS server for the
    Windows 2003 domain. Then you can keep the clients pointing to the NT DNS
    server.

    If the problem still persists, please let me know the detailed error
    message in migration log and I will do further research.

    Regards,
    Bob Qin
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security

    ====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    From: "Curtis Fray" <>
    Subject: Adding target domain on source domain's workstation for
    migration
    Date: Wed, 25 Aug 2004 12:31:08 +0100
    Newsgroups: microsoft.public.windows.server.migration

    Hi,

    I was having trouble migrating computers across to a new domain until
    I
    found the source workstations need to be able to resolve the full
    domain
    name of the new 2003 domain (ie, abc.com). I can resolve this by
    specifying
    the target domain's DNS server as the source workstations primary DNS
    server. However, due to the amount of workstations I have to do this
    isn't
    really practical. Does anyone know if it's possible to specify the
    full DNS
    domain name in HOST or LMHOST files?

    I have already set the target domain's NETBIOS domain name in the
    lmhost
    file of the client machine, but this doesn't appear to be sufficient
    for its
    migration. It seems to require the full DNS domain name.

    Thanks,

    Curtis.

    ====================================
    When replying by email please remove the X
    ====================================
     
    Bob Qin [MSFT], Aug 26, 2004
    #2
    1. Advertisements

  3. Curtis Fray

    Curtis Fray Guest

    Hi Bob,

    Sorry for the delay in replying. I've been away and just got back. Hopefully
    you're still monitoring this thread.

    Thank you for your ideas. Unfortunatey the NT domain I'm upgrading does not
    have a WINS or DNS server. Historically its always depended on HOST and
    LMHOST files (hence yet another reason for the migration and fresh start!).
    That why I was hoping it may be possible to add the necessary entry in the
    host files.

    I could set up the necessary servers but would then have to set up all
    client machines with the new WINS and DNS server entries. Is it possible to
    change these with a logon script maybe to avoid visiting all machines? If so
    I could just point them to the new DNS server in the new domain which does
    overcome the problem.

    Any other thoughts you have on this would be greatly appreciated.

    Thanks,

    Curtis.
     
    Curtis Fray, Sep 6, 2004
    #3
  4. Hi Curtis,

    In fact, we can create LMHOSTS files to point the clients to the target
    domain and PDC of the target domain. Please refer to the following article
    to create a properly formatted Lmhosts file.

    How to Write an LMHOSTS File for Domain Validation and Other Name
    http://support.microsoft.com/?id=180094

    But it is not a recommended solution in Windows Active Directory. If you
    use dynamic IP address in your network, you can assign the new DNS and WINS
    server to clients using DHCP options.

    228803 DHCP Dynamic Updates with DNS
    http://support.microsoft.com/?id=228803

    323360 How to install and configure a DHCP Server in an Active Directory
    domain
    http://support.microsoft.com/?id=323360

    Hope this helps!

    Regards,
    Bob Qin
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security

    ====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    From: "Curtis Fray" <>
    Subject: Re: Adding target domain on source domain's workstation for
    migration
    Date: Mon, 6 Sep 2004 16:08:52 +0100
    Newsgroups: microsoft.public.windows.server.migration

    Hi Bob,

    Sorry for the delay in replying. I've been away and just got back.
    Hopefully
    you're still monitoring this thread.

    Thank you for your ideas. Unfortunatey the NT domain I'm upgrading
    does not
    have a WINS or DNS server. Historically its always depended on HOST
    and
    LMHOST files (hence yet another reason for the migration and fresh
    start!).
    That why I was hoping it may be possible to add the necessary entry
    in the
    host files.

    I could set up the necessary servers but would then have to set up
    all
    client machines with the new WINS and DNS server entries. Is it
    possible to
    change these with a logon script maybe to avoid visiting all
    machines? If so
    I could just point them to the new DNS server in the new domain which
    does
    overcome the problem.

    Any other thoughts you have on this would be greatly appreciated.

    Thanks,

    Curtis.
     
    Bob Qin [MSFT], Sep 7, 2004
    #4
  5. Curtis Fray

    Curtis Fray Guest

    Hi Bob,

    I've tried the LMHOSTS solution but without luck unfortunately. Again, my
    options are limited as the current network has no DHCP server. All clients
    have static IP's.

    I've entered the below in the LMHOSTS file:

    192.168.0.6 2003BUCKS #PRE #DOM:BUCKS
    192.168.0.6 "BUCKS \0x1b" #PRE
    # "123456789012345*7890"

    (NB the 16th character has been counted as specified on the website you gave
    me.)

    I think this is failing because the computer migration seems to require the
    full DNS domain name (bucks.com), not the NETBIOS one (BUCKS). Is there
    anyway to specify the DNS domain name within the host files? I tried
    updating the above to the below but without success:

    192.168.0.6 2003BUCKS #PRE #DOM:bucks.com
    192.168.0.6 "BUCKS \0x1b" #PRE
    # "123456789012345*7890"

    Thanks again for your help with this!

    Curtis.
     
    Curtis Fray, Sep 7, 2004
    #5
  6. Hi Curtis,

    We can use LMhosts file on the source domain DC to connect to the target
    domain DC.

    Please make sure that the "BUCKS \0x1b" item has 20 characters
    (without the quotations).

    In addition, you can try netsh command to sets the IP address of the Local
    Area Connection system configuration to use DHCP addressing. for example:

    netsh interface ip set address "Local Area Connection" dhcp

    You can refer to the following article for more information.

    257748 How to Use the NETSH Command to Change from Static IP Address to
    DHCP in
    http://support.microsoft.com/?id=257748

    Best regards,
    Bob Qin
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security

    ====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    From: "Curtis Fray" <>
    Subject: Re: Adding target domain on source domain's workstation for
    migration
    Date: Tue, 7 Sep 2004 09:54:01 +0100
    Newsgroups: microsoft.public.windows.server.migration

    Hi Bob,

    I've tried the LMHOSTS solution but without luck unfortunately.
    Again, my
    options are limited as the current network has no DHCP server. All
    clients
    have static IP's.

    I've entered the below in the LMHOSTS file:

    192.168.0.6 2003BUCKS #PRE #DOM:BUCKS
    192.168.0.6 "BUCKS \0x1b" #PRE
    # "123456789012345*7890"

    (NB the 16th character has been counted as specified on the website
    you gave
    me.)

    I think this is failing because the computer migration seems to
    require the
    full DNS domain name (bucks.com), not the NETBIOS one (BUCKS). Is
    there
    anyway to specify the DNS domain name within the host files? I tried
    updating the above to the below but without success:

    192.168.0.6 2003BUCKS #PRE #DOM:bucks.com
    192.168.0.6 "BUCKS \0x1b" #PRE
    # "123456789012345*7890"

    Thanks again for your help with this!

    Curtis.
     
    Bob Qin [MSFT], Sep 7, 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.