RDS 2019 issues related with to much services

[KrzysztofSek]

Hello All,

I have installed new RDS server on latest 2019 standard server. This is standalone RDS server. Server is used by more than 100 people and has enough resources and licenses etc... Users can connect to one RDS web app published on the server without any problems. Everything looks fine till time when i want to check few things on the server.

I can't open services mmc, because i'm receiving error message: "Error 1783: The stub received bad data":

Same from powershell. Result of Get-Service is empty.

Solution is here:

https://docs.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/error-1783...

Completely not acceptable for me, but i think above issue is correlated with: "Per-user services in Windows 10 and Windows Server":

https://docs.microsoft.com/en-us/windows/application-management/per-user-services-in-windows

So if one user can create few services, how much services will be if on server will be more than 100. 

I can't open also Remote Desktop Services Overview from server manager:

Next issue is related with monitoring system which can't get some data from this server. 

Everything is comming back to normal if server is not used but to much of people at the evening for example, because when RDS session is disconnected then per user services also are removed. Then everything described above is working correctly.

So my question is what is the solution for this case, because i as administrator can't provide good quality of the RDS service, because i don't see many things described above. Probably is much more.

[#2]

@KrzysztofSek 

I have this problem too. 

Solution is here:

https://docs.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/error-1783...

---

That solution doesn't help. I think you are right about per-user services: it is still possible to monitor services by "sc query" or windows admin center and in my case it is over 300 services created when user logs in. Something like CDPUserSvc_*****. 

Maybe this can help for a very temporary solution? 

@echo off

goto main

:clsvc

FOR /F "tokens=1,2 delims= " %%A IN ('SC QUERY state^= all ^| find "%SN_STARTS_WITH%"') DO (@echo %%B && net stop %%B && SC delete %%B)
EXIT /B

:main
SET SN_STARTS_WITH=WpnUserService_
call :clsvc
SET SN_STARTS_WITH=DevicePickerUserSvc_
call :clsvc
SET SN_STARTS_WITH=DevicesFlowUserSvc_
call :clsvc
SET SN_STARTS_WITH=ConsentUxUserSvc_
call :clsvc
SET SN_STARTS_WITH=PimIndexMaintenanceSvc_
call :clsvc
SET SN_STARTS_WITH=CDPUserSvc_
call :clsvc

[#3]

Unfortunately this is not a solution form me. My monitoring system is not working, because can't get status of services if some limit is reached described in article about per user services. I also found that "WMI Service provider" is getting a lot of CPU if Vmware Tools service is started:

And in my opinion it is also related with to much per user services created. 

I also received some tip that I should clean boot server. I can answer that this is not a solution. Problem is related by system which is creating many many of per user services.

So Microsoft what is the solution? When you will repair this case?