Windows->> FIX: "The security database on the server does not has a computer account for this workstation trust re Lationship "

A few days ago, when I was doing an alwayson experiment, a machine that had joined the ad was unable to log in as a domain administrator account when the Active Directory domain was built.

The error message is:
The security database on the server does not has a computer account for this workstation trust relationship

After Google found a useful blog post.

The cause died this way: The original Active Directory domain has a machine called Main, which is a DC. I later changed the name of the machine to DC. Then another machine used this domain to control the original machine name. As a result, the machine name used in the old domain cannot be landed. Because a machine registers into the Active Directory domain there will be some properties of the machine itself, although the machine name has changed, but these properties have not been modified. Those attributes may still contain the old machine name name. So, as in this example, the solution is to change the configuration of the Attribute Editor tab of the machine in the Active Directory domain to the new machine name as well as refer to the old machine name.

Reference:

FIX: "The security database on the server does not has a computer account for this workstation trust relationship"

Windows->> FIX: "The security database on the server does not has a computer account for this workstation trust re Lationship "