Server 2019 and 2022 Remote Desktop Services installation fails: MultiPointServerRole missing

steven h 101 Reputation points
2021-10-19T13:40:17.86+00:00

Hi everyone,

I've just performed a clean installation of Windows Server 2022 and 2019 Standard (fully up to date) and not having changed anything else, I just tried to perform a Remote Desktop Services installation (server manager > add roles and features > remote desktop services installation) but the installation fails with the following error:

Failed:  
Unable to install the role services. ArgumentNotValid: The role, role service, or feature name is not valid: 'MultiPointServerRole'. The name was not found.  

As far as I can tell, MultiPointServerRole is A) not installed on Server Core, but I'm not using that (I checked HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Installation Type and B) MultiPoint Services are no longer actively developed.

Especially point B makes it odd to see that MultiPointServerRole is a hard requirement to be able to use the RDS Installation option.

Could anyone point me to the right direction as to how I can solve this? Is this even intended behaviour?

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments No comments
{count} votes

Accepted answer
  1. steven h 101 Reputation points
    2021-10-20T08:41:20.78+00:00

    I managed to solve the issue: apparently in (somewhat) recent time Microsoft has made the configuration of an AD an unavoidable requirement when using the RDS Installation option.

    The quick start option will clearly tell you that an AD is required when you want to take that route. The standard option doesn't and fails with the cryptic error from my original post. Once you do configure the server as a domain controller, you're good to go however without any issues.

    An odd design decision considering the RDS Installation Quick Start option is aimed at test labs and small environments. Not to mention that the MultiPointServiceRole is no longer actively developed. I expect this RDS Installation behaviour will be changed in the future.

    Another reason this is a weird design decision: installing all RDS roles on your domain controller is against best practice standards. So this recent design decision by Microsoft either brings additional and somewhat unnecessary resource requirements to a single server, or requires you to add an additional server as domain controller (and if you like connection broker), depending on your choices. Very odd as this negatively impacts small environments... still, I'll consider this issue resolved.

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Nick t0nZ 11 Reputation points
    2022-09-07T15:34:05.497+00:00

    I solved WITHOUT ACTIVE DIRECTORY.

    Windows server 2022 here, datacenter edition, fresh install, unique phishical machine in a dedicated Vlan for testing RDP services.

    Installing Remote Desktop Services on Windows Server 2022

    Resolved in this mode:
    installed the new web based "Windows Admin Center"

    after used to install the role directly.


    now Windows warning about the license of RDP expiring in 120 days, so we have to:
    "Install RDS client access licenses"
    https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-install-cals?source=recommendations

    we have first to activate, and after entering licenses.
    (retail licenses, USER CAL , not device CAL)

    Done, you can now add local userS, adding to Remote Desktop Users Group, and let users connecting !

    2 people found this answer helpful.

  2. Anonymous
    2021-10-19T14:12:15.233+00:00

    Afraid the MultiPointServerRole died with Server 2016 and is no longer available in Server 2019

    --please don't forget to upvote and Accept as answer if the reply is helpful--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.