Answer the question
In order to leave comments, you need to log in
How to set up a remote desktop server correctly?
Hello!
There is a network in which AD is lifted.
You need to add a server to this network, the functionality of which will be to connect users to it from AD via rdp. Everyone has their own account (from AD), their own desktop, and so on.
I'm a little slow in this, so I don't even know how to google. I don’t ask for a detailed guide, at least push it in the right direction :))
Answer the question
In order to leave comments, you need to log in
1. Enter the server into the domain
2. You will need to add the "Remote Desktop Services" roles in the server manager, you can literally walk through the wizard.
3. After adding Remote Desktop Services, by default, only 2 LOCAL administrators will be able to work with you at the same time. Accordingly, you will need to activate the "RDS CAL" licenses in the "Control Panel / Administration / Remote Desktop Services"; they must correspond to the number of maximum connected users to the terminal server at the same time. These licenses are respectively purchased and licensed separately from Windows Server itself. When buying licenses, please note that you will need to choose "per user" or "per device"
4. Next, I advise you to configure (although I have not yet configured it myself because of the not very great flexibility of this mechanism) disabling users who closed the RDS session, but did not complete it, leaving running programs inside the session. Using the same scheme, you can end inactive sessions, that is, those sessions that are not disabled, but the user does not use it for a long time, for example, he left for 2-3 hours leaving the RDS session window open.
5. Next, install the software on the terminal server accordingly. Please note that any software from Microsoft, if it is not of the "Corporate" level, when you see that you install it on a Windows terminal server, it will give an error and will not allow it to be used due to license restrictions. Accordingly, you need to buy separate software packages that are designed specifically for use on a terminal server. An example of such software is MS Office. I stumbled on this point in due time and killed a lot of time to understand why the same MS Office Prof does not work on my terminal server. I didn't want to buy Corp so I replaced it with LIbreOffice.
something like this https://4admin.info/terminal-user-access/
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question