>

RDS Collection error: Unable to configure the RD Sessionhost server. Invalid operation

When trying to create a new Remote Desktop Session Collection you receive an error: Unable to configure the RD Sessionhost server servername.domain.local. Invalid operation.

rds collection error

The collection it self is created but not completly, some parts are missing, like there is no Desktop icon on the Webaccess page. And probably some other settings aren’t set correctly. So it would be wise to solve the problem, delete the old and create a new collection.

Solution:
Described in this kb kb3014614 article it is a know issue, some policies are already applied to the RD Session Host server. To solve the issue make sure there are no policies set to the new RD Session Host server especially these two gpo strings:

  • Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Security
  • Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing

In most cases this would be the case when there is already an existing Remote Desktop server and policies are applied via a group policy to a specific OU and the new server is already moved to this OU.

Move the new Remote Desktop server to another OU where no policies are applied. Run gpupdate /force or reboot the new RDSH server. Then delete the existing collection and create a new collection.

If you already set local policies on the RD Sesions Host policy these also need to be removed.

Posted in Remote Desktop, Windows Server 2012 R2 by ronnypot at February 24th, 2016.

2 Responses to “RDS Collection error: Unable to configure the RD Sessionhost server. Invalid operation”

  1. yaro says:

    I get the error without any of the GPOs you mentioned applied

  2. Randy Fleszar says:

    Hello,

    I came across this error while upgrading my domain controller to Server 2016. I previously set up a RD server and had GPOs applied. I also had local GPOs configured.

    I started troubleshooting by removing the RD server from any OUs with GPOs, but this didn’t work. I had to run gpedit.msc on the local RDS server and edit the settings there also.

    Once I modified both the Domain GPO and the Local GPO, the Wizard completed successfully.

    Your post should elaborate on this last comment.
    “If you already set local policies on the RD Sesions Host policy these also need to be removed.” If you are not a Windows GPO expert, you may not know that the local GPO has to be checked in addition to the Domain GPO.

Leave a Reply

Sharing Buttons by Linksku