Ad trust relationship between workstation primary domain failed

DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed

ad trust relationship between workstation primary domain failed

Error: The trust relationship between this workstation and the primary domain failed. Article | Authentication, Configuration, Third Party | 2 found. Solution: I have seen this a few times beforeTrust relationship fails at some point in timeUser logs in with Cached Credentials - no problemUser. Causes of Trust relationship failed or "The trust relationship between this workstation and the primary domain failed" error and solutions on how.

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.

The trust relationship between this workstation and the primary domain failed

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. Other option is to completely disable sending a request for computer password updates, by changing the value of the DisablePasswordChange parameter to 1.

DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed

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.

Error: 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!

Fix Trust relationship failed issue without domain rejoining

The method is fast and efficient. To use it, login to the target system with Local administrator!!! You can check for a secure connection to the domain using Netdom by using the following command: This is the fastest and most convenient way to reset the password of a computer that does not require a reboot. Unlike the Netdom utility, PowerShell 3. You can install it manually see here on this platforms: If you want to restore a trust relationship as a local Administrator, run PowerShell console and execute this command: This approach works really well for workstations, but it can do more harm than good if you try it on a member server.

The reason for this has to do with the way that some applications use the Active Directory. Take Exchange Server, for example.

ad trust relationship between workstation primary domain failed

Exchange Server stores messages in a mailbox database residing on a mailbox server. However, this is the only significant data that is stored locally on Exchange Server. All of the Exchange Server configuration data is stored within the Active Directory.

ad trust relationship between workstation primary domain failed

In fact, it is possible to completely rebuild a failed Exchange Server from scratch aside from the mailbox database simply by making use of the configuration data that is stored in the Active Directory.

The reason why I mention this particular example is that the Exchange Server configuration data is stored within the computer object for that server. So with that in mind, imagine that a trust relationship was accidentally broken and you decided to fix the problem by deleting the Exchange Server's computer account and rejoining the computer to the domain.

ad trust relationship between workstation primary domain failed

By doing so, you would lose all of the configuration information for that server. Worse yet, there would still be orphaned references to the computer account scattered elsewhere in the Active Directory you can see these references by using the ADSIEdit tool.

In other words, getting rid of a computer account can cause some pretty serious problems for your applications. A better approach is to simply reset the computer account. Right click on the computer that you are having trouble with.

ad trust relationship between workstation primary domain failed

Select the Reset Account command from the shortcut menu, as shown in Figure 2. When you do, you will see a prompt asking you if you are sure that you want to reset the computer account.

Click Yes and the computer account will be reset. You can reset the computer account through the Active Directory Users and Computers console. In case you are wondering, computer accounts can also be reset through PowerShell version 2 or higher. The cmdlet used for doing so is Reset-ComputerMachinePassword.