Setup: Virtualization Host - Physical Dell PowerEdge R540 w 192gb RAM, 2x Xeon procs (cant remember the model, 16 cores total) running Win Server 2016 + Hyper-V Service RD Gateway, RD Broker, RD Web Access, RD Licencing - One VM running on the Virtualization Host. Windows Server 2016, 16gb RAM, 4CPU cores.
Right now I have only have 10 Windows 10 VMs spun up.
Problem #1: At seemingly random intervals, users are unable to connect to their VM via their physical Wyse thin client terminal. After logging in, the client contacts the broker, attempts to sign into the machine and then says "RD Failed". After rebooting the broker server things go back to normal for a few hours, then the "RD Failed" messages return again.
The weird thing: everything works fine if they try to connect from RD Web Access.
Problem #2: Again, at seemingly random intervals, users are receiving messages when logging into their terminals saying: "The requested session access is denied."
The weird thing: this is only sometimes, and usually goes away if they either a) leave the error message on their screen or b) exit and try again.
I'm honestly not sure where to go from here. I thought it could be a policy or permission issue but it only does it sometimes?
Event Viewer messages collected when experiencing problem #1:
The user "DOMAIN\USER", on client computer "10.10.12.41", met connection authorization policy and resource authorization policy requirements, but could not connect to resource "COMPUTERNAME.DOMAIN.COM". Connection protocol used: "HTTP". The following error occurred: "23005".
The user "DOMAIN\USER", on client computer "192.168.4.231", met RD resource authorization policy (RD RAP) requirements but the network resource "10.25.20.197;10.25.20.197" did not meet the requirements, so the connection was not authorized. Try connection to another network resource or possibly lower RD Gateway security by modifying the RD RAP requirements for the connection to be authorized.
RD Connection Broker failed to process the connection request for user DOMAIN\USER. Error: Element not found.
RD Connection Broker failed to process the connection request for user DOMAIN\USER. Load Balancing failed OR Specified endpoint could not be found. Error: Element not found.
Again, after a reboot of the broker/gateway server, everything is back to normal for a few hours.
I'm so lost.