UsePowerShellFix Trust relationships
In the course of training, a lot of students will ask a question is when to join the domain environment of the client off the domain?
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/58/2F/wKiom1SrXQvDRGChAACrXjjjPIE716.jpg "style=" float: none; "title=" 11.png "alt=" Wkiom1srxqvdrgchaacrxjjjpie716.jpg "/>
simply analyze Why:
1. It may be because another computer with the same name exists on the same network.
2. if a computer in a domain is not logged on with a domain account for a long time, then there is a corresponding Kerberos ticket policy in the policy.
3. There is also the possibility that the time of the computer and the domain generator will differ by more than five minutes, which can also result in the inability to log on to the domain.
How to solve it?
Many people will retire and rejoin the domain. This can really solve the problem, but if the number of computers affected is more than one, it is inherently inefficient. Operations that actually use PowerShell on the Windows 7 operating system to add domains include actions to repair trusts. In Windows 8 and Windows 8.1, the command parameters for the repair trust are enhanced.
look at the steps super simple
The first step is to confirm the presence of the client computer account in AD if it is not new.
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/58/2B/wKioL1SrXg7T9PveAAI_WHCtUNQ160.jpg "title=" 22.jpg "alt=" Wkiol1srxg7t9pveaai_whctunq160.jpg "/>
The second step is to log on to the client computer using the local administrator.
Enter Test-computersecurechannel-repair-server < domain controllers in PowerShell >
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/58/2F/wKiom1SrXTGxHW3gAAHbfjjM3jk030.jpg "title=" 33.png "alt=" Wkiom1srxtgxhw3gaahbfjjm3jk030.jpg "/>
OK, try it again. You can already log in normally.
This article is from the "KAKA" blog, make sure to keep this source http://286722.blog.51cto.com/276722/1599631
Repairing trust relationships with PowerShell (original)