none
Hyper-V Server 2016 (TP4): HowTo manage Hyper-V with DesktopOS Hyper-V Manager (and Bug?)

    Question

  • Since I struggled quite a bit - I am just an enthusiast without any proper training - setting up a Hyper-V Server 2016 (TP4) "CORE" to be remotely managed from the GUI Hyper-V Manager on my Windows 10 Desktop WITHOUT A DOMAIN (Workgroup only), here is how you do it (quick and dirty):

    All those tutorials out there are largely outdated, the steps are actually quite simple, if you do know them...

    On the HOST:

    Powershell:

    PS C:\Users\Administrator>enable-PSremoting 
    PS C:\Users\Administrator>enable-wsmancredssp -role server

    On the CLIENT:

    1. Powershell:

    PS C:\Users\Administrator>start-service winrm
    PS C:\Users\Administrator>Enable-WSManCredSSP -Role client -DelegateComputer *
    PS C:\Users\Administrator>stop-service winrm

    2. GPEDIT (as administrator)

    Local Computer Policy-->Computer Configuration-->Administrative Templates-->System-->Credentials Delegation-->"Allow delegating fresh credentials with NTLM-only server authentication" set "Enabled" and "Add servers to the list" (click "Show..."), enter "WSMAN/*" as Value, hit OK 2 times.

    3. Fire up Hyper-V Manager and connect to server only with IP-address and enter as user "YOURIP\ADMINACCOUNT_ON_HOST" and its passwort. There you go.

    No manual firewall settings required anymore. No additional service starting/configuration required anymore. No need to manually configure TrustedHosts anymore. No need to have identical admin-accounts on host and client. No fiddling with hosts files... BUT

    ...is the following a BUG?

    I noticed a strange behaviour around the hosts file as follows: 

    If your Windows 10 Desktop client is (or WAS!) domain-joined, the above will only work if you allocate the HyperVHost-hostname to its IP in the client's hosts file. Still you do not need to set "localhost\client\trustedhosts" anywhere, simply mapping the IP to the hostname works. Did I do something wrong? Is this a known issue?

    Just curious. Thanks!



    • Edited by Besterino Friday, April 1, 2016 2:16 PM
    Friday, April 1, 2016 2:07 PM

Answers

All replies

  • Hi Besterino,

    >>If your Windows 10 Desktop client is (or WAS!) domain-joined, the above will only work if you allocate the HyperVHost-hostname to its IP in the client's hosts file.

    Are you connecting to the server using IP address or hostname?

    If hostname, I suppose it is normal behavior.

    When connecting using hostname, client would query DNS server for the corresponding IP address. If the hyper-v host is not joined to domain, the query will fail and connection would not succeed.

    When the hostname and IP address is added into hosts file. The client would get the IP address from the entry and it would not query DNS server. Then the connection would succeed.

    Best Regards,

    Leo


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, April 4, 2016 5:30 AM
    Moderator
  • No, I am connecting using (only) the IP address. That is why I think this behavior is weird. Also, I have no entries in trustedhosts where a mapping via hosts file might have an influence.
    Monday, April 4, 2016 6:28 AM
  • Hi Besterino,

    I'm afraid I could not find any official document about the issue. Considering Server 2016 is a preview version and Windows 10 was just released, you may wait for later updates.

    You could also post in Windows 10 forum to see if there is any difference between domain-joined and no-domain clients on it:https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=Windows10ITPro&filter=alltypes&sort=lastpostdesc

    Best Regards,

    Leo


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, April 5, 2016 9:28 AM
    Moderator
  • Hi Besterino,

    Thanks for this awesome (sweet and simple) recipe.

    It works great!

    **** Just to let you know, I used Windows 10 Enterprise Anniversary Update (1607), it worked like a charm, I did not have to fiddle with my client's host file.


    Warmest Regards, Richard. RICHARD DOR | (MTA, MCTS, MCITP) | +233246814598

    Friday, March 17, 2017 11:24 AM
  • Thanks!
    Saturday, August 5, 2017 10:46 PM