DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed
Occurs on a Windows 7-based or Windows Server R2-based "Trust relationship between this workstation and the primary domain. trust relationship between this workstation and the primary domain failed Windows Server and Windows Server R2 ship with. I have domain controller r2 and Windows server r2 with again the computer to the domain should fix the trust relationship issue.
All of the Exchange Server configuration data is stored within the Active Directory. 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. 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.
- How to Create Trust Relationships
- DON’T REJOIN TO FIX: The trust relationship between this workstation and the 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. When the machine is reset, it is missing all of the automatic password changes that it executed against the domain controller during the intervening months.
Create Two-Way Forest Trust in Windows Server 2008 R2
The password changes are required to maintain the security integrity of the domain. Support blogs and Microsoft will generally tell you to rejoin the domain to restore the trust relationship. Another option they will give is to delete the computer object and recreate it without a password and rejoin. 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.
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.
A nontransitive trust is bounded by the domains in the relationship. A forest trust is a transitive trust between two forests that allows users in any of the domains in one forest to be authenticated in any of the domains in the other forest Realm Trust: A realm trust is a transitive trust between an Active Directory domain and a non Windows Kerberos realm.Fix "Trust relationship ..." issue without rejoining to a domain
This trust provides cross-platform operability with security services based on other versions of the Kerberos 5 protocol.
A shortcut trust is transitive between domains in a Windows Server forest. This trust expedites the authentication process between domains in a forest, especially if the two domains are separated by two domain trees.
Create Two-Way Forest Trust in Windows Server R2
Transitivity determines whether a trust can be extended outside the two domains between which it was formed. You can use a transitive trust to automatically extend trust relationships to any other domains that is trusted by the original domain. You can use a nontransitive trust to deny trust relationships with other domains. For our example, NowFixIT and CloudBT are forest root domains in separate forests, therefore you can create an External trust or Forest trust between them only as seen below.
On the Directions of Trust page, you indicate whether you want to create an incoming or outgoing one-way trust, or a two-way trust. For our example, we want to create a two way trust both domains have access to each others resources.