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

Hi,

Glad to hear you found a workaround. :)

Have a good day!


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>
References: <OMvApfquGHA.4140@xxxxxxxxxxxxxxxxxxxx>
<h3itSGruGHA.5872@xxxxxxxxxxxxxxxxxxxxx>
<OLMIQUruGHA.1224@xxxxxxxxxxxxxxxxxxxx>
<Ip#onO3uGHA.5584@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Error on migrating XP client on NT 4.0 Domain into WINDOWS
2003 AD
Date: Wed, 9 Aug 2006 16:10:23 +0800
Lines: 187
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: <e$jSGt4uGHA.2036@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 218.189.186.94
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24746
X-Tomcat-NG: microsoft.public.windows.server.migration

Hi Vincent,

Points 1,2,3,4 have been confrimed and still not work. Anyhow, thanks for
your suggestion. I have setup two more machine on Windows 2003 server and
XP
pro, the Migration work without any problems. Then, I develop a backup
plan
(simply join domain manually and modify user profile path by registry) if
any client machine cannot use ADMT to migrate to new domain.

Best regards,
Andrew

"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:Ip%23onO3uGHA.5584@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

OK, we go on checking following things:

1. If RPC service is started.
2. If firewall is disabled.
3. Turned off sid filtering in the source domain
4. Validate the trust between the two domains again.



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>
References: <OMvApfquGHA.4140@xxxxxxxxxxxxxxxxxxxx>
<h3itSGruGHA.5872@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Error on migrating XP client on NT 4.0 Domain into WINDOWS
2003 AD
Date: Tue, 8 Aug 2006 14:37:01 +0800
Lines: 102
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: <OLMIQUruGHA.1224@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:24739
X-Tomcat-NG: microsoft.public.windows.server.migration

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: Different network connection with different proxy settings for
    ... Best regards, ... Microsoft Online Partner Support ... Get Secure! ... When responding to posts, please "Reply to Group" via your newsreader so ...
    (microsoft.public.windowsxp.work_remotely)
  • RE: Cant see shares when logged in through VPN
    ... Change the IP address of the client to a 10.0.0.2 or some other different ... IP address range just for testing, so the address range does not conflict ... Get Secure? ... When responding to posts, ...
    (microsoft.public.windows.server.sbs)
  • RE: How to uninstall SMS Client
    ... Best Regards, ... Get Secure! ... When responding to posts, ...
    (microsoft.public.sms.admin)
  • Re: Smart Navigation property causing infinite Page Reload (v 1.1)
    ... Regards, ... >I suspect the client side code generate by the SmartNavigation script. ... > Execute Permission to scripts and Executables for your defaultl Home. ... > Trevor Benedict R ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Problem with Shadow Copy
    ... Best regards, ... When responding to posts, please "Reply to Group" via your newsreader so ... KB818742 Overview of the Microsoft Configuration Capture Utility ... The CAB file will be generated for your convenience in the ...
    (microsoft.public.windows.server.general)