This message was deleted.

Is PowerShell remoting enabled? https://adamtheautomator.com/trust-relationship-between-this-workstation-and-the-primary-domain-failed/#Reset-ComputerMachinePassword_PowerShell

I was able to PSremote onto the W10 devices as a test as well as using psexec, it seems to be yes.

Good. I use the PoSH cmdlet to fix this persistent (unfortunately) issue

My preferred way of doing it is Test-ComputerSecureChannel -Repair

Yeah that's the one I was trying to use but had some permission type errors will post tomorrow as it's late here - anyway will try this one "Invoke-Command -ComputerName thecomputer -ScriptBlock {Test-ComputerSecureChannel} True" - or possibly -

Test-ComputerSecureChannel -Repair -Verbose

Now do it remotely

Got it working had to use the Credentials twice one to PS-session onto the compute and then again to run the securechannel -repair cmdlet!

@Marco Zimmermann was on something similar... Maybe he can share his results 🙂

I'm banging my head on trusts issues as well. But my fun error is below.

Is that run as a admin or elevated?

can you run the Test-ComputerSecureChannel cmdlet ? or nltest /sc_verify:TypeMyDomainhere.com

Carl yes the commands are bing run with elevated rights but you did give me an idea of trying to login with an elevated account. Not sure if anyone has attempted that.. Test-ComputerSecureChannel returns true. Did not try nltest. I found that blog post and passed credentials and it looks like it takes but then the machine trust is lost.

Determine the status of the WinRM service on a remote computer PowerShell Y

PS C:\> Test-WSMan -ComputerName "server01"

Test-WsMan came back OK. This morning I tried a different strategy of using my account to login instead of elevation within a user session. At least doing that I was able to get Reset-ComputerMachinePassword to complete. Monitoring.

Can you still ping the machine ? I've had issues when I reset the machine in AD or via cmdlet, weirdly enough.

You shouldn't have to, but sometimes I've had to restart the computer/VM to get access back.

Ping continues outside of the normal issue of having to flush the dns cache on my workstation.

ok cool - just I had this issue here - https://github.com/adbertram/Random-PowerShell-Work/blob/f88241b7942e343eeef08ab583212e682df89eb3/ActiveDirectory/Rejoin-Computer.ps1 looks like a remote remove/rejoin script - will try later

On 3 PCs, I was able to elevate the Reset-ComputerMachinePassword. None of the users called me back to say it stopped working. Will contact them tomorrow. Hopeful.

nice

1 of the 3 users I was working with reported an issue after leaving the workstation on overnight. Monitoring continues.

yeah I had my first trust relationship ticket user couldn't login with local account or cached account, the machine was moved from and disable OU back into the normal OU, but after a reboot I can only ping it , I can't PS-remote or psexec onto it , infact can't do squat. might try again tomorrow though.

Wanted to circle back and mention the workstations beat me. I got to the point that the workstation would not see the trust issue for a few days and then it would appear again. User would restart the PC and then things would work for a few more days. I even went so far as to disable the workstation password function and it still did not solve it.

I always pass a PScredential object when I use Test-ComputerSecureChannel. Very occasionally doesn't work on the first -repair but never had to do more than 3 (one after another, same credential)

Hmmm, I had heard you always passed gas. Maybe that was a different conversation? 🙂