ADMT TcpipClientSupport registry key NT 4.0 to AD

[Louis Bouchard]

Hello,

I am having a problem with ADMT to migration the SID
history of my users to my newly created Windows 2003
active directory. I have followed Microsoft Knowledge
Base Article # 325851.

but I keep getting this error message "Either the source
domain's primary domain controller (PDC) has not been re-
started after setting the tcpipClientSupport registry key
to 1 or the PDC could not be contacted."

I have discarded the communication problem between the NT
4.0 server and the Windows 2003 server because when I do
not select "Migrate user SIDs to target domain" the
migration is successful.

to be sure I have added this key to my NT 4.0 PDC and BDC
and rebooted twice both servers:

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"TcpipClientSupport"=dword:00000001

What am I doing wrong? is there a more detailed
troubleshooting procedure somewhere out there?



..

 

[Eric Fleischman [MSFT]]

Anecdotally, I'll say that the error below is *very good* and is almost
always right. Even when you do tests like the one you did below, it is still
usually right. When migrating SIDs we do have a stricter requirement on
network connectivity and name resolution due to innerds of the process.

I would take a network trace of the failure and see where it fails. More
often than not I've found it is a subtle network issue or the user doesn't
have perms to check the TcpipClientSupport reg key on the remote system.

~Eric

 

[Louis Bouchard]

I will try to get you a network trace, but I have big
sceptical. The following entries have been added in the
LMHOST file on my Windows 2003 server.

192.168.5.120 MIG-PDC-01 #PRE #DOM:STAS_CHICOUTIMI
# IP Address "123456789012345*7890"
192.168.5.120 "STAS_CHICOUTIMI\0x1b" #PRE

and these lines in my LMHOST file on my Windows 4.0 PDC.

192.168.5.100 MIG-DC-01 #PRE #DOM:CORP
# IP Address "123456789012345*7890"
192.168.5.100 "CORP \0x1b" #PRE

-----Original Message-----
Anecdotally, I'll say that the error below is *very good* and is almost
always right. Even when you do tests like the one you did below, it is still
usually right. When migrating SIDs we do have a stricter requirement on
network connectivity and name resolution due to innerds of the process.

I would take a network trace of the failure and see where it fails. More
often than not I've found it is a subtle network issue or the user doesn't
have perms to check the TcpipClientSupport reg key on the remote system.

~Eric


--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Hello,

I am having a problem with ADMT to migration the SID
history of my users to my newly created Windows 2003
active directory. I have followed Microsoft Knowledge
Base Article # 325851.

but I keep getting this error message "Either the source
domain's primary domain controller (PDC) has not been re-
started after setting the tcpipClientSupport registry key
to 1 or the PDC could not be contacted."

I have discarded the communication problem between the NT
4.0 server and the Windows 2003 server because when I do
not select "Migrate user SIDs to target domain" the
migration is successful.

to be sure I have added this key to my NT 4.0 PDC and BDC
and rebooted twice both servers:

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"TcpipClientSupport"=dword:00000001

What am I doing wrong? is there a more detailed
troubleshooting procedure somewhere out there?



.

.

 

[Eric Fleischman [MSFT]]

Great, looking forward to seeing the trace. Just drop the 'online' from my
address and send it over.

--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

I will try to get you a network trace, but I have big
sceptical. The following entries have been added in the
LMHOST file on my Windows 2003 server.

192.168.5.120 MIG-PDC-01 #PRE #DOM:STAS_CHICOUTIMI
# IP Address "123456789012345*7890"
192.168.5.120 "STAS_CHICOUTIMI\0x1b" #PRE

and these lines in my LMHOST file on my Windows 4.0 PDC.

192.168.5.100 MIG-DC-01 #PRE #DOM:CORP
# IP Address "123456789012345*7890"
192.168.5.100 "CORP \0x1b" #PRE

-----Original Message-----
Anecdotally, I'll say that the error below is *very good* and is almost
always right. Even when you do tests like the one you did below, it is still
usually right. When migrating SIDs we do have a stricter requirement on
network connectivity and name resolution due to innerds of the process.

I would take a network trace of the failure and see where it fails. More
often than not I've found it is a subtle network issue or the user doesn't
have perms to check the TcpipClientSupport reg key on the remote system.

~Eric


--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Hello,

I am having a problem with ADMT to migration the SID
history of my users to my newly created Windows 2003
active directory. I have followed Microsoft Knowledge
Base Article # 325851.

but I keep getting this error message "Either the source
domain's primary domain controller (PDC) has not been re-
started after setting the tcpipClientSupport registry key
to 1 or the PDC could not be contacted."

I have discarded the communication problem between the NT
4.0 server and the Windows 2003 server because when I do
not select "Migrate user SIDs to target domain" the
migration is successful.

to be sure I have added this key to my NT 4.0 PDC and BDC
and rebooted twice both servers:

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"TcpipClientSupport"=dword:00000001

What am I doing wrong? is there a more detailed
troubleshooting procedure somewhere out there?



.

.