Multiple terminal servers setup
I'm looking to replace my old (like really old 2k8 r2) terminal server with 3 new ones (win2k5). Instead of each department going to one server as it is now, I would like to break up the departments to a specific server. For example. HR and Fiscal go to server 1, C suites go to server 2, etc. How can this easily be achieved? Can I give them all the same virtual server name, group the servers together, and terminal knows which one to go to based on the users group or do I have to make 3 individual servers and tell each division to go to server1 or server2? I've thought about just grouping them together, having roaming profiles and allowing terminal to pick the server based on load but, I don't want to have to fight the terminal server vs their desktop computer when they are in the office. Not to mention the amount of storage needed for all of the profiles. Any help or suggestions would be appreciated.
Custom resolution on Android Remote Desktop app only offers fixed ratios connected to device screen
I have two Android devices using nonstandard monitor display ratios (21:9, 5:3). I have previously set up profiles on one of these devices with a 16:9 ratio resolution that matches my remote session's actual physical display. This prevents a number of strange resizing issues when switching between a local and remote session. However, in the current latest (beta) version, 10.0.13.1167, I'm now limited to resolutions matching the device's ratio. Is there a way to change this to allow for picking a ratio, or at least revert to the previous functionality? If this is the wrong place for this, I apologize. I was linked here from a Remote Desktop support page, and couldn't find a better place via searching.W2K19 server - remoteapps issue
Hello everyone, I got a good for you all... We have one windows 10 v1909 workstation that is unable to connect back into remoteapps after the user logs off the workstation. It will work on the first login to the workstation, once the user logs off it is unable to connect back again. Nor is it able to remote desktop to the server (it is able to remote desktop to any other server in the office). We can get an "internal error has occured" msg . No other workstations in the office is having this issue. We have enough TS licenses in license manager with an extra 4 licenses to spare. We've disconnected the TS sessions, checked the event logs (which shows authentication is successful for that workstation), restarted remote deskop services on the server. The only fix we have now is to reboot the server. Then the workstation is able to connect until the user logs off from it. (which we informed then to not to at the moment) When it is working, we can close out of remote apps, go back into it without an issue. Also Installed the latest updates on the windows 10 - didnt help. Unfortunately we do not have a windows restore point to fall back on. I included a screenshot of the error. Any help is appreciated. thanks, Chargr
The RD Connection Broker server is not available or the relevant services are not running
Hello, I have installed Windows Server 2016 STD with Session Host, Connection Broker on one server (AD domian joined). There is no problem when i have connected less than ~200 user. When i have more than ~200 users when i try to check "shadow session" i have error "The RD Connection Broker server is not available or the relevant services are not running". When i try to open services.msc i have error: "The system encountered the following error while reading the list of services on: Error 1783: The stub received bad data" When i try to open event viewer i have error: "Event Viewer cannot open the event log or custom view. Verify that Event Log service is running or query is too long. The RPC server is too busy to complete this opertion (1723)"