"The security db on the srv does not have a comp acct for this wks trust...
have seen and solved this error several times, but this particular case is a bit unique.
Brief Background:
We used backup software to "image" a machine on the domain and chose the option to restore to dissimilar hardware. This procedure worked pretty well. We had to enter a different Win7Pro license key and re-activate other commercial products, but that was all.
A few days later, the user on the machine from which the backup image was taken is now getting the error ("The security database on the server does not have a computer account for this workstation trust relationship"). This only happens, however, if she logs into her PC as a specific domain user. She can login successfully to other PCs on the domain as this user, and others can login successfully to her machine.
Before going through the usual rigmarole to fix this error, I wanted to check with the community to see if anyone else had run into this type of problem.
My first plan would be to detach and re-join this machine to the domain.
Brief Background:
We used backup software to "image" a machine on the domain and chose the option to restore to dissimilar hardware. This procedure worked pretty well. We had to enter a different Win7Pro license key and re-activate other commercial products, but that was all.
A few days later, the user on the machine from which the backup image was taken is now getting the error ("The security database on the server does not have a computer account for this workstation trust relationship"). This only happens, however, if she logs into her PC as a specific domain user. She can login successfully to other PCs on the domain as this user, and others can login successfully to her machine.
Before going through the usual rigmarole to fix this error, I wanted to check with the community to see if anyone else had run into this type of problem.
My first plan would be to detach and re-join this machine to the domain.
David Johnson, CD
You have two computers with the same SID.. you need to sysprep one of them
ASKER
OK. I did consider this, but we have imaged/cloned machines before without Sysprep or NewSID without running into this problem. Also, the domain controller at this site is only a Win 2003 server - certainly not the latest & greatest.
Are you certain this behavior is caused by the duplicate SID?
Are you certain this behavior is caused by the duplicate SID?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just you were lucky and had multiple machines with the same SID without any issues does not mean that you should carry on with this.
Sysprep is free. Let us know if you need any help with this on Windows 7 regarding usage.
Sysprep is free. Let us know if you need any help with this on Windows 7 regarding usage.
ASKER
I have run Sysprep on the other machine and confirmed that they have different SIDs with PsGetSID. The individual is still having the issue. She has to unplug her PC from the LAN in order to login with her user name on her machine.
Is there another step left to perform?
Is there another step left to perform?
remove that computer from the domain locally
in AD remove the computer account
rejoin the computer to the domain
in AD remove the computer account
rejoin the computer to the domain
ASKER
OK. We are almost home free on this. After removing and re-joining the domain, the machine is now able to logon with the designated user account again.
Just so I could test the operation of some of her apps/profile, she temporarily changed her password (use CTRL-ALT-DEL). When she came in the next day, she tried to change her pwd back, and it would not accept any - claiming that none met the requirements. But they definitely did - 8+ characters, etc., including the one she had used previously. She is stuck using the temp password.
I could potentially reset it manually on the DC, but really do not want to know her password.
Is this a related issue?
Just so I could test the operation of some of her apps/profile, she temporarily changed her password (use CTRL-ALT-DEL). When she came in the next day, she tried to change her pwd back, and it would not accept any - claiming that none met the requirements. But they definitely did - 8+ characters, etc., including the one she had used previously. She is stuck using the temp password.
I could potentially reset it manually on the DC, but really do not want to know her password.
Is this a related issue?