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.
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.
I get the error without any of the GPOs you mentioned applied
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.
Thank you for this. This really helped. As you suggested, I disabled the policy associated with Licensing below, deleted the collection and recreated the collection with success (no error now).
•Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
I had originally configured the above (enabled “Use the specified Remote Desktop license servers” and “Set the Remote Desktop licensing mode”) in order to active my RD CAL licensing. So, if I re-enable these two parameters now, will that impact my collections now that it has been successfully created? Otherwise, my third-party app using the RDS will have issues because it isn’t licensed, correct?
I’m having the same question … I changed the OU computer and I was able to create a collection in trouble. However now I need to move the computer back to a correct OU as I need the licensing to be OK. In this case I will not have problems?
Hi, i was wondering how this worked out for you as i am on the same boat now.
Something messed up .Net permissions on a relatively new Server 2019 VM requiring me to reinstall IIS. This broke RDWeb. I was having the same issue and your suggestion worked. I disabled the policies and was able to successfully install. Thank you!
I had a similar issue when trying to uninstall then reinstall RD services on 2016. When I tried to reinstall I got an error relating to group policies but when I checked, there were none that related to remote desktop being applied.
I was able to fix it by deleting the whole HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\QuickSessionCollection key.
It really helped me and saved my whole night.
Thanks a lot Miles
You saved my day! Thanks a lot!
God bless you bro! You saved my day, thank you so much!
This worked Perfectly Nice big Green Checkmark now going to redoo all my Collections they seeem buggy and ill bet this was why.
Thank You
Argh, I wish the installer could set these required reg keys as part of the install, or even detect this before the install as a prerequisite. It’d be nice if you also didn’t have to recreate the collections.
Thanks for the workarounds 🙂
Argh, I thought this was fixed, now I’m getting “Unable to create the session collection.”. I’ll post a follow up if I find a fix for that.
Googled my issue ‘unable to configure the rdsession host server’ and came here.
What I then did, following the gist of what is written here, is to move the session host server to a new OU where no policies get applied (block inheritance!), then reboot the server just to be sure. Then I removed the session host from the session collection, and added it back. No error messages at all, success. I can now go to my gateway with the browser, select an application from the collection, and it runs on the new server.
Thanks!
In my case no GPO was configured as suggested by MS KB, it was just some leftover after decomissioning RD License Server. Looks like the Server Manager’s remove role didn’t removed the role correctly, so I had to delete HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\LicenseServers registry key manually!
that key does not exists in windows server 2012 R2.
Deleting all registry DWORDs from the following location fix it for me:
Server: Windows Server 2016
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
The main dword that I believe it was is LicensingMode
Thanks for the tip, saved me quite some time.
for me Server: Windows Server 2019
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
Delete all \Terminal Services folder (KEY)
For me, what worked was this: On all session hosts, delete only the key which specifies the RDS license servers. Create the collection again… worked! (it does give some yellow warning about some two other keys, but succeeds in creating the collection)
License Key comes back after some time because of domain level GPO; that is ok. Collection keeps on working.