ADMT2.0 issue - Can not migrate SID History

[Scott Abel]

Here is my issue,

I am using the ADMT tool to migrate users, computers, etc... I have
no problems doing this from our main corporate office (where our PDC
lies). However, we just brought on a new remote office in California
(it has it's own BDC in the NT domain and a DC in the AD domain). I
wish to run the ADMT tool on the local DC out there so I don't take up
bandwidth when migrating the computer accounts. I installed the ADMT
tool and created the password file in order to migrate users passwords
from the NT domain. I made all the necessary changes including
changing the dword value for the AllowPasswordExport to 1 on the
source NT DC. I also rebooted the BDC after installing the pwdmig.exe
application.

Problems now lies when I try to migrate a user account using the ADMT
tool on the DC in california I get the following error message when I
select the checkbox to migrate the Sid History.

"Could not verify auditing and TCPIPClientSupport on domains. Will
not be able to migrate Sid's. The specified domain does not exist or
could not be contacted".

I am at a loss here as I don't know what to troubleshoot. This
migration works fine in our corporate office. If anyone has any
suggestions or ideas it would be greatly appreciated.

Thanks!

Scott

(e-mail address removed)

 

[Chriss3]

Soctt the Registry have to been prepared at WindowsNT4.0 PDC.
The Windows2000 Domain have to bee in Native Mode.

To create the TcpipClientSupport registry entry by editing the registry

1.. While logged on to the primary domain controller (PDC) or the PDC
emulator in the source domain, click Start, then click Run
2.. In the Open field, type regedit, and then click OK.
3.. In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA

4.. On the Edit menu, click New and select DWORD Value.
5.. On the Edit menu, click Rename and type TcpipClientSupport.
6.. Double-click TcpipClientSupport.
7.. In Value data, type 1 (the numeral one). In Base, click Hexadecimal,
and then click OK.
8.. Close Registry Editor, and then restart the computer.
Verify If this entry is not present then it possible can be the problem.