In the section “Remote Desktop License servers” you can add or remove the RDL servers to be used by the RDSH. This dialog box lets you configure general Remote Desktop Services (RDS) settings and the Licensing tab targets licensing settings of course. Double click something under the “Licensing” section with the left mouse button and the dialog box “Properties” pops up, immediately in the tab “Licensing”. The window “Remote Desktop Session Host Configuration” opens.
But who am I, right? ?Īnyway, one way to configure the RDL server(s) on an RDSH is the graphical way: go to the Start menu on the RDSH, then to the menu “Administrative Tools” (if your Start menu is configured to show this menu if not, open Administrative Tools through Control Panel), then the submenu “Remote Desktop Services” and finally select “Remote Desktop Session Host Configuration”. On the other hand, automatic discovery is easy: no configuration work at all! IMO a mix of both would have been the best of both worlds actually: if it doesn’t matter, use automatic discovery and if it does, configure the RDL server(s) explicitly. With automatic discovery this would be very difficult and/or error-prone to achieve, as RDSH A could discover RDL server 2 and RDSH B could find RDL server 1 even more, this could change over time: one moment RDSH A would use RDL server 1, but later it could use RDL server 2 after a new discovery. RDSH A will never use RDL server 2, while RDSH B will never use RDL server 1. This is easily achieved by configuring RDL server 1 as the licensing server on RDSH A and RDSL server 2 as the licensing server on RDSH B. For example, suppose you have 2 RDSHs (A and B) and 2 RDL servers (1 and 2) and you want RDSH A to use RDL server 1 and RDSH B to use RDL server 2. This way it’s much easier to determine which RDSHs should use which RDL servers. How can an RDSH know which system to use as its licensing server? Well, in the past Terminal Server (TS), the predecessor of RDSH, could discover such a licensing server automatically, but now an RDSH must be configured explicitly to use a set of licensing servers. Now, let’s assume every RDSH needs such an RDL server. If you are a cheater, don’t care about user friendliness, don’t need to have more than 2 users access the system at the same time, let your users be administrator on the system (except when you configure the system so normal users can use administrative sessions) and don’t need or care about the restrictions, well, OK, than you have an exceptional situation where you don’t need that license server. Some things can’t be achieved during such a session.By default administrative sessions are only possible for administrator accounts, but not for normal user accounts.Only 2 concurrent administrative sessions are allowed on a certain system, so in almost every case this limit is way too restrictive J.That’s not a user friendly way, isn’t it?.
You can get an administrative session by starting Remote Desktop Connection (RDC mstsc.exe) with the admin switch, so just like this:ĭo not try to give your users access through administrative sessions, because An administrative session is a session for administrative purposes and doesn’t require a license. One exception is when you only use administrative sessions on your RDSHs, but there are not many scenarios out there where you need to set up RDSHs for administrative sessions only. When you use Remote Desktop Session Hosts (RDSHs) you need a Remote Desktop Licensing (RDL) server to take care of licensing needs. What you should know about Remote Desktop Licensing first
Note this is not a complete manual though, it just explains the things you should know before discussing the actual issue. But let’s start with some background information first, just to be sure you have the necessary knowledge about this topic.
This article explains what happened and how to fix the issue. attributes of an AD user can’t be updated by the licensing server. This event is talking about a problem, i.e. It seems in some scenarios users accessing a Remote Desktop Session Host (RDSH) don’t get a license from a Remote Desktop Licensing (RDL) server and an even ID 4105 is logged on the RDL server.
Remote Desktop Licensing server can’t update attributes of AD user