I have a domain and I am upgrading PCs to 64-bit Windows 7. Many of my users are reporting the error message "Trust relationship between this workstation and primary domain failed" and can not log in. I can remove the computer from active directory, change to a workgroup, then add back to the directory but that is not a good solution. I have thousands of users and this fix can't be done remotely, nor do I know that it it is fixed once it will not reoccur. Can someone please tell me what needs to be done to fix this problem? Thank you, in advance, for any assistance. Mark

>"Trust relationship between this workstation and primary domain failed...I have thousands of users... " Hi, welcome. Please, go to Microsoft Support at: http://support.microsoft.com/kb/162797 and if this do not solve your issue directly, it has alternative useful links to handle it better. Rgds. itconcerned

Thank you for your response but it does not help. It is not applicable to Windows 7. Windows 7 has a hotfix I installed but that didn't work either because our domain servers are 2003 and the hotfix is for 2008. Also our thousands of users to not have the authority to change to a workgroup, delete their computer from AD and rebind to the domain.

Hi, welcome back. Please, try it at Microsoft Support KB - http://support.microsoft.com/search/default.aspx?query=The%20trust%20relationship%20between&catalog=LCID%3D1033 - Advanced Search (The trust relationship between), there are plenty of related links on this issue. Good Luck. Rgds. itconcerned

Hi, I really appreciate your assistance. Those links refer again to Windows Server 2008 as requisite. It is not a fix for Server 2003. I'll keep hunting.

You are welcome. My best wishes on your searches. B. Rgds.itconcerned

It may be too late now, but I had exactly the same problem. I installed this patch, and it worked fine after. http://support.microsoft.com/kb/976494

Windows 7 Professional ... Small Business Server 2003 I did a system restore on the affected computer (windows 7) and that took care of the problem. Did not need to rejoin or rename anything on the PC or the server