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

Hi Vincent,

Here is my current situation. Thanks for your suggestion.

Regards,
Andrew

"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:h3itSGruGHA.5872@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

Some thoughts:
1. Does Windows 2000's migration properly?
I haven't tested 2000 client
2. Try to join the current user account (running ADMT) into the
workstations' local Administrators group.
I am using source domain admins' group administrator account to logon ADMT
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
client machine
3. Try to ping the computer name to see if the name resolution is correct
from target domain.
it OK.
4. If you are using DNS, please check if DNS settings are correct.
As I put every machine in an isolated LAN, so DNS should not be a issue. Any
way, I add this host record into 2003 AD DNS but it still not working >.<




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
    ... Does Windows 2000's migration properly? ... WIN2000 Pro, and XP Pro Client ... Active Directory Migration Tool Agent Dialog. ... been granted administrators right on target domain; ...
    (microsoft.public.windows.server.migration)
  • RE: ADMT Help
    ... We can use ADMT to migrate the client computers. ... The following are some requirements or tips for ADMT - Computer Migration. ... The account that runs ADMT must have local administrator permissions on ...
    (microsoft.public.windows.server.migration)
  • Re: Migrating NT domain to AD
    ... The W98 machines do not have to have AD client to be in the new domain, ... ONLY AD domain controllers are listed as preferred dns servers for your computers via ... The downside is that I believe some of the better migration tools ... require that the migration be to a native mode domain. ...
    (microsoft.public.win2000.security)
  • Re: How Can I Allow Access From The Internet to Only Selected User
    ... users, groups, client ip address ranges, client computer naming conventions ... All users can access Terminal Server from inside the network ... "select remote users" and enter in th administrators group. ...
    (microsoft.public.windows.terminal_services)
  • Re: Help me change XPpro from 2000 domain to new 2003 domain
    ... import the files and settings once logged onto the new domain. ... Migration Tool), which allows migration of user account and profiles to a ... I unplug my XPpro client from 2000 server domain and plug it in to new ...
    (microsoft.public.windowsxp.network_web)