ADMT Computer Migration Error

[kludge]

First post here.

We are using ADMT v3 to migrate users and computers from one child domain to another. The machines are all W2k SP4. Profiles moved without a hitch, but getting an unknown error on the computer domain migration.

Since I'm unable to find another poster with the same problem I'm offering it up for some help!

--Snip from log--
2009-05-13 09:35:09 ERR3:7075 Failed to change domain affiliation, hr=8007013d The system cannot find message text for message number 0x%1 in the message file for %2.
2009-05-13 09:35:09 Wrote result file C:\WINNT\OnePointDomainAgent\000024_FYC4J41N41.result
2009-05-13 09:35:09 Operation completed.
--Snip from log--

the 8007013b isn't coming up an any of my KB searches either. What we've done.

1. Made sure the "NTLM security support provider" service is started
2. Disabled Symantec
3. wept

Any other suggestions?

Thank You!

"kludge" <kludge.3s55jc@DoNotSpam.com> wrote in message news:kludge.3s55jc@DoNotSpam.com...
>
> First post here.
>
> We are using ADMT v3 to migrate users and computers from one child
> domain to another. The machines are all W2k SP4. Profiles moved without
> a hitch, but getting an unknown error on the computer domain migration.
>
> Since I'm unable to find another poster with the same problem I'm
> offering it up for some help!
>
> --Snip from log--
> 2009-05-13 09:35:09 ERR3:7075 Failed to change domain affiliation,
> *hr=8007013d* The system cannot find message text for message number
> 0x%1 in the message file for %2.
> 2009-05-13 09:35:09 Wrote result file
> C:\WINNT\OnePointDomainAgent\000024_FYC4J41N41.result
> 2009-05-13 09:35:09 Operation completed.
> --Snip from log--
>
> the 8007013b isn't coming up an any of my KB searches either. What
> we've done.
>
> 1. Made sure the "NTLM security support provider" service is started
> 2. Disabled Symantec
> 3. wept
>
> Any other suggestions?
>
> Thank You!
>


Is NetBIOS enabled? Is there a two way trust?


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay

[kludge]

Ace-

Thanks. We did have an issue with our WINS setup, but correcting it didn't solve the issue. Luckily though it lead us down another path to the solution..

In case others have this issue, here was our fix.

While investigating the above issue, however, it was noticed that the DC was logging a NETLOGON 5722 error. That led to this KB article , which contains the solution, to update the Default Domain Controllers Policy to Allow cryptography algorithms compatible with Windows NT 4.0.

This fixed the problem.

"kludge" <kludge.3s6p3c@DoNotSpam.com> wrote in message news:kludge.3s6p3c@DoNotSpam.com...
>
> Ace-
>
> Thanks. We did have an issue with our WINS setup, but correcting it
> didn't solve the issue. Luckily though it lead us down another path to
> the solution..
>
> In case others have this issue, here was our fix.
>
> While investigating the above issue, however, it was noticed that the
> DC was logging a NETLOGON 5722 error. That led to this 'KB article'
> (http://support.microsoft.com/kb/942564) , which contains the solution,
> to update the Default Domain Controllers Policy to Allow cryptography
> algorithms compatible with Windows NT 4.0.
>
> This fixed the problem.
>
>
> --
> kludge



You are welcome Kludge. Good to hear you've solved the problem!

I also appreciate that you've posted your solution. Hopefully it will benefit others!

Ace