ERR3:7075 Failed to change domain affiliation

From: Keith Borgmann (anonymous_at_discussions.microsoft.com)
Date: 07/08/04

  • Next message: Kjetil Thorstensen: "Admin gets "Access denied" when trying to delete." 
    Date: Thu, 8 Jul 2004 11:28:27 -0700

    I installed ADMT 2 following the instructions in KB325851
    and migration of users and groups from NT4 SP6a to W2K3
    seems to work fine. However, migrating computers is
    something else entirely.

    We are running the two domains side by side and I intend
    to move the computers and accounts one department at a
    time. Right now, I'm just testing with one test computer
    and one test user account. All my PCs are running W2K
    SP3 or higher or XP Pro SP1 and most have an NTFS.

    Every time I test the migration of a computer from the NT
    domain to the 2K3 domain, I get the following error:

    ERR3:7075 Failed to change domain affiliation,
    hr=8007054b The specified domain either does not exist
    or could not be contacted.

    If I actually perform the migration, I get the same error.

    I keep reading the same responses to similar problems
    telling the person to log onto the target DC as the
    source domain admin. I assume that means I logon as
    SOURCEDOMAIN\administrator, use the appropriate password,
    and keep the actual domain as the TARGETDOMAIN. Or am I
    supposed to log onto the target DC but change the domain
    to SOURCEDOMAIN? Regardless, it doesn't seem to work
    properly either way.

    The other response I keep seeing is to put the target
    domain administrator into the source domain's Domain
    Admins group. The only problem with that is I can find
    no way to do this. When I go into the NT4 user manager,
    Domain Admins is a global group whose members must come
    from the members of the NT domain.

    I can add the target domain administrator to the
    Administrators group (a local group) in the NT domain,
    but that does me no good since it is the Domain Admins
    group that is part of the local Administrators group on
    each PC. In desperation, I added the
    TARGETDOMAIN\Administrator to the local administrator's
    group on the test machine I am attempting to migrate.
    Again, I get the same error.

    Regardless of what I do, the machine does not fully
    migrate to the target domain. If I look in Control Panel-
    >System->Network Identification->Properties, the machine
    still appears to be in the source domain.

    I would appreciate any suggestions.

  • Next message: Kjetil Thorstensen: "Admin gets "Access denied" when trying to delete."

    Relevant Pages

    • RE: Error migrating WinXP workstation with ADMT 3 or ADMT 2.
      ... Add the target domain Administrator account into local Administrators ... Error migrating WinXP workstation with ADMT 3 or ADMT 2. ... I am getting the following error in the Migration log, ...
      (microsoft.public.windows.server.migration)
    • Re: Its official: NO one is protecting your privacy
      ... How about by leaving a new board on privacy and civil liberties ... Computers in Communist China and Russia, and some among them are using ... Government and US Corporations Computers, much of mine was sent to ... could not plan and target them, while they are using the accurate Maps ...
      (alt.politics)
    • RE: ADMT v3 Error
      ... I suspect it may be related to trust relationship. ... necessary to create a trust relationship between the target domain and the ... used to do the migration has full access control for the two domains. ... | Do I need to upgrade the source domain and forest to Windows 20003 ...
      (microsoft.public.windows.server.migration)
    • Re: Migration to New Subdomain
      ... Forest is a migration ... connections back to the root domain still exist. ... My goal is to move just a couple of users and computers from ... I have one domain controller for the new sub domain ...
      (microsoft.public.windows.server.active_directory)
    • Re: Migration of user accounts from NT4 to 2003 AD
      ... also tried to remove the Registry key on the source NT DC and began ... it then asked to reboot the DC. ... I did a migration of that domain and it went through fine. ... The RestrictAnonymous value on the target domain controller should be ...
      (microsoft.public.windows.server.migration)
    Loading