📎 AI Summary:
The thread discusses an issue where a recent Windows update broke the ability of a Hyper-V server to communicate with a laptop via WinRM, as the standard configuration command no longer works. The original poster provides an alternative method to set trusted hosts using PowerShell commands, emphasizing the need to enable the WinRM service temporarily. A follow-up comment expresses gratitude and indicates that someone is testing the proposed solution. Overall, the discussion centers on troubleshooting remote management after a Windows patch, with helpful advice offered by the original poster.

ussnorway

Windows Forum Team
Staff member
Joined
May 22, 2012
Messages
4,597
Thread Author #1
Just a heads up, I run into an issue after the lastest patch stopped my hyper-v server from talking to my laptop... it appears that the basic
Code:
winrm set winrm/config/client '@{TrustedHosts="THE_NAME_OF_THE_SERVER"}'

no longer works and I had to go around it using
Code:
Get-Item WSMan:\localhost\Client\TrustedHosts
to see what host is trusted and
Code:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "name-of-host"
to set a new trusted hosts
... you of course still need to use an admin powershell...

note: that you will need to turn the Winrm service on before you can apply these codes but once you have your server set to be trusted then go ahead and turn that service back off... it's not actualy needed to manage a hyper-v by remote.