{"id":177,"date":"2018-02-28T18:48:11","date_gmt":"2018-02-28T18:48:11","guid":{"rendered":"http:\/\/192.168.50.22\/index.php\/2018\/02\/28\/hyperv2016-remote-connect\/"},"modified":"2026-03-15T21:43:15","modified_gmt":"2026-03-16T01:43:15","slug":"hyperv2016-remote-connect","status":"publish","type":"post","link":"https:\/\/smegnl.medina.oh.us\/?p=177","title":{"rendered":"HyperV2016 Remote Connect -Manager -RDP"},"content":{"rendered":"

Manage Hyper-V Server 2016 in a workgroup using Windows 10 Hyper-V Manager<\/h1>\n

*** Most of the below taken from https:\/\/theserverplaypen.wordpress.com\/2018\/01\/23\/manage-hyper-v-server-2012r22016-in-a-workgroup-with-windows-10-hyper-v-manager-in-13-simple-steps<\/a><\/p>\n

Here is an end-to-end guide for using Windows 10 Hyper-V Manager to manage Hyper-V Server 2016 in a workgroup.<\/p>\n

NOTE:<\/strong>\u00a0Windows 10\u00a0Professional or Enterprise or Education edition will be needed. Windows 10 Home edition\u00a0cannot\u00a0<\/em>be used as it does not contain the Hyper-V Manager option.<\/p>\n

These steps have been used successfully to manage multiple installations of Hyper-V. If you\u2019ve followed some other WWW instructions and your configuration is not working, or is flaky, then do a fresh install of Hyper-V Server\u00a0before<\/strong>\u00a0<\/em>following these steps.<\/p>\n

Tested with Hyper-V Server 2016, and Windows 10 Pro Build 1607 (Anniversary Edition) , Build 1703 (Creator\u2019s Edition), and Build 1709 (Fall Creator\u2019s Edition).<\/p>\n

Assumptions:
\n<\/strong><\/p>\n

    \n
  1. The Hyper-V server and the Windows 10 computer are on the\u00a0same<\/em>\u00a0<\/strong>LAN and in the\u00a0same<\/em>\u00a0<\/strong>IP subnet and in the\u00a0\u00a0same<\/em>\u00a0<\/strong>VLAN (if such exists).<\/li>\n
  2. The server and workstation are in the\u00a0same<\/em>\u00a0<\/strong>DNS domain.
    \n<\/strong><\/li>\n<\/ol>\n

    So, start with a simple configuration. You can move things around\u00a0after\u00a0<\/em>you\u2019ve gotten it working.<\/p>\n

    Note:\u00a0<\/strong>If DNS is not yet setup, then add the Hyper-V hostname to the hosts file on the Windows 10 computer \u2014 it\u2019ll make things significantly easier.<\/p>\n

    Lets begin the process:<\/strong><\/p>\n

    NOTE: references to \u201cdomain\u201d in the subsequent steps of this article refer to DNS domain,\u00a0not<\/strong>\u00a0<\/em>Active Directory Domain.
    \nRemember, Hyper-V is being setup in a\u00a0workgroup,\u00a0<\/strong>i.e., not associated with any Active Directory domain.
    \nFor this article, my DNS domain is \u201cfshome.local<\/span>\u201d. My Hyper-v server will be \u201chyperv2\u201d<\/p><\/blockquote>\n

    If starting with a fresh install of Hyper-V Server 2016, here\u2019s the typical screen after the install:<\/p>\n

    <\/p>\n

    If you configure in the following order, the necessary reboots will be at the end of the process\u2026<\/p>\n

    7) Remote Desktop \u2013\u00a0enabled<\/em>. Select the choice of authentication as applicable to you. I used option 2)\u00a0Allow clients running any version of Remote Desktop (less secure)<\/em><\/p>\n

    3) Add Local Administrator
    \nNOTE: the local administrator user name\/password is significant as it will be used later in the management process<\/b>.\u00a0BTW, this password is valid for 42 days by default but we\u2019ll fix that in Part 1, Step 2 of this article.<\/em><\/p>\n

    4) Configure Remote Management \u2013\u00a0leave Enabled<\/em>
    \nConfigure Server Response to Ping \u2013\u00a0Yes<\/em><\/p>\n

    5) Windows Update Settings \u2013\u00a0set to your perference<\/em><\/p>\n

    8) Network Settings \u2014\u00a0will be easier if set to a Static IP<\/em><\/p>\n

    9) Date and Time \u2014\u00a0set as appropriate for your location<\/em><\/p>\n

    10) Telemetry Settings \u2014\u00a0set to your preference<\/em><\/p>\n

    1) Domain\/Workgroup \u2014\u00a0leave it as WORKGROUP or change to your Workgroup name<\/em><\/p>\n

    2) Computer Name \u2014 will require server reboot
    \nNote: the computer name can be just a hostname, e.g., \u201chyperv2\u201d. It does not need to be a FQDN, e.g., \u201chyperv2.fshome.local<\/span>\u201d<\/em><\/p>\n

    6) Download and Install Updates \u2013 will require server reboot<\/p>\n

    We\u2019re now done with the fresh install configuration.<\/p>\n

    \n


    \nPart 1: Hyper-V Server Configuration<\/strong><\/p>\n

    After the post intallation setup and rebooting here is what it looks like:<\/p>\n

    \"hv_step1\"<\/p>\n

    Now select the command prompt window \u2013 it\u2019s hidden behind the blue window.<\/p>\n

    Step 1:<\/strong>\u00a0disable the Hyper-V built-in firewall. You\u2019re behind your firewall\/router so doing this is OK, don\u2019t worry. However, I would not do this in a production network. See at the bottom of this page for more specific Firewall setting<\/em>s.\u00a0in fact i did not do this at all on my production server and it worked just fine for connecting the manager. Did not work for ping or RDP .<\/em>\u00a0Enter the following:<\/p>\n

    netsh advfirewall set allprofiles state off<\/strong><\/pre>\n
    Step 2<\/strong>: disable the password age out. By default,\u00a0the Local Administrator users\u2019 password is valid for 42 days<\/em>. You don\u2019t want to get locked out of your Hyper-V server if using RDP. So enter:<\/p>\n
    net accounts \/maxpwage:unlimited<\/strong><\/pre>\n
    Verify the new value is set<\/p>\n
    net accounts\n\"hv_step3\"\n\n<\/strong><\/pre>\n
    Step 3:<\/strong>\u00a0allow PowerShell Remoting.<\/p>\n
    At the C:\\ command prompt type\u00a0powershell<\/em>. Once PowerShell is running, enter the following:<\/p>\n
    enable-psremoting<\/strong><\/pre>\n
    That is it. The three steps are *ALL<\/strong>*<\/strong>\u00a0that are required on the Hyper-V server side.<\/p>\n
    NOTE:<\/strong>\u00a0Step 3 is not needed on Hyper-V Server 2016. It is enabled by default (Option # 4 in the Hyper-V server configuration screen).<\/em><\/p>\n
    Here is a summary of the three steps:<\/p>\n
    <\/p>\n
    Part 2: Windows 10 Configuration<\/span>
    \n<\/strong><\/h3>\n
    Let\u2019s now move over to to the Windows 10 computer.<\/p>\n
    Verify we can reach the Hyper-V server by pinging it by its hostname.<\/p>\n
    ping hyperv2
    \n<\/strong><\/p><\/blockquote>\n
    If ping is not successful, you\u2019ll need to troubleshoot and fix\u00a0before<\/em>\u00a0<\/strong>moving on.<\/p>\n
    Step 4:<\/b>\u00a0Install the Hyper-V Manager<\/p>\n
    \"hv_turn_windows_feature_on_off\"<\/p>\n
    After the Hyper-V manager install has completed, start PowerShell with\u00a0 \u201cRun As Administrator<\/em>\u201c.<\/p>\n
    Step 5:<\/strong>\u00a0set the network connection profile \u2013 we have to change to PRIVATE<\/p>\n
    Set-NetConnectionProfile -NetworkCategory private
    \n<\/strong><\/p><\/blockquote>\n
    Step 6:\u00a0<\/strong>verify the net-connectionprofile new settings<\/p>\n
    Get-NetConnectionProfile<\/strong><\/p><\/blockquote>\n
    \"hv_step6\"<\/p>\n
    Step 7:<\/strong>\u00a0setup remote management.<\/p>\n
    Set-WSManQuickConfig<\/strong><\/p><\/blockquote>\n
    \"hv_step7\"<\/p>\n
    Step 8:<\/strong>\u00a0enable a trusted host. In this case the\u00a0trusted host<\/em>\u00a0will be the Hyper-V server<\/p>\n
    Set-Item WSMan:\\localhost\\Client\\TrustedHosts -Value \u201chyperv2.fshome.local<\/span>\u201d
    \n<\/strong><\/p><\/blockquote>\n
    Or<\/strong>, if there are\u00a0multiple<\/em>\u00a0<\/strong>trusted hosts in the\u00a0same<\/em>\u00a0<\/strong>DNS domain you can do it this way by using the * as the hostname wildcard<\/p>\n
    Set-Item WSMan:\\localhost\\Client\\TrustedHosts -Value *.fshome.local<\/span>
    \n<\/strong><\/p><\/blockquote>\n
    Or<\/strong>, if there are\u00a0multiple<\/em>\u00a0<\/strong>hosts in\u00a0any<\/em>\u00a0<\/strong>domain, then use the * modifier globally as shown<\/p>\n
    Set-Item WSMan:\\localhost\\Client\\TrustedHosts -Value *
    \n<\/strong><\/p><\/blockquote>\n
    Step 9:<\/strong>\u00a0Now let\u2019s check to make sure the trusted host is correct<\/p>\n
    Get-Item WSMan:\\localhost\\Client\\TrustedHosts<\/strong><\/p><\/blockquote>\n
    \"hv_step9\"<\/p>\n
    Step 10:<\/strong>\u00a0Add the alternate user credentials (aka, the Local Administrator) configured in Step 3 of the fresh install of Hyper-V.<\/p>\n
    In my network I have multiple Hyper-V servers, and the Trusted Hosts is set as \u201c*.fshome.local<\/span>\u201d, so the user is added for each Hyper-V server in my network like so:<\/em><\/p>\n
    cmdkey \/add:hyperv \/user:sysadmin \/pass:PaSsWoRd
    \n<\/strong><\/p><\/blockquote>\n
    cmdkey \/add:hyperv2 \/user:sysadmin \/pass:PaSsWoRd
    \n<\/strong><\/p><\/blockquote>\n
    cmdkey \/add:hyperv3 \/user:sysadmin \/pass:PaSsWoRd
    \n<\/strong><\/p><\/blockquote>\n
    If there was a different user and password for each Hyper-V server, we would adjust the above to reflect that. In my case, the user and password are the same across all my Hyper-V servers to keep things sane.<\/p>\n
    \n
    *Note<\/strong>: let\u2019s say you did not have DNS setup, nor your \u2026\\drivers\\etc\\hosts file, then this is how you\u2019d setup cmdkey using IP addressing<\/p>\n
    cmdkey \/add:192.168.1.111 \/user:sysadmin \/pass:PaSsWoRd<\/strong><\/pre>\n
    And, every step in this article where there is reference to the Hyper-V server name you would replace with the IP address.<\/p>\n
    When you go to add the Hyper-V server in the Hyper-V Manager, you\u2019d also add it by IP address<\/p>\n
    \"hv_step10a\"<\/p>\n
    Step 11:<\/strong>\u00a0Allow the user credentials\u00a0 (configured in the above\u00a0cmdkey<\/em>)\u00a0on this computer (Windows 10) to be sent to the remote computer (the Hyper-V server):
    \n(note: the entries are all on one line even though WordPress shows multiple lines)<\/i><\/p>\n
    Enable-WSManCredSSP -Role client -DelegateComputer \u201chyperv.fshome.local<\/span>\u201d
    \n<\/strong><\/p><\/blockquote>\n
    Now the command will only allow one computer,\u00a0hyperv.fshome.local<\/span><\/em><\/strong>. So, to allow the user credentials to be sent to another remote computer we add the other computer\u2019s name:<\/p>\n
    Enable-WSManCredSSP -Role client -DelegateComputer \u201chyperv2.fshome.local<\/span>\u201d
    \n<\/strong><\/p><\/blockquote>\n
    Or<\/strong>, we can configure multiple computers at one time<\/p>\n
    Enable-WSManCredSSP -Role \u201cClient\u201d -DelegateComputer \u201chyperv.fshome.local<\/span>\u201d, \u201chyperv2.fshome.local<\/span>\u201d, \u201chyperv3.fshome.local<\/span>\u201d
    \n<\/strong><\/p><\/blockquote>\n
    Or<\/strong>, to allow the users credentials on this computer to be sent to\u00a0any\u00a0<\/em><\/strong>Hyper-V host in the\u00a0same<\/em>\u00a0<\/strong>DNS domain, we can just use the hostname wild card:<\/p>\n
    Enable-WSManCredSSP -Role client -DelegateComputer \u201c*.fshome.local<\/span>\u201d
    \n<\/strong><\/p><\/blockquote>\n
    Or<\/strong>, to allow the users credentials on this computer to be sent to\u00a0any\u00a0<\/em><\/strong>Hyper-V host in\u00a0any\u00a0<\/em><\/strong>DNS domain, we can just use the host and domain wild card:<\/p>\n
    Enable-WSManCredSSP -Role client -DelegateComputer \u201c*\u201d
    \n<\/strong><\/p><\/blockquote>\n
    Tip:<\/strong>\u00a0for Managed Service Providers deploying Hyper-V, the above method is useful if you carry one laptop that is used on-site for all your customers \u2013 each being their unique DNS domains. Of course, you\u2019d want to set one universal local admin user\/password across all your customers for sake of making this useful.<\/em><\/p>\n
    Step 12:<\/strong>\u00a0now let\u2019s verify the WSManCredSSP configuration<\/p>\n
    Get-WSManCredSSP<\/strong><\/p><\/blockquote>\n
    \"hv_step12_2\"<\/p>\n
    Now, if there was a mistake that was made, or a need to reconfigure, or to start over from scratch, or just to experiment, whatever, the WSManCredSSP configuration can be cleared by doing the following and restarting from Step 11<\/p>\n
    Disable-WSManCredSSP -Role Client
    \n<\/strong><\/p><\/blockquote>\n
    Step 13:<\/strong>\u00a0allow COM Security anonymous login remote access. While still in PowerShell, type the following:<\/p>\n
    dcomcnfg
    \n<\/strong><\/p><\/blockquote>\n
    <\/p>\n
    double-click on the Computers folder<\/p>\n
    <\/p>\n
    right-click on the My Computer icon<\/p>\n
    <\/p>\n
    click on COM Security<\/p>\n
    <\/p>\n
    in the Access Permissions section of the window, click Edit Limits\u2026<\/p>\n
    <\/p>\n
     Select ANONYMOUS LOGON\n Check the box for Remote Access\n Click OK<\/pre>\n
    Close the dcomcnfg window.<\/p>\n
    That is it. The Window 10 configuration steps are complete. You are done!<\/p>\n
    At this point you should be able to launch the Windows 10 Hyper-V Manager and successfully connect and add the Hyper-V server(s) to the manager.<\/p>\n
    \"hv_success\"<\/p>\n
    Most of the above taken from\u00a0https:\/\/theserverplaypen.wordpress.com\/2018\/01\/23\/manage-hyper-v-server-2012r22016-in-a-workgroup-with-windows-10-hyper-v-manager-in-13-simple-steps<\/a><\/p>\n
    Remote Desktop Hyper-V Server 2016<\/h1>\n
    uptop we enabled\u00a0 Remote Desktop \u2013\u00a0enabled<\/em>. Select the choice of authentication as applicable to you. I used option 2)\u00a0Allow clients running any version of Remote Desktop (less secure)
    \n<\/em>Enabling Remote Desktop using the prompts on #7 of the option screen might make one think that it is therefore possible to connect immediately via an RDP client. Due to a Microsoft security setting, this does not work.
    \n<\/em>This is because the network interface is set to public, yep public for a server. This does not allow RDP. To fix do the bellow in windows Powershell on the HyperV server…<\/p>\n