I have used gpedit to 'Allow Fresh Credentials with NTLM-only Server Authentication' and added the server name.
A computer policy does not allow the deligation of the user credentials to the target computer because the computer is not trusted'. If I use the 'Connect as another user' option with any local account on Hyper-V server I get a much longer error: "The operation on computer 'Server' failed: The winRM client cannot process the request.
Verify that the computer exists on the network and that the name provided is spelled correctly." The following error occurred while using Kerberos authentication: Cannot find the computer. If I don't use the 'Connect as another user' option I get "WinRM cannot process the request. I have mirrored accounts on the Hyper-V 2012 R2 servers for both Administrator and his logon. I've temporarily disable the firewalls on all three machines in question and I've run hvremote on the servers with no errors. I've done the usual setup and remote management works fine with Windows 8.1 and using Hyper-V Manager from a Windows 2012 R2 server. I've found several places that say this should work but I've spent the last two hours trying to make it work but have failed miserably. His Workstation is in the domain and the two Hyper-V 2012 R2 servers are in workgroup mode.
I have a situation where an admin wants to use his Windows 10 Professional workstation's Hyper-V manager to manage two Hyper-V 2012 R2 setups. Anyone have the Hyper-V Manager from Windows 10 working with a workgroup Hyper-V 2012 R2 server?