Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, March 9, 2017 2:49 PM
Hi
I have an hyper-v farm with 3 physical host, VMM installed on a VM.
Since some days in VMM console I have all the VM showing "host not responding".
Host Status is showing the following error:
Error (20506)
Virtual Machine Manager cannot complete the Windows Remote Management (WinRM) request on the computer XXX.XXX.lan.
Recommended Action
Ensure that the Windows Remote Management (WinRM) service and the Virtual Machine Manager Agent service are installed and running. If a firewall is enabled on the computer, ensure that the following firewall exceptions have been added: a) Port exceptions for HTTP/HTTPS; b) A program exception for scvmmagent.
In Event viewer (Microsoft-VirtualMachineManager-Server/Admin) the following error appears every 30 minutes:
The Virtual Machine Manager management server could not copy a required Hyper-V authorization file to NODE1.XXX.lan.
Firewall is off on both VMM and Hosts, WinRM service is fine, Machine account and VMM service account are in Administrators group on the Hosts***...***
Could you please help to resolve the issue?
Thank you****
All replies (11)
Monday, March 13, 2017 9:39 AM âś…Answered
Problem solved (after 2 days of troubleshooting); for some reason the 2 policy "Allow delegating fresh credentials" were wrong: they didn't contain the right server list, the list contained two identical values ("WSMAN/*"). Once corrected the second value in the list with "WSMAN/*.mydomain.lan" the VMM started successfully query the Hosts.
Friday, March 10, 2017 7:37 AM
Hello,
You can follow the guide as below for troubleshooting this issue.
Best regards,
Andy Liu
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, March 10, 2017 12:15 PM
Hi Andy, thank you for the response.
I already check the guide you mention but I didn't find any problem on the hosts.
How can I proceed?
Friday, March 10, 2017 1:28 PM
VMM service is running under a domain account and the domain account is a member of the local admin on the Host.
From the VMM server I can successfully run (as the vmm service account) the following command:
winrm get winrm/config -r:host.mydomain.lan
so the winrm seems to work but in the vmm console I still get the error 20506...
Monday, March 13, 2017 10:06 AM
Hello,
Great!
Did you change the policy on the Hyper-V hosts or SCVMM Server?
It would be more helpful for others if you can share more details about the solution.
Thanks a lot!
Best regards,
Andy Liu
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, March 28, 2017 11:34 AM | 1 vote
I changed the policy on the SCVMM server, through Gpedit.
Probably the same result can be accomplished using some CredSSP command...
Thursday, March 30, 2017 10:01 AM
Hello,
Thanks for sharing.
Best regards,
Andy Liu
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Saturday, March 31, 2018 1:13 AM | 2 votes
Thanks for sharing your fix, Sistemista. Although it wasn't the fix I needed, you brought to my attention that the problem was credssp related.
In my case the one Hyper-V server that I couldn't connect to had been patched with the March CU but not yet rebooted. Because the VMM Server had been patched and rebooted AND because I have the GPO setting "Encryption Oracle Remediation=Mitigated" enabled across the domain, any patched client (including the VMM Server) would not be able to make an RDP connection, or as it turns out the WinRM connection needed by VMM, to an unpatched server.
Note that when "Mitigated" is set, a patched server allows connections from unpatched clients, but a patched client will refuse to connect to an unpatched server.
I'm posting this in case someone else runs into this issue. I haven't checked to see if this is already a well-known issue with VMM.
Monday, October 1, 2018 7:15 AM
Hi,
Can you elaborate the steps to configure this ? Facing this issue in my hyper-v host.
Muhammad Saquib Hameed Bhutta
Tuesday, October 2, 2018 5:48 AM
I've also started experiencing a similar issue in the past few days;
3 Hyper-V Nodes SRV2016
1 VMM Server 1801
Management from the Hyper-V nodes is fine, all VM's seem to be fine, from the VMM server all VM's have the status of "Host not responding"
I've reviewed the "Allow delegating fresh credentials" policy and added the second string and rebooted the VMM server. The Nodes don't seem to have received any updates recently, however, they have not been rebooted in over a month.
Monday, October 15, 2018 3:15 AM
To close the loop on this, Microsoft released some Windows updates which have resolved the problem.
Thank's Microsoft...