Also - I noticed that under Best Practices Analyzer I see: Error > The IIS service must be running on the RD Web Access Server (which is this one, even though it isn't used) and IIS won't start.
RDS Issue (2016 Server) There are no available computers in the pool
I can't seem to find a resolution here or elsewhere on the web. Whenever using MSTSC (without /admin), I will get error messages in the TerminalServices-SessionBroker-Client that are: 1301, then 1296, then 1306. Seems to be some sort of redirection error.
- [EventID: 1301] Remote Desktop Connection Broker Client received request for redirection. User: {domain\me}. RDP Client Version: 5
- [EventID: 1296] Remote Desktop Connection Broker Client failed when getting redirection packet from Connection Broker. User: {domain\me}. Error: Element Not Found
- [EventID: 1306] Remote Desktop Connection Broker Client failed to redirect the user {domain\me}. Error: NULL
I have tested licensing - they are set per user with 11 available (per the Licensing Diagnoser)
I used Roles and Services to set up the configuration again after removing the Host Server and Collection. Then set it up again with a new collection and a new host server (and set up licensing at per user). Even after this - I am still getting the errors mentioned above :(
I am pretty much stuck here until I figure it out, but I'm totally lost at this point :( I keep googling, but not finding anything worthwhile yet.
EDIT also - I have looked in the SQL Server database for configuration and I don't really see a lot wrong in the RDCms database, but admittedly I'm not 100% sure what to look for.
2 answers
Sort by: Most helpful
-
-
Andrew Mueller 6 Reputation points
2023-01-11T15:04:22.1166667+00:00 I got RDWeb Access going, had to re-install IIS and set it up again. Not a huge deal. I cannot publish apps to it, though. They show published, but do not show up.
Still the same issue when trying to RDP :( MSTSC.exe /admin works, of course, but that isn't going through the broker as far as I am aware.