This configuration should be used only when it is the only option. This is because the recommended configuration includes the Remote Desktop Connection Broker to provide access to the complete functionality with Remote Desktop Services. If a Domain Controller (DC) is available on a separate server, we recommend that you use the Standard Remote Desktop Services deployment wizard. This configuration is appropriate when there is only one server on the network. This server can be part of a workgroup or may be configured as a DC.
This configuration provides desktop sessions to users based on the number of Remote Desktop Services client access license (RDS CALs) installed on the server. However, it does not provide access to RemoteApp programs or the RDWeb site.
The deployment of a Remote Desktop Session Host role service without the Remote Desktop Connection Broker role service adds certain requirements and considerations. Unless otherwise noted, these steps apply to both Workgroup and Domain Controller cases:
- If the system has to be configured as a Domain Controller, install the Active Directory Domain Service (AD DS) role service on the Server and promote as Domain Controller
For more information about how to install AD DS in Windows Server 2012, go to the following Microsoft webpage:
- Install the Remote Desktop Licensing and the Remote Desktop Session Host role services using the following steps:
- Open Server Manager.
- Click Manage and select Add Roles and Features.
- Select Role-based or Feature-based installation.
- Under Remote Desktop Services, select Remote Desktop Licensing and Remote Desktop Session Host role services.
- Continue the installation.
- Add the License Server to Terminal Server License Servers group, and then restart the Remote Desktop service. To do this, you have the following options:
- Add the server to Terminal Server License Servers group by opening licmgr.exe and selecting the Review link.
- Manually add the server to Terminal Server License Servers group. (On DC. this will be in Built-in groups.)
- Activate the License Server automatically from License Server UI (licmgr.exe).
For more information about how to activate the Remote Desktop License server:
- Install appropriate RDSCALs.
For more information about how to install RDS CALs, go to the following Microsoft webpage:
- If the system is a Domain Controller, add the Domain Users group (or the specific list of users) to the Allow logon through Remote Desktop Services local group policy. To change the local group policy object setting, follow these steps:
- Open GPEDIT.MSC.
- Expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then click User Rights Assignment.
- Double-click Allow log on through Remote Desktop Services and then click Add User or Group.
- Type the user account, and then click OK two times.
- Close the Group Policy Object Editor.
- Add the users you want to allow to connect to the Remote Desktop Users group. For example, add Domain Users. (On DC, this will be in Built in groups.)
- Configure the Remote Desktop Session Host role to use the local Remote Desktop Licensing server. To do this, follow these steps:
- Open an elevated Windows PowerShell Command Prompt window.
- Type the following command on the PS prompt, and then press Enter:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
- Run the following command to set the licensing mode.
Note Value = 2 for per device, Value = 4 for per user.
- Run the following command to replace the machine name with License Server:
- Run the following command to verify the settings that are configured using previous steps:
You should see the server name in the output.
Note If the system is a Domain Controller, an additional step must be taken to allow printer redirection to function properly. For more information, click the following article number to see the article in the Microsoft Knowledge Base:
Article ID: 2833839 - Last Review: Apr 10, 2017 - Revision: 2