RE: Error on migrating XP client on NT 4.0 Domain into WINDOWS 2003 AD

Hi,

Some thoughts:
1. Does Windows 2000's migration properly?
2. Try to join the current user account (running ADMT) into the
workstations' local Administrators group.
3. Try to ping the computer name to see if the name resolution is correct
from target domain.
4. If you are using DNS, please check if DNS settings are correct.


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.
======================================================



--------------------
From: "Andrew Chan" <andrew.chan@xxxxxxxxxxxxxx>
Subject: Error on migrating XP client on NT 4.0 Domain into WINDOWS 2003
AD
Date: Tue, 8 Aug 2006 13:02:54 +0800
Lines: 28
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Original
Message-ID: <OMvApfquGHA.4140@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 218.189.186.94
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24737
X-Tomcat-NG: microsoft.public.windows.server.migration

Dear all,

My company currently is using NT 4.0 single domain structure with NT wk,
WIN2000 Pro, and XP Pro Client
PCs. At this moment, we are planning to migrate to Windows 2003 AD and so
doing test on ADMT 3.0 to migrate current NT domain user accounts, group
and
computer into new AD domain structure. During the testing phase, we find
that we could not migrate XP Client computer security setting, but it
work
on NT client. An error message comes up during the Pre-Check phase on the
Active Directory Migration Tool Agent Dialog. The message is "ERR2:7666
Unable to access server service on the machine 'xxx'. Make sure netlogon
and
workstation services are running and you can authenticate yourself to the
machine. hr=0x800706ba. The RPC server is unavailable.

The SP2 has been installed on XP Client. Two-ways trust has been built
between source and target domain. Source Domains' domain admins group has
been granted administrators right on target domain; and Target domains'
domain admins groups has also been granted administrators right on source
domain.

NT WK are successfully migrated into W2K3 AD but XP client cant, any idea
to
solve this problem.

Thanks in advance

Andrew




.

Relevant Pages

  • Re: Error on migrating XP client on NT 4.0 Domain into WINDOWS 2003 AD
    ... I haven't tested 2000 client ... installed machine on target domain, so it should be alright as source ... domain's domain admins group should be added into administrators group on XP ... Active Directory Migration Tool Agent Dialog. ...
    (microsoft.public.windows.server.migration)
  • Re: Migrating to 2003 SBS
    ... Windows 2003 SBS. ... new client Pc's. ... is when I perform the client computer migration do I need to ...
    (microsoft.public.windows.server.migration)
  • Migrating to 2003 SBS
    ... Windows 2003 SBS. ... new client Pc's. ... is when I perform the client computer migration do I need to ...
    (microsoft.public.windows.server.migration)
  • Client PCs
    ... After migration of users/groups/computers accounts from ... the old NT domain to the new Windows 2003 domain, ... to join each client PC into the new domain one by one. ...
    (microsoft.public.windows.server.migration)
  • RE: Print Server Migration From NT4.0 to Windows 2003
    ... But since the print server is in a AD, ... that client side will find the printer. ... To publish printers in Windows 2003 ... Print Server Migration From NT4.0 to Windows 2003 ...
    (microsoft.public.windows.server.migration)