I logged his user account into our test pc and it did not generate an error. I attempted to log myself, Administrator, and train1 into his PC and got:
“The security database on the server does not have a computer account for this workstation trust relationship.” –

His PC says it’s on the domain. JSmith-PC.domain.com(Under system properties) – Network settings appear to be correct as far as DNS/DHCP/Gateway. The only difference I see in his network adapter is ipv6 is turned off. He is on “Private” Network profile as opposed to Domain network profile.

He has two profile folders on his local machine. JSmith and JohnS. Neither of them are JSmith.domain.

I once tried to remove him from the domain then rejoin, however, I got several errors and the workaround was to use system restore. That worked well enough to allow him to log into the PC and continue working. We need to impact the user as little as possible. Anything that would take more than 30 minutes on his machine is not really going to be possible unless his machine fully breaks and he can no longer function at all(at which point he would have no choice but to let us have it.)

Featured Post

Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why