Test-ComputerSecureChannel —- https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/test-computersecurechannel?view=powershell-5.1

Test-ComputerSecureChannel -Verbose

Test-ComputerSecureChannel komutunun true dönmesi gerekmektedir. Bu komut çıktısı False dönüyorsa active directory ve ilgili client arasındaki trust ilişkisi bozulmuştur.

Test-ComputerSecureChannel -Repair -Credential (Get-Credential)

Get-Adcomputer -identity ComputerName -Properties PasswordLastSet

Reset-ComputerMachinePassword

$LocalAdminCred = Get-Credential
Remove-Computer -WorkgroupName TEMP -UnjoinDomainCredential $LocalAdminCred

$DomainCred = Get-Credential
Add-Computer -Credential $DomainCred -DomainName powershell.no

Get-NetTCPConnection | 
Select LocalAddress, LocalPort, RemoteAddress, RemotePort, State, OwningProcess , @{n="ProcessName";e={(Get-Process -Id $_.OwningProcess).ProcessName}} , @{n="UserName";e={(Get-Process -Id $_.OwningProcess -IncludeUserName).UserName}}| 
Where {$_.State -eq"Established"} | Group-Object ProcessName -NoElement | Sort-Object -Property Count -Descending

netdom resetpwd /s:server /ud:domain\User /pd:* to reset a machine password and
nltest.exe /sc_verify:domain.local to verify the secure channel. Obviously, the syntax and
discoverability of the PowerShell alternatives is much better and should be the preferred options.