Configuring Hyper-V Server Manager on a workgroup Client. Part 3 #hyperv #virtualmachines

All you need to know about setting up Hyper V Server 2019.

After the installation of the hyper-v server and the enabling of the Hyper-V manager on the client follow these steps to pull the server Hyper-V Manager on the Client Hyper-V Management environment.
1st

\\Both the client and the server Network Adapter need to be set to "Private".
\\This command will display the current network profile. Run the command on both client and server to verify the profile.
Get-NetAdapter|Get-NetConnectionProfile

\\This command will set the profile
Set-NetConnectionProfile -InterfaceAlias "Ethernet" -NetworkCategory Private

\\Once that is set review the connection again with the Get command
Get-NetAdapter|Get-NetConnectionProfile

\\Enable-PSRemoting
Enable-PSRemoting

\\Enable-WSManCredSSP -Role server

Enable-WSManCredSSP -Role server

\\Enable the windows feature option on windows

\\Edit the host file and add the dns name of the HyperV server.
192.168.1.3 SANDBOX

On the client Machine
run

start-service -name winrm
set-item wsman:\localhost\client\trustedhosts -value SANDBOX
stop-service -name winrm
\\ This command verifies the local hosts is a trustedhost.
Get-Item WSMan:\localhost\Client\TrustedHosts

#hyper
#hyperv
#virtual
#virtualmachines
#vm
#vmware
#vmwareworkstation
#vmwarecloud

[ccip]

HyperV server manager is very useful and a much lesser expensive option compared to any windows datacenter options. However, the complexity of the configuration have scared many technicians away from it. HyperV server manager is free. You can install as many VMs as possible. Then ensure that those VMs are running the latest operating systems with the proper licensing. This is just my thought on it.

[MadManMarkAu]

Every single post on the internet either tells you to do the wrong things, or gives you commands that makes the client PC trust ALL computers, no mater what. This is the only post on the internet I have found that tells you how to do this correctly.

The command list in the description of this video got me up and running again after migrating to a new client machine.

[tjbrison]

This is the only solution that worked for me - I have tried for hours to get this working all to no avail - until I came accross this video. Many thanks for the considerable effort it tool to make.

[juanc.addamo]

I was looking for a way to set up a Hyper V server in a workgroup and the only solution that worked was yours. Thank you!

[mhos]

Thank for the effort of making this video!

[demetriusjohnson]

wow this worked for me. Thank you kind sir.

[christopherpeterson]

-Kerberos only works with domain joined, not workgroup, and not hybrid or Azure AD
-CredSSP works with everything, but its an implicit trust to the host and therefore discouraged
-NTLM works in workgroups and domains but it has known exploits

I've decided to implement OpenSSH with key rotation using Ansible authorized_key_module

Then you can run WinRM and Hyper-V manager

[WladimirTavares]

Thank you! I've been going around to make Hyper-V Manager connect to a remote server by using WinRM over HTTPS, using a self signed certificate. So far, I've been unsuccessful. WinRM is configured I can do PSRemoting over HTTPS but Hyper-V Manager keeps on connection to the HTTP listener

[cloudbase]

Instead of changing permissions on the hosts file, why not run command prompt or PowerShell as administrator? Then you can simply do:
notepad

If you use PowerShell, you can also do some interesting things like:

Get-Content | Select-Object -Last 5

This will show the last 5 lines of the hosts file (something like _tail_ on *nix). If you're only needing to add a line--you're not modifying existing hosts content, in your example, you could do something like:

Add-Content "192.168.1.3`t`tsandbox"

This will add a new line to the hosts file with the IP address 192.168.1.3, two tab characters, and the hostname _sandbox_

There is probably a more elegant PowerShell approach, but if you want to remove the last line of the hosts file:

$HostsContent = Get-Content
$HostsContent | Select-Object -Last ($HostsContent.Length - 1) | Out-File

You might wonder about chaining the Get-Content, Select-Object, and Out-File cmdlets. That can easily produce unexpected results (e.g. empty file) if you're working with the same file for Get-Content and Out-File.

I'm also wondering, when you attempted to connect to the remote Hyper-V host (in Hyper-V Manager), why did you enter the username as .\Administrator instead of sandbox\administrator? In the end I guess it didn't matter, but for hostnames . in .\Administrator refers to "this computer/system." But you don't want to authenticate to the server (sandbox) using the local (on the Windows 10 PC) administrator account. You want to authenticate using the administrator account on the server.

[arpitbrijcement]

After following all yours step, at last it gives " An error occurred while attempting to connect to server Check that the Virtual Machine Management service is running and that you are authorized to connect to the server."
The operation is not supported.

[NLDiminish]

could you try this on Windows 11 client?

[ccip]

HyperV server manager is very useful and a much lesser expensive option compared to any windows datacenter options. However, the complexity of the configuration have scared many technicians away from it. HyperV server manager is free. You can install as many VMs as possible. Then ensure that those VMs are running the latest operating systems with the proper licensing. This is just my thoughts on it.