Configure the Windows R2 Remote Desktop Services in a workgroup environment

Configure the Windows R2 Remote Desktop Services in a workgroup environment
How to configure Remote Desktop Service in Windows R2 workgroup

Today there is a need to configure a Windows R2 Terminal Server, but in a workgroup. Originally thought that there is no problem, the most configuration interface is difficult to find some. (The Windows 2012 start of Terminal Services/Remote Desktop Services Administration interface and previous versions of Windows differ enormously.) The result was a lot of trouble.
After installing the server role, including Remote Desktop Session host and Remote Desktop licensing, you need to configure the server's license mode, per user or Per device. Try to configure the server management interface, the result came to a need for a domain environment, immediately feel good trouble. It appears that you need to configure it with PowerShell.


First change the licensing mode, and then install the authorization, according to the previous experience (2003 times) Terminal Server can discover its own licensing services. To find this article, you can use Set-rdlicenseconfiguration–mode peruser to change it.
Powershell:managing RDS Licensing on Windows Server 2012
https://social.technet.microsoft.com/wiki/contents/articles/13293. Powershell-managing-rds-licensing-on-windows-server-2012.aspx
The result cannot be set. Tip There is no deployment for Remote Desktop services.

Next, find out how to configure Terminal Services using PowerShell. So I found this article.
Using PowerShell to control RDS in Windows Server 1
http://techgenix.com/using-powershell-control-rds-windows-server-2012/
Look like, use the new-rdsessiondeployment to create, the result is still unable to connect (the figure uses the localhost is just an example, using the real FQDN and shutting down the firewall on the local run or the same cannot connect)

At this time, it seems that the problem is not so simple. The workgroup environment does not look that simple. The search is ongoing on the web, but few searches can be found on how to configure the workgroup environment. But the heart still feel that Microsoft can not say that must be the domain to use Terminal Services, otherwise it is too dark. Find an article, also talk about a lot of how to deploy the method, how to find a place to set up. Although the UI can be deployed in a domain, it is particularly difficult to find. After a closer look at the second time, it was found that there was a using Group Policy.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/ebc032e2-ab2d-4acd-aef7-28ed548be569/ How-to-set-up-remote-desktop-licensing-mode-in-windows-server-2012?forum=winserverts

Then, open the Group Policy Editor to find computer configuraion-administrative templates-windows components-remote Desktop services-remote Desktop Session host-licensing, which has two strategies: use the specified Remote Desktop license servers, Set the Remote Desktop Licensing Mode Through these two policies, I finally completed the authorization mode setting and specifying the authorization server I needed. The final diagnosis results are as follows:

Usually, I didn ' t use 中文版 to write my blog. But this time I think it was necessary to does that. Wish It can help more people.
How to configure Remote Desktop Service in Windows R2 workgroup
You'll be unable to configure Remote Desktop service in Windows-R2 workgroup neither in Windows GUI nor PowerShell. Use the Group Policy to configure it. Here is the settings computer configuraion-administrative templates-windows components-remote Desktop services-remote Desktop Session Host.

Configure the Windows R2 Remote Desktop Services in a workgroup environment