Fix Trust relationship failed issue without domain rejoining – TheITBros
Occurs on a Windows 7-based or Windows Server R2-based trust relationship between this workstation and the primary domain failed. The trust relationship between this workstation and the primary domain failed. this error is to log onto the workstation using the local, non-Domain on Windows 7 (all versions) and Windows Server and R2. Probably the workstation account password has come out of sync or has Another reason for this error may be the system time difference on both machines .
Trust at this level is provided by the fact that operation is performed by Domain administrator or another user with the same rights. Each time when domain computer login to the domain, it establish a secure channel with a domain controller and send credentials.
In that case, trust is established between the workstation and domain and further interaction occurs according to administrator-defined security policies. The computer account password is valid for 30 days by default and then automatically changes. It is important to understand that the change of password initiated by computer is defined by Domain policies. This is similar to the changing user password process. You can configure maximum account password age for domain computers using GPO Domain member: Maximum machine account password age, which is located in the following GPO editor branch: You can specify number of days between 0 and by default it is 30 days.
For a single machine, you can configure the machine account password policy through the registry. To do this, run regedit. Edit the value of the MaximumPasswordAge parameter, in which you can specify the maximum period of validity of the computer password in the domain in days.
- DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed
Other option is to completely disable sending a request for computer password updates, by changing the value of the DisablePasswordChange parameter to 1. The Active Directory domain stores the current computer password, as well as the previous one just in case. If the password was changed twice, the computer that is using old password will not be able to authenticate in the domain and establish a secure connection.
If the password has expired, computer changes it automatically when login on the domain. Therefore, even if you did not Power on your computer for a few months, trust relationship between computer and domain still be remaining and the password will be changed at first registration in the domain.
DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed
Trust relationship failed if computer tries to authenticate on domain with an invalid password. Typically, this occurs after reinstalling the OS, then the system state was restore from an image backup or snapshot of the Virtual machine, or it was just turned off for a long time. In this case, the current value of the password on the local computer and the password in the domain will be different.
The most obvious classic way to restore trust relationship is: Reset local Admin password Move computer from Domain to workgroup Reboot Reset Computer account in the domain using ADUC console Rejoin computer to the domain Reboot again This method is the easiest, but not the fastest and most convenient way and requires multiple reboots. Also, we know cases when user profile is not reconnecting correctly after rejoining.
We will show how to restore a trust relationship and restore secure channel without domain rejoin and reboot!
Microsoft support article on the topic: Recently, when I ran into this problem, the virtual machine that reset was an enterprise certificate authority joined to my test domain. Well, guess what, Microsoft will not allow you to rename or unjoin a computer that is a certificate authority—the button in the computer property page is greyed out.
Fix: The trust relationship between workstation and primary domain failed
Powershell v3 shipped with a cmdlet for resetting computer passwords. For those with Powershell skills, this is a much better option. Powershell v3 ships with the latest version of Windows and can be downloaded from Microsoft: You can fix this by opening Powershell with administrative rights and running Update-Help. You can use the Get-Credential cmdlet for a secure way to generate a PSCredential, which can be stored in a variable and used in a script.
The Server parameter is the domain controller to use when setting the machine account password.
A better fix Just change your computer password using netdom. You need to be able to get onto the machine. I hope you remember the password.
Fix Trust relationship failed issue without domain rejoining
Another option is to unplug the machine from the network and log in with domain user. You will be able to do disconnected authentication, but in the case of a reset machine, remember that you may have to use an old password. You need to make sure you have netdom. Where you get netdom. Windows Server and Windows Server R2 ship with netdom.
Google can help you get them. For other platforms see this link: If the broken machine is a domain controller it is a little bit more complicated, but still possible to fix the problem. Turn off the Kerberos Key Distribution Center service.