Hyper-V 2019 on a domain

  • This guide is borrowed directly from my 2016 Take 2 thread. There are a few minor changes.

    Install Hyper-V 2019 on a server - very typical Windows install, so I am not including any screen shots.
    Typical install will have a 40-80 GB 😄 and the rest as the 😨 drive.

    Upon first boot you will be prompted to create a local admin password. After setting the password you should see something like this.

    The following step is completely optional, assuming you have DHCP. These changes will become meaningless if you create a Network Team Adapter and include the port you would configure here.

    I'll start by setting a static IP address, option 8 for networking.

    In my case only one NIC is plugged in, so that's the only one you can manage via sconfig (the default menuing system you see here).

    We want to set the Network Adapter Address, so option 1

    We want static, so s

    Type in the IP address information as requested

    Now we set the DNS server, option 2, click OK to continue.
    you're prompted for a secondary DNS, enter it if you have one

    Press 4 to return to the main menu.

    Now I'll join the domain, option 1, then D for domain

    Type in the name of the domain, then you're prompted for the user that can add computers to the domain

    A new window opens and prompts you for that user's password

    You're returned to sconfig and prompted about changing the computer name before reboot, click yes

    You're now prompted for a domain account that has rights to change computer names
    you can't reuse a computer name that already exists - unlike adding a desktop machine, Hyper-V will simply error indicating that an account of that name already exists

    And again with a new black window asking for that user's password.

    Prompted to restart to apply change, click yes.

    Upon restart, chose option 6 to install updates.

    You'll likely be prompted to reboot - do it.

    The Original ISO for Hyper-V 2019 is broken. It doesn't allow RDP to function. MS released a patch on 3-3-2019 (windows10.0-kb4482887-x64_826158e9ebfcabe08b425bf2cb160cd5bc1401da.msu) that fixes this and other things. Here is the link to the MS download.

    Here is the original ISO name so you know if you need to apply this patch. 17763.1.180914-1434.rs5_release_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

    Install this and reboot

    Now we'll enable remote desktop access via the sconfig menu. Option 7, e for enable, and 1 for the best secure option.
    FYI - Remote access via Server Manager is available by default once you join a domain. You'll still likely want remote desktop access though. Additionally, you can install ScreenConnect/ConnectWise or MeshCentral

    This is a Dell server, so I install OMSA - I won't go into details, you can see JB's writeup here
    I'm still looking for good HP add-on options.

    Change firewall to allow remote administration

     Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”
     Enable-NetFirewallRule -DisplayGroup “Remote Event Log Management”
     Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”
     Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true
     Set-NetFirewallRule -DisplayGroup 'Windows Defender Firewall Remote Management' -Enabled true
     Set-NetFirewallRule -DisplayGroup 'Remote Service Management' -Enabled true
     Enable-NetFirewallRule -name RVM-RPCSS-In-TCP,RVM-VDSLDR-In-TCP,RVM-VDS-In-TCP

    *note - MS changed the Display group from Windows Firewall Remote Management to Windows Defender Firewall Remote Management in 2019
    note - MS removed access to Device Manager remotely as of Server 2012
    *Here is a possible solution for those that want a GUI *
    Here is an MS blog post about using Powershell for device management

    Remote access needs to be enabled on the machine you're remoting from as well as the one you're remoting too,
    netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes enables the needed piece from the local side to allow remote access to Disk Manager OR you can use the powershell command from above Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”

    Change the location to store VMs
    Launch Hyper-V manager as a domain admin user (or a domain user who has admin rights on the Hyper-V host)
    If you haven't already added the Hyper-V host, do so now. You'll need to use the FQDN.
    You should see something like this.

    Right click on your Hyper-V host and choose Hyper-V Settings

    Change the Virtual Hard Disk and Virtual Machine to your desired location

    Create a NIC team, even if only one NIC will be it, because it will be easier to add a second NIC later if needed.
    You have two options

    1. via powershell, connect to the console and using the cmd.exe window, get into powershell by typing powershell
      your prompt should change to a powershell prompt.
      Type Get-NetAdapter to see a list of your adapters like this.

    To create a team using my output
    New-NetLGfoTeam -Name Team1 -TeamMembers "Ethernet 4","Ethernet 3"

    1. You can use Server Manager from a Windows 10 PC. Launch Server manager as domain admin,
      locate the Hyper-V host, right click and choose Configure NIC Teaming

    Next to Teams, click the drop down and choose New Team

    Give the team a name, then choose the desired adapters, you can change any needed settings under additional properties (exposed here)

    FYI, the new team may or may not use the IP settings set above. If doing this remotely, make sure you have either local access to the host, or something like iLo incase the settings are not what you set above.
    Now could be the time to set the IP of the new network adapter. After setting it - it will take several mins for DNS to update properly - until that happens, you'll have difficulties connecting using Hyper-V Manager or Server Manager.

    Configure a vSwitch, right click on the Hyper-V host and choose Virtual Switch Manager

    Click Create Virtual Switch

    Name your vSwitch, choose External, then choose your newly created NIC Team.
    MS calls the first team Microsoft Network Adapter Multiplexor Driver
    *If these are the only adapters connected to the network, make sure you leave Allow management operating system to share this network adapter checked.

    *note - make sure you have the correct adapter - the Multiplexor Driver - otherwise if you use the default listed adapter and it's part of the NIC Team, you'll get an error.

    You're now ready to create your first VM.

  • Even though it's posted above, I want to remind people that if you have the original HV 2019 ISO, you'll need to manually download and install kb4482887 as MS isn't pushing it out via the update servers as of this post.

  • @Dashrender said in Hyper-V 2019 on a domain:

    The Original ISO for Hyper-V 2019 is broken.

    This is not true. There is nothing wrong with the ISO and Hyper-V server installs perfectly.

    A component inside, does not work correctly, that is true. But RDP is hardly the big need you are trying to make it out to be here.

    Actual console access can be obtained from iDRAC or as stated something like MeshCentral or ScreenConnect.

  • All of the above and more but done in PowerShell on our KB site.

  • @PhlipElder said in Hyper-V 2019 on a domain:

    All of the above and more but done in PowerShell on our KB site.

    New-NetLbfoTeam -Name vSwitch -TeamMembers *



  • This post is deleted!

  • @Dashrender said in Hyper-V 2019 on a domain:

    @PhlipElder said in Hyper-V 2019 on a domain:

    All of the above and more but done in PowerShell on our KB site.

    New-NetLbfoTeam -Name vSwitch -TeamMembers *



    I've posted that before.