Computer Account Migration to AD2003 issue

Discussion in 'Server Migration' started by adfreek, Sep 7, 2004.

  1. adfreek

    adfreek Guest

    Scenario: Presently in the testing stages of a migration
    from 5 NT User Domains to a single Windows 2003 AD Child
    Domain. Using the BV-Admin product from Bindview to
    assist in the migration. We have about 60% population of
    Windows 98 clients (there is an XP migration running
    parralel to this but won't be done in time) in which all
    these computers will need to log into the new AD. The
    Novell Netware client is on these machines as well since
    all home directories and other shares are on Novell File
    Servers. The issue we're running into is that after we
    migrate both the NT and NDS user accounts to AD, we
    realized that we can't use the BV-Admin tool to create a
    project to migrate the Win98 machine objects because they
    DON'T exist in the NT Domains!

    I was able to go in to Network Neighborhood properties,
    select "Client for MS Networks" and MANUALLY change the
    domain from the source NT domain to the new 2003 AD. I
    then logged in successfully. Has anyone run into this and
    if so, have you come up with a solution where no MANUAL
    intervention is required? We're hoping come migration
    day, that we don't have to visit each Win98 machine and
    change the domain or even have to ask the user to do it.

    Any help or insight would be appreciated.

    Regards
     
    adfreek, Sep 7, 2004
    #1
    1. Advertisements

  2. Hello,

    Thanks for your posting here.

    As for the Windows 9x clients, if the users already logon to the Microsoft
    Network, then the NT Domain can be changed by a .reg file to update the
    registry. Specifically if you change these
    keys:

    [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSNP32\NetworkProvider
    ]
    "AuthenticatingAgent"="enter_the_domain_name_here"
    "LogonDisconnected"=hex:00,00,00,00
    "Name"="Microsoft Network"
    "ProviderPath"="msnp32.dll"
    "Description"="Microsoft Network"
    "NetID"=hex:00,00,01,00
    "CallOrder"=hex:00,00,00,40
    "DisableReLogin"=hex:00,00,00,00

    [HKEY_LOCAL_MACHINE\Security\Provider]
    "Platform_Type"=hex:00,00,00,00 "Container"="enter_the_domain_name_here"

    *Substitute the enter_the_domain_name_here with your domain.

    Have a nice day!

    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: "adfreek" <>
    Subject: Computer Account Migration to AD2003 issue
    Date: Tue, 7 Sep 2004 11:21:16 -0700
    Newsgroups: microsoft.public.windows.server.migration

    Scenario: Presently in the testing stages of a migration
    from 5 NT User Domains to a single Windows 2003 AD Child
    Domain. Using the BV-Admin product from Bindview to
    assist in the migration. We have about 60% population of
    Windows 98 clients (there is an XP migration running
    parralel to this but won't be done in time) in which all
    these computers will need to log into the new AD. The
    Novell Netware client is on these machines as well since
    all home directories and other shares are on Novell File
    Servers. The issue we're running into is that after we
    migrate both the NT and NDS user accounts to AD, we
    realized that we can't use the BV-Admin tool to create a
    project to migrate the Win98 machine objects because they
    DON'T exist in the NT Domains!

    I was able to go in to Network Neighborhood properties,
    select "Client for MS Networks" and MANUALLY change the
    domain from the source NT domain to the new 2003 AD. I
    then logged in successfully. Has anyone run into this and
    if so, have you come up with a solution where no MANUAL
    intervention is required? We're hoping come migration
    day, that we don't have to visit each Win98 machine and
    change the domain or even have to ask the user to do it.

    Any help or insight would be appreciated.

    Regards
     
    Bob Qin [MSFT], Sep 8, 2004
    #2
    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.