You will need to add the RDS Role.
https://msfreaks.wordpress.com/2018/10/06/step-by-step-windows-2019-remote-desktop-services-using-th...
If you've never done this before I suggest a bit of research as there are many options available.
Spice (1) flagReport
1 found this helpful thumb_up thumb_down
Also, be careful about CALs. Are the server shares being accessed by the 11 people you mentioned? If so, you need 11 User CALs.Unless you already have 2019 Server User CALs for your network? Server User CALs are per network, not per server.
Spice (1) flagReport
Was this post helpful? thumb_up thumb_down
You can use server manager to deploy the RDS server role to your server. There are a lot of options, so I would recommend taking a look at this guide as to how to set it up properly. https://www.slashadmin.co.uk/how-to-setup-a-single-server-rds-deployment-using-server-2016/
Ideally you would have separate servers for all of the roles, but in a small business it is very normal to have a server that handles multiple roles. Just be aware of the fact that you do introduce some possible security / usability issues in doing so. For instance, if you need to reboot the RDS Session Host because it needs an update, that is one thing/ But when it is also a file or application server, you cause more interruptions in service.
As far as the licensing goes, during the setup you will setup a license server (again, will be on the same host since you are doing a single server deployment), and will place your RDS CAL packs in there. They get automatically assigned to whoever connects (if User CALs) or what device connects (if Device CALs).
Hope that helps.
Also, DragonsRule is correct. You only need enough RDS CALs for whoever is connecting via Remote Desktop, but if you are using any type of server service, every user needs a Server User CAL. These aren't assigned anywhere, but they are needed in order to maintain proper licensing, if you have users accessing servers in a Windows environment.
It should also be pointed out that if you don't have an Active Directory domain and are in a Workgroup, there are specific instructions on how to install/configure RDS. Most how-to's assume you are in an AD domain.
Spice (3) flagReport
2 found this helpful thumb_up thumb_down
The file share is a single folder on the server that they access. Currently there have not been any problem with multiple people accessing the shared folder.
What are the requirements for RDS role? Do you need AD or a DC? Neither of these are setup on the server. Being a small business we only have the one server.
spicehead-kbwar wrote:
The file share is a single folder on the server that they access. Currently there have not been any problem with multiple people accessing the shared folder.
Licensing is a legal issue, not a technical one. If more than 5 people are accessing the server you need CALs for them all to remain legally compliant.
spicehead-kbwar wrote:
What are the requirements for RDS role? Do you need AD or a DC? Neither of these are setup on the server. Being a small business we only have the one server.
Ok.. so this is the only Windows Server at the location? You can setup RDS without a Domain, but it's a PITA. And the RDS Licenses you purchased may not be valid - did you get RDS User or RDS Device CALs?
Da_Schmoo, we are setup in a workgroup and not in an AD domain. Where can I find the specific instructions on how to install/configure RDS for a workgroup?
spicehead-kbwar wrote:
Da_Schmoo, we are setup in a workgroup and not in an AD domain. Where can I find the specific instructions on how to install/configure RDS for a workgroup?
This one looks good. The issue is the RDS install/configure tool requires an AD account to do what it needs to do and many things are configured in Group Policy which you don't have. In a Workgroup environment you have to do a bunch of things manually like make these changes yourself in the local policies. You also have to use RDS Device CALs, not RDS User CALs but 2019 allows you to convert them after they are installed so no worries there.
Spice (3) flagReport
2 found this helpful thumb_up thumb_down
I have 5 user CALs and 5 RDS User CALs. It is the only server for the company.
spicehead-kbwar wrote:
I have 5 user CALs and 5 RDS User CALs. It is the only server for the company.
You said you have 11 users. You need 11 Server User CALs to be legally compliant.
Spice (3) flagReport
1 found this helpful thumb_up thumb_down
You do not have to setup an entire RDS to do this. The following Powershell will enable the feature. You need to have a License server if you don't already, but it can be the same server if needed.
$obj = Get-WmiObject -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
# Set Machine to Per User TS Licensing
$obj.ChangeMode(4)
# Set Licensing Server
$obj.SetSpecifiedLicenseServerList("<FQDN of License Server>")
# Check Current Settings
$obj.GetSpecifiedLicenseServerList()
* This is assuming you have the correct licensing.
I got it working with the instructions Da_Schmoo linked to. The only issue I have is that the connections are coming across as temp connections and not using the 5 cals I have added to the server. I have attached what I am seeing when I look at the license server.
attach_file Attachment RDLicense.jpg 30.4 KB
That usually indicates you don't have the licensing server defined correctly in the Deployment Properties. People have reported sometimes that doesn't work and you have to define in in Group Policy. Since you don't have AD, it's possible you may have to define it in the local policies - not sure as I've never set this up in a workgroup environment.
Your picture shows 2019 per device temp license, but your paid license is 2016. What version are you running? If you have 2019 servers and only have a license for 2016, or installed them as 2016 you will see this.
DrownEnt wrote:
Your picture shows 2019 per device temp license, but your paid license is 2016. What version are you running? If you have 2019 servers and only have a license for 2016, or installed them as 2016 you will see this.
Good catch!
I am running a 2019 server. The license I received with the server were 2016 Cals. Do I have to get them changed to 2019? I thought whether they were 2016 or 2019 they would work. Guess I was wrong.
Your RDS Server has to be the same level as your CALs. Your licensing server has to be the same level of the RDS Server or higher.
Spice (1) flagReport
1 found this helpful thumb_up thumb_down
Is there a way to convert the 2016 licenses to 2019? Or should I contact the manufacturer who sold me the licenses and try to exchange them?
spicehead-kbwar wrote:
Is there a way to convert the 2016 licenses to 2019? Or should I contact the manufacturer who sold me the licenses and try to exchange them?
No, you can't convert them. MS expects you to purchase the proper licenses.Maybe the place that sold them to you will be willing to exchange them. Good luck.
Thanks for the help. Considering we got them from Dell with the $5000.00 Dell server I am hoping they will make it right.
If it was on the same order as the server I'd push them to make it right. The salesman should have caught that or at least question it. Push hard.
Spice (1) flagReport
Was this post helpful? thumb_up thumb_down
Speaking of... Are your User CALs the right version?
I currently don't have any user cals. I had 5 RD User Cals that I converted to device cals. I am in the process of getting enough cals to cover all the users accessing the server. I will make sure they are all 2019 cals.
spicehead-kbwar wrote:
I currently don't have any user cals. I had 5 RD User Cals that I converted to device cals. I am in the process of getting enough cals to cover all the users accessing the server. I will make sure they are all 2019 cals.
User or Device, they still need to be 2019, not 2016.
