RE: Error migrating WinXP workstation with ADMT 3 or ADMT 2.

Hi,

For your current situation, I have following suggestions:

1. Choose one fixed computer for testing.
2. Check if it has the correct DNS record in DNS server.
3. Add the target domain Administrator account into local Administrators
group of the fixed computer.
4. Turn off firewall on the client.
5. Delete the computer in target domain (if exists)
6. Re-migrate the computer to see the results.

Thanks.



Best regards,

Vincent Xu
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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
Thread-Topic: Error migrating WinXP workstation with ADMT 3 or ADMT 2.
thread-index: Acbc95nBnSrM9Q3QTxegPPBd+54DTA==
X-WBNR-Posting-Host: 208.32.151.10
From: =?Utf-8?B?R2VvbWVsYXNh?= <Geomelasa@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Error migrating WinXP workstation with ADMT 3 or ADMT 2.
Date: Wed, 20 Sep 2006 13:59:02 -0700
Lines: 22
Message-ID: <539B3F1D-43F4-418F-8659-A5068B7DD2A2@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:25096
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

I am getting the following error in the Migration log, everytime I
migrate
any of my workstations :

NOTE: Computer account gets created in New domain, but the computer is
not
joined to the domain.

Err3: 7075 Failed to Change Domain Affiliation, Hr=80070005 Access
denied.

The Scurity translation and file translation Occure without errors, but
when
it tries to change the computer's domain I get the above error.

Here is what I have verified:
1. I run ADMT logged in as the Target's domain Administrator
2. The workstation's local Administrators group contains the Target's
Domain
Admins group.
3. User migration and Group migration worked without problems.

NOTE: Using the target's Domain admin account I am able to log in to a
workstation and manually join it to the new domain.


PLEASE help....


.

Relevant Pages

  • RE: Error migrating WinXP workstation with ADMT 3 or ADMT 2.
    ... Error migrating WinXP workstation with ADMT 3 or ADMT 2. ... I am getting the following error in the Migration log, ... Computer account gets created in New domain, ... I run ADMT logged in as the Target's domain Administrator ...
    (microsoft.public.windows.server.migration)
  • RE: Error migrating WinXP workstation with ADMT 3 or ADMT 2.
    ... Error migrating WinXP workstation with ADMT 3 or ADMT 2. ... I am getting the following error in the Migration log, ... Computer account gets created in New domain, ... I run ADMT logged in as the Target's domain Administrator ...
    (microsoft.public.windows.server.migration)
  • Re: NT4 to win2k3
    ... I finally got the migration tool to work. ... Server service is scheduled for deletion. ... domain administrator to each PC? ...
    (microsoft.public.windows.server.migration)