Microsoft Hyper-V Server 2019 - RD Virtualization Host feature missing RRS feed

  • Question

  • I'm trying to use Hyper-V Server 2019 as a virtualization host.  This fails.

    I have 3 computers;

    1. domain controller
    2. Windows Server 2019, which will be RD Connection Broker and RD Web Access
    3. Hyper-V Server 2019, which will be RD Virtualization Host

    When I attempt to install this using Server Manager, RD Connection Broker and RD Web Access installation succeeds, but RD Virtualization Host fails.

    Investigating further, the feature is missing! Here's some PowerShell, confirming I am running Hyper-V Server 2019 (downloaded today, 3 July 2019), and the Remote Desktop Virtualization Host feature simply not there!

    Get-ComputerInfo | select OSName,OSVersion
    OsName                   OsVersion
    ------                   ---------
    Microsoft Hyper-V Server 10.0.17763
    Display Name                                            Name                       Install State
    ------------                                            ----                       -------------
    [X] File and Storage Services                           FileAndStorage-Services        Installed
        [ ] File and iSCSI Services                         File-Services                  Available
            [ ] File Server                                 FS-FileServer                  Available
        [X] Storage Services                                Storage-Services               Installed
    [X] Hyper-V                                             Hyper-V                        Installed
    [ ] Remote Desktop Services                             Remote-Desktop-Services        Available
    [ ] .NET Framework 3.5 Features                         NET-Framework-Features         Available
        [ ] .NET Framework 3.5 (includes .NET 2.0 and 3.0)  NET-Framework-Core               Removed
    [X] .NET Framework 4.7 Features                         NET-Framework-45-Fea...        Installed
        [X] .NET Framework 4.7                              NET-Framework-45-Core          Installed
        [ ] ASP.NET 4.7                                     NET-Framework-45-ASPNET        Available
        [X] WCF Services                                    NET-WCF-Services45             Installed
            [X] TCP Port Sharing                            NET-WCF-TCP-PortShar...        Installed
    [ ] Background Intelligent Transfer Service (BITS)      BITS                           Available
        [ ] Compact Server                                  BITS-Compact-Server            Available
    [ ] BitLocker Drive Encryption                          BitLocker                      Available
    [ ] Data Center Bridging                                Data-Center-Bridging           Available
    [ ] Enhanced Storage                                    EnhancedStorage                Available
    [ ] Failover Clustering                                 Failover-Clustering            Available
    [ ] I/O Quality of Service                              DiskIo-QoS                     Available
    [ ] Media Foundation                                    Server-Media-Foundation        Available
    [ ] Multipath I/O                                       Multipath-IO                   Available
    [ ] Remote Server Administration Tools                  RSAT                           Available
        [ ] Feature Administration Tools                    RSAT-Feature-Tools             Available
            [ ] BitLocker Drive Encryption Administratio... RSAT-Feature-Tools-B...        Available
            [ ] DataCenterBridging LLDP Tools               RSAT-DataCenterBridg...        Available
            [ ] Failover Clustering Tools                   RSAT-Clustering                Available
                [ ] Failover Cluster Module for Windows ... RSAT-Clustering-Powe...        Available
                [ ] Failover Cluster Automation Server      RSAT-Clustering-Auto...        Available
                [ ] Failover Cluster Command Interface      RSAT-Clustering-CmdI...        Available
        [ ] Role Administration Tools                       RSAT-Role-Tools                Available
            [ ] Hyper-V Management Tools                    RSAT-Hyper-V-Tools             Available
                [ ] Hyper-V Module for Windows PowerShell   Hyper-V-PowerShell             Available
    [ ] SMB 1.0/CIFS File Sharing Support                   FS-SMB1                        Available
        [ ] SMB 1.0/CIFS Client                             FS-SMB1-CLIENT                 Available
        [ ] SMB 1.0/CIFS Server                             FS-SMB1-SERVER                 Available
    [ ] SMB Bandwidth Limit                                 FS-SMBBW                       Available
    [ ] SNMP Service                                        SNMP-Service                   Available
        [ ] SNMP WMI Provider                               SNMP-WMI-Provider              Available
    [ ] Telnet Client                                       Telnet-Client                  Available
    [X] Windows Defender                                    Windows-Defender               Installed
    [X] Windows PowerShell                                  PowerShellRoot                 Installed
        [X] Windows PowerShell 5.1                          PowerShell                     Installed
        [ ] Windows PowerShell 2.0 Engine                   PowerShell-V2                  Available
    [ ] Windows Server Backup                               Windows-Server-Backup          Available
    [ ] Windows Standards-Based Storage Management          WindowsStorageManage...        Available
    [ ] Windows Subsystem for Linux                         Microsoft-Windows-Su...        Available
    [X] WoW64 Support                                       WoW64-Support                  Installed

    According to Using Hyper-V Server 2008 R2 for VDI – Matthijs's blog I would have expected to something like this, clearly showing "Remote Desktop Virtualization Host" as a component;

    But that doesn't appear on Hyper-V Server 2019.


    Add-WindowsFeature –Name RDS-Virtualization

    ...simply doesn't work.

    How do install "Remote Desktop Virtualization Host" on Hyper-V Server 2019?

    Wednesday, July 3, 2019 5:55 PM

All replies

  • Hi,

    In general, there should be detail server roles listed under Remote Desktop Services, as below screenshot:

    Based on your description, there is only “[ ] Remote Desktop Services  Remote-Desktop-Services  Available” displays. As far as I know, Windows Server 2019 Standard and Datacenter version should have full support for RDS server roles. Windows Server 2019 Essentials version does not full support for RDS server roles. Also, Core version support part of RDS server roles, however, RD VH is supported on Core version.

    Please open Run, type “winver” or “msinfo32” to check your current OS version, if it is Standard or Datacenter, but lack of RDS server roles, as it is newly installed system, I would recommend you to re-install the system using fully/complete installation medium and check the result.  

    Best Regards,
    Eve Wang

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

    Thursday, July 4, 2019 3:13 AM
  • Thanks Eve.

    Unfortunately this isn't very helpful;

    • the second part is redundant; I've already clearly articulated and demonstrated it is Hyper-V Server 2019
    • the first part is merely repeating what I've already determined

    Why, when Microsoft say

    Hyper-V Technology Overview | Microsoft Docs

    last edited: 2016-11-29

    last retrieved: 2019-07-04

    Applies To: Windows Server 2016, Microsoft Hyper-V Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019
    Some ways Hyper-V can help you
    • Establish or expand a virtual desktop infrastructure (VDI). Use a centralized desktop strategy with VDI can help you increase business agility and data security, as well as simplify regulatory compliance and manage desktop operating systems and applications. Deploy Hyper-V and Remote Desktop Virtualization Host (RD Virtualization Host) on the same server to make personal virtual desktops or virtual desktop pools available to your users.

    ...can I not add the Remote Desktop Virtualization Host feature to Microsoft Hyper-V Server 2019?

    I have checked whether RDVH is a feature-on-demand (FOD) that can be installed from a .CAB file on the .ISO.  The documentation states it isn't.  The list of .CAB files on the Hyper-V Server 2019 .ISO don't offer RDVH.

    Even if it was available on demand, typically it would still be listed in get-windowsfeature.

    The final possibility is it's available as a standalone .MSU, in the same way that you can add Remote Server Administration Tools (RSAT) to client operating systems.  But I can find nothing to suggest this either.

    Eve - please escalate this. I doubt I'm the only one who will encounter this.  the Hyper-V Server 2019 .ISO was only issued towards the end of June 2019, so more IT professionals will encounter this soon.

    Thursday, July 4, 2019 5:02 AM
  • I suggest you create a feedback request over this to get a final answer from Microsoft about this.

    You'll find the feedback option at the bottom of the documentation page, or you can create a new issue straight over here on GitHub:

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, July 4, 2019 6:54 AM
  • Hi,

    RD VH should be install on physical server as it should be working with Hyper-V to provide the full functions.  If it is Hyper-V specific installation medium, such as VHD file, I would recommend you to install with other  ISO file.

    Best Regards,
    Eve Wang

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

    Thursday, July 4, 2019 6:59 AM
  • Thanks Eve.

    I had installed Hyper-V Server 2009 on a physical computer.

    I had installed from the .ISO.

    I can see if there's a UserVoice for this; at the same time, please can you escalate?


    Thursday, July 4, 2019 8:34 AM
  • Have created a UserVoice request;


    [I know you suggested a documentation edit, but this feels more fundamental than a typo...]

    Thursday, July 4, 2019 8:40 AM
  • It's not only a documentation modification what I meant, it's more to check that the content provided is actually true or not.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, July 4, 2019 8:44 AM
  • Team,

    I have the same trouble.

    Could you help to solve this RD virtualization host role service installation failure, please?

    Steps I've done:

    I work in our test/trial server Dell Power Edge Server, 62GB and 2 TB Mem all Microsoft technology driven, ISO Window Server 2019-DC, License as part of the Microsoft Partners benefits.  All related features to RDA Connection broker are installed as expected, EXCEPT the RD Virtualization Host role.  It failed tree times.

    I did re-install Windows server 2019 DC twice.  Including waiting for updates,  delete and re-datafill Active Directory, OUs, RDAdmin access as well as as a normal general administrator, etc.

    I did apply the following guide lines for similar issue:

    If WID(Windows Internal Database) has been installed:
    1. Open Run, type “services.msc” and end with enter., 
    2. Find service Windows Internal Database, open its Properties – Log On, make sure it has been configured with “Local system account”.
    3. Save the change and re-start the service, try to install RD CB again.
    If problem persists, please try:
    1. Uninstall the Windows Internal Database. 
    2. Rename the old WID (C:\Windows\) to WID_old.
    3. Try to install RDCB again to check the result. 

    I did reinstall RDCB two times from 'zero' Windows Server 2019, Active Directory, setting etc.

    I used an RDSAdmin account to access as a RDAdmin for only RDCB and RD Virtualization host.  

    It does not work, at least for me.      The irony is that it works in VMWare virtualization with Windows Server 2019 DC and its does not work in a pure Microsoft driven fabric structure.

    Is there any work around? or, it there a consistent INSTALLATION PROCEDURES technical document?  The Microsoft documents I found and read are very speculative in theory.  If there is a site for System Engineering Operations/for/in production documents, could you please let me know?

    Thank you,


    Monday, September 9, 2019 11:25 PM
  • I see this is quite an old post, I had exactly the same issue, I was however doing nested VM's in both MS HyperV and VMware, so three places I needed to check....

    Following these three option solved this issue I was having.

    • In physical server bios make sure "enable virtualization" is enabled
    • and on VMware (also while the VM is off) inside the ESX management tool (either vCenter or directly to the ESXi host) enable "Expose hardware assisted virtualization to the guest OS" on the CPU
    • on HyperV host (with the targeted VM off)...run Set-VMProcessor -VMName <vmname> -ExposeVirtualizationExtensions $true

    Thursday, March 19, 2020 11:52 AM