This article provides the guidelines to install and configure the Remote Desktop Session Host role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service installed.
This configuration should only be used when it is the only option as the recommended configuration includes the Remote Desktop Connection Broker to provide access to the complete functionality with Remote Desktop Services. If a Domain Controller is available on a separate server, it is recommended to 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 Domain Controller.
This configuration, will provide desktop sessions to users based on the number of Remote Desktop Services client access license (RDS CALs) installed on the server, but will not provide access to RemoteApp programs or the RDWeb site.
Consideration for installing the Remote Desktop Session Host role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service.
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, the steps apply to both Workgroup and Domain Controller cases:
- If the system needs 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 on how to install AD DS in Windows Server 2012, Visit the following Microsoft Web page:
- Install the Remote Desktop Licensing and the Remote Desktop Session Host role services using the following steps:
- Open Server Manager
- Click on Manage and select Add Roles and Features
- Select Role-based or Feature-based installation
- Under Remote Desktop Services, choose Remote Desktop Licensing and Remote Desktop Session Host role services.
- Proceed with installation
- Add the License Server to Terminal Server License Servers group and restart the Remote Desktop service
- You can add the server to Terminal Server License Servers group by opening licmgr.exe and select the Review link.
- You can 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 on how to activate the Remote Desktop License server:
- Install appropriate RDSCALs.
For more information on how to install RDS CALs, visit the following Microsoft Web page:
- 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 edit 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, click OK and then click OK
- Close the Group Policy Object Editor.
- Add the users you want to allow to connect to the Remote Desktop Users group.
For example: Domain Users. (On DC this will be in Built in groups)
- Configure the Remote Desktop Session Host role with to use the local Remote Desktop Licensing server. Follow these steps:
- Open an elevated Windows PowerShell prompt
- Type the following command on the PS prompt and 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 above mentioned steps:
You should see the server name in the output.
Users can now initiate Remote Desktop Sessions to the server from any supported RDS client.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:
Terminal Server Easy Print not printing
for other considerations.
Article ID: 2833839 - Last Review: April 11, 2013 - Revision: 1.0
- Windows Server 2012 Foundation
- Windows Server 2012 Standard
- Windows Server 2012 Datacenter
|kbstepbystep kbpolicy KB2833839|