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

Hi,

This is a quick note to let you know that I am researching your issue and
will get back to you as soon as possible. I appreciate your patience.


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: AcbdhdBOOFjAo/ibQi2RqWv1CpCPzg==
X-WBNR-Posting-Host: 208.32.151.10
From: =?Utf-8?B?R2VvbWVsYXNh?= <Geomelasa@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <539B3F1D-43F4-418F-8659-A5068B7DD2A2@xxxxxxxxxxxxx>
<bTJrcqS3GHA.4464@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Error migrating WinXP workstation with ADMT 3 or ADMT 2.
Date: Thu, 21 Sep 2006 06:57:02 -0700
Lines: 130
Message-ID: <69D18001-174D-419E-B9EB-1B4F64B1D7BB@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:25106
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

I followed your suggestion:

1. I chose one machine.
2. Verified that I can resolve the FQDN of the Target and Source domain
from
the Workstation
3. Local Administrator's group contains Target's Domain admins
4. Firewall is turned off.
5. I deleted the Computer account on the Target's domain
6. remigrated station

Same problem... here is a snippet from the log:

2006-09-21 09:47:55 1254 users, 625 groups
2006-09-21 09:47:55 1879 accounts selected. 1879 resolved, 0 unresolved.
2006-09-21 09:47:55 Examined Changed Unchanged
2006-09-21 09:47:55 Files 0 0 0
2006-09-21 09:47:56 Dirs 0 0 0
2006-09-21 09:47:56 Shares 0 0 0
2006-09-21 09:47:56 Members 20 1 19
2006-09-21 09:47:56 User Rights 87 2 85
2006-09-21 09:47:56 Exchange Objects 0 0
0
2006-09-21 09:47:56 Containers 0 0 0
2006-09-21 09:47:56 DACLs 164564 0 164564
2006-09-21 09:47:56 SACLs 0 0 0
2006-09-21 09:47:56 Examined Changed No Target
Not
Selected Unknown
2006-09-21 09:47:56 Owners 164564 0 164564

0 0
2006-09-21 09:47:56 Groups 164564 0 164564

0 0
2006-09-21 09:47:56 DACEs 1442376 0 1436601

1436463 0
2006-09-21 09:47:56 SACEs 0 0 0

0 0
2006-09-21 09:47:56 ERR3:7075 Failed to change domain affiliation,
hr=80070005 Access is denied.
2006-09-21 09:47:56 Wrote result file
C:\WINDOWS\OnePointDomainAgent\000180_CSIP012.result
2006-09-21 09:47:56 Operation completed.

"Vincent Xu [MSFT]" wrote:

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: NT 4 to 2003 Error
    ... I understand when you use the Active Directory Migration Tool, ... Because no changes are actually written when you run the ADMT in test mode, ... >ERR3:7075 Failed to change domain affiliation, ... >database on the server does not have a computer account for this ...
    (microsoft.public.windows.server.migration)
  • RE: Computer Account Migration
    ... ADMT 2.0 should be the best tool to migrate the clients from the existing ... Windows NT 4.0 SP4 or higher ... Active Directory Migration Tool Overview ... |Subject: Computer Account Migration ...
    (microsoft.public.windows.server.migration)
  • RE: [Rant] ADMT
    ... I'm sorry to hear that ADMT tool gives you so much trouble. ... is a useful tool when you try to perform a migration even the usage is ... | - Created an empty OU for migrated objects in target domain. ... Now the source server was found ...
    (microsoft.public.windows.server.migration)
  • RE: ADMT local user profile migration
    ... I noticed that you are using ADMT V3 now.How about the ADMT ... migration you found these account still disabled. ... I think you need to migrate member server ...
    (microsoft.public.windows.server.migration)
Loading