Windows Forum

Ask something
Discussion Locked

NT 4.0 to 2000 Server Migration Problem

0 helpful
5 replies

by bradq

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have two NT 4.0 Servers:

PDC - YDI 192.168.0.6
BDC - YDI_2 192.168.0.7
DOMAIN - named DOMAIN

Got a new 2000 Server
192.168.0.5 YDIMAIN
DOMAIN - named YOUTHDYNAMICS

25 Windows 98 Clients
7 Windows 2000 Pro Clients

I added the local admins to DOMAINAdmins between domains. I edited the registry on the PDC with the LSA key, added the Admin on each 2000 workstation Users and Passwords, and created the trust between domains. I can browse fine between domains. I did a test user migration and it works fine. I need to do a computer migration too because we have the Win 2000 machines. When trying a test computer account migration, it completes with errors and I see this in the event viewer on the 2000 Server:

EVENT ID: 5723 "The session setup from the computer THERESA failed because there is no trust account in the security database for this computer. The name of the account in the security database is THERESA$."

Can anyone help?

5 replies

by bradq

Do I need to join each 2000 Professional machine onto the new domain first and then run the computer account migration wizard?

by joseph moore

First, what change to the LSA key on the PDC did you make?
Technet article Q150518 sounds similar to your error. It talks about the secure communications channel that NT4 PDCs and BDCs use to exchange account data. It states that it is possible for the secure channel password to get out of sync; this password is used with the computer account that is made for the BDC. The password is changed every 7 days. If there is a problem, then you can get this error.

So, what I am wondering is if Win2KPro clients also use secure channel to communicate to the domain controllers to update and receive account information. I am not sure.
So, what I am thinking is for you to try the suggested fix in the article on the 2000Pro clients. See what happens.

Here is the URL on this article.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q150518
(please remove any spaces)

Hope this helps.

by bradq

This is the one I added:

On the PDC in the source domain, add the TcpipClientSupport:REG_DWORD:0x1 value under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA.

This discussion is closed to new replies.