windows server 2012 remote desktop licensing

You should see your RDLI server is already added to the list of License Servers, so you can click OK.įrom the Servers page, right click the server you installed the RDLI role on and select RD Licensing Manager. I tend to see customers using Per User instead of Per Device, but you can pick either one based on your usage scenario. Here you can select the RD Licensing mode (or type). The Confirmation page is pretty bland but click Add.įrom the Tasks menu select Edit Deployment Properties. Select the Connection Broker server and add it to the Selected list. I like to co-locate the Licensing role on the same server that runs the Connection Broker role so I do not need to add any new servers to the manager or the deployment.įrom the Remote Desktop Services section click the “RD Licensing” icon from the Overview page. Open the Server Manger that knows all of your RDS servers.

I’ll assume you’ve already got either one or three servers in place, so we’ll just jump right in. You can read a great step-by-step guide on TechNet on this topic as well.Īssuming you already have an RDS environment in place ( use one of my earlier guides), there are basically four steps to getting your RDLI in place. That said, there are free keys available for the Trial, RC and Beta editions of Windows Server 2012 from Microsoft here. This means you do not need to deploy the RDLI role if you’re just testing things out or want to do a Proof of Concept for a few months. Without this role the RDS environment will function for 120 days in a “grace period” before connections will be refused. Read more Step-by-Step Guides on Remote Desktop Services in Windows Server 2012.Īn important part of really finishing a deployment of Remote Desktop Services is the Licensing role, or “RDLI”.

Windows server 2012 remote desktop licensing