The name or security identity (SID) of the specified domain does not match the trust information for the domain

Once again, Windows is mad and must be remembered.

This two days, to the remote server installed Microsoft Office Web Apps Service, originally held the document thought that just follow the steps do not install on the domain controller should not be a big problem. It never occurred to me. Or a big somersault.

First new-officewebappsfarm the mistake. "Login failed: Unknown user name or bad password"

new-officewebappsfarm: Login failed: Unknown user name or bad password. Location Line:11"http://xxxx" -allowhttp-editinge ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : NotSpecified: (:) [new-Officewebappsfarm], authenticationexception     + FullyQualifiedErrorId:System.Security.Authentication.AuthenticationException, Microsoft.Office.Web.Apps.Adminis   tration. Newfarmcommand

OK, this is simple, have encountered as long as the domain account login can be solved.

Then, try to log in with a domain account, prompting "your credentials do not work", guessing whether it is because the remote service is not turned on, and then to the domain account set remote. Well, the landlord is a rookie, at this time and did not think you can view the log.

You still cannot log on after the remote is turned on. At this time, the landlord's heart is collapsed ...

Then after a series of Baidu, Bing ... Dazzled.. Still no clue ... Well, I'm really a rookie.

Finally finally the landlord's brain in a flash, think of the log can read ... Log shows "domain SID inconsistent" ...

Hurry to continue Baidu, Bing. So see this article http://rainbird.blog.51cto.com/211214/114589 guess their remote machine should also be a replication system. After asking, sure enough.

This is the solution that finally found the problem.

http://jingyan.baidu.com/article/5225f26b0c5456e6fa0908dc.html?qq-pf-to=pcqq.c2c

Finally the perfect solution.

Another: It is said that server2012 has fixed the problem, the same SID directly cannot add domain. The bar was great.

The name or security identity (SID) of the specified domain does not match the trust information for the domain