On Hyper-V Server

• Enable Remote Management
• Enable Remote Desktop
• Set Computername
• Enable WSMan and PS-Remoting:

Enable-PSRemoting  
Enable-WSManCredSSP -Role server  

On Managing Client

• Configure hosts or DNS entry for Hyper-V Server
• Ensure network profile is “Private”:

Set-NetConnectionProfile -InterfaceAlias Ethernet -NetworkCategory Private  

• Temporarily start WinRM and add Hyper-V Server as Trusted Host:

Start-Service -Name winrm  
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "hyperv-server.home.local"  
Stop-Service -Name winrm  

• Enable Hyper-V Management Tools in Windows Features
• Add Hyper-V Administrator credential with cmdkey:

cmdkey /add:HYPERV-SERVER /user:Administrator /pass:  

• Launch Hyper-V Manager and connect to server (don’t specify user)
  • or, launch Hyper-V Manager with runas:

runas /user:HYPERV-SERVER\Administrator /netonly "mmc virtmgmt.msc"  

Summary

After lots of mucking around, this is the bare-minimum working configuration I’ve found to remotely manage a Hyper-V server in a non-domain environment.

I’m still not 100% certain why Hyper-V Manager does not work with supplied credentials and the cmdkey or runas workaround is necessary.

Stolen from: https://blog.ropnop.com/remotely-managing-hyper-v-in-a-workgroup-environment