Remote Desktop As A Service

  



Remote desktop services are a form of service that allows user to take control of a remote computer or virtual machine over a network connection. It is used to access an off-site computer and provides the control of other computers online through a single computer or device. A remote desktop service is a system whereby a person is able to connect to and use a specific computer from a remote location as if they were sitting in front of it at the time. The most common example is that of accessing your office computer from the PC or laptop at home, enabling you to manage files, use available resources and generally do.

Last updated on February 27th, 2020

This article contains step by step instructions on how to install and configure the Remote Desktop Services on a Windows Server 2016 or 2012. In Windows Server 2016 & 2012 the Terminal Services role has been replaced by the Remote Desktop Session Host (RDSH) role service and is part of Remote Desktop Services (RDS). A Remote Desktop Session Host (RDSH) server, provides to remote users the ability to access the applications on the RDS host server and the company resources from anywhere by using an RDP client.

In this tutorial you 'll learn how to setup and configure a Windows Server 2016 or 2012 as a Remote Desktop Session Host (Terminal) server, in order to provide remote desktop sessions, based on the number of Remote Desktop Services client access licenses (RDS CALs) installed on the RDSH server.

How to Setup and Configure a Windows Server 2016/2012 as a Remote Desktop Session Host Server (Terminal Server).

Notes:
1. The mentioned steps below, can be applied either on a Domain Controller or in a standalone server 2016/2012.
2. If the Terminal services are installed on a server that will act as a Domain Controller also, then first install the Active Directory Domain Service (AD DS) role service and promote the Server to a Domain Controller, before installing the Remote Desktop Session Host (RDSH) role service (Terminal Service).
3. Keep in mind that the below configuration does provide access to RemoteApp programs or the RDWeb site, because the Remote Desktop Connection Broker role service will not be installed.

Step 1. Install Remote Desktop Services on Server 2016/2012.
Step 2. Activate the Remote Desktop License Server.
Step 3. Install Licenses on the Remote Desktop License Server.
Step 4. Configure RD Session Host role to use the local Remote Desktop Licensing server & Set the Remote Desktop licensing mode.
Step 5. Add RD Clients (Users) to the Remote Desktop Users Group.
Step 6. Allow the log on through remote desktop Services.
Step 1. Install Remote Desktop Licensing and Remote Desktop Session Host role services.

1. Open 'Server Manager' and click on Add Roles and Features.

2. At the first screen of 'Add Roles and Features wizard' leave the Role-based or feature-based installation option and click Next.

3. At the next screen, leave the default option 'Select server from the server pool' and click Next.

4. Select the Remote Desktop Services and click Next.

5. Leave the default settings and click Next at Features and Remote Desktop Services screens.
6. At Role Services screen, select the Remote Desktop Licensing role service and then click Add Features.

7. Then select the Remote Desktop Session Host role service and click Add Features again.

8. When done, click Next to continue.

9. Finally click Install to install the Remote Desktop Services: Remote Desktop Licensing and Remote Desktop Session Host.

10. When the installation is completed close the 'Add Roles and Features Wizard' and restart your server.

Step 2. Activate the Remote Desktop License Server.

1. Simultaneously press the Windows + R keys to open run command box.
2. Type licmgr.exe and press Enter to open the RD Licensing Manager *

* Note: Alternately, you can launch the RD Licensing Manager, from Control Panel –> Administrative Tools –> Remote Desktop Services –> Remote Desktop Licensing Manager.

3. At the right pane, right click on the server name and select Activate Server.

4. Click Next at the Welcome screen and then click Next again at Connection method options.

5. At 'Company Information' window, fill the required fields and click Next twice to activate your License Server.

6. When the activation is completed, leave checked the 'Start Install Licenses Wizard' checkbox and click Next.

7. Continue to next step.

Step 3. Install Licenses on the Remote Desktop License Server.

1. At 'Welcome to the install licenses wizard', click Next

2. On the License Program page, select the appropriate program through which you purchased your RDS CALs, and then click Next.

3. According the License Program you selected on the previous page, type either the license code or the agreement number provided when you purchased your RDS CALs and then click Next.

4. On the Product Version and License Type page, select the appropriate product version, license type, and the quantity of the RDS CALs based on your RDS CAL purchase agreement, and then click Next.

5. When the RDS CALs installed on the server, click Finish. *

TIP: If you cannot activate the RDS Server automatically, then try to activate it using the Web Browser or via Telephone. To do that:

a. Right-click on the Server's name and select Properties.
b. Change the Connection Method to Web Browser or to Telephone.When done, click OK.
c. Finally, right click on the server name, select Activate Server and follow the onscreen instructions to completed the activation.

Step 4. Configure RD Session Host role to use the local Remote Desktop Licensing server & Set the Remote Desktop licensing mode.

1. Open Group Policy Editor. To do that:

1. Simultaneously press the Windows + R keys to open run command box.
2. Type gpedit.msc and press Enter.

2. In Group Policy Editor navigate to:

  • Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session Host Licensing

3. At the right pane, double click at Use the specified Remote License Servers.

4. Click Enabled, and then at 'License server to use' field, type the RDS license server name and click OK.

5. Then open the Set the Remote Desktop licensing mode setting.

6. Click Enabled and then specify the licensing mode (Per User or Per Device) for the RDS host server and then click OK again.

7.Close Group Policy Editor.
8. Verify the RD Licensing configuration, by going to: Windows Control Panel –> Administrative Tools –> Remote Desktop Services –> RD Licensing Diagnoser.

Step 5. Add RD Clients (Users) to the Remote Desktop Users Group.

1. Open Server Manager.
2. From Tools menu, select Active Directory Users and Computers. *

* Note: If the RD Session Host Service is not installed on the Domain Controller, use the 'Local Users and Groups' snap-in or the 'Remote' tab in the 'System Properties' on the RDS host server, to add the remote desktop users.

3. Double click at your domain on the left and then select Builtin.
4. Open Remote Desktop Users on the right pane.

Service

5. At Members tab, click Add.

6. Type the name(s) of the users that you want to give Remote access to the RDS Server and click OK.

7. After selecting the remote desktop users, click OK again to close the window.

8. Continue to step-6 below.

Step 6. Allow the log on through remote desktop Services.

1. Open the Local Group Policy Editor. To do that:

1. Simultaneously press the Windows + R keys to open run command box.
2. Type gpedit.msc and press Enter.

2. In Group Policy Editor navigate to: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.

3. At the right Pane: double click at Allow log on through Remote Desktop Services.

4. Click Add User or Group.

Desktop As A Service Definition

5. Click Object Types, check all the available objects (Users, Groups, & Built-in security principals) and then click OK.

Remote Desktop As A Service Definition

6. Type remote desktop users and then click OK.

7. Finally click OK again and close Group Policy Editor.

8. Now you 're ready to connect to the Remote Desktop Session Host Server 2016/2012 from any Remote desktop client.

That’s it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free:

We're hiring

We're looking for part-time or full-time technical writers to join our team! It's about a remote position that qualified tech writers from anywhere in the world can apply. Click here for more details.

If you want to stay constantly protected from malware threats, existing and future ones, we recommend that you install Malwarebytes Anti-Malware PRO by clicking below (we do earn a commision from sales generated from this link, but at no additional cost to you. We have experience with this software and we recommend it because it is helpful and useful):

Full household PC Protection - Protect up to 3 PCs with NEW Malwarebytes Anti-Malware Premium!

-->

Purpose

Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008 with Remote Desktop Services (formerly known as Terminal Services) allow a server to host multiple, simultaneous client sessions. Remote Desktop uses Remote Desktop Services technology to allow a single session to run remotely. A user can connect to a Remote Desktop Session Host (RD Session Host) server (formerly known as a terminal server) by using Remote Desktop Connection (RDC) client software. The Remote Desktop Web Connection extends Remote Desktop Services technology to the web.

Note

This topic is for software developers. If you are looking for user information for Remote Desktop connections, See Remote Desktop Connection: frequently asked questions.

Where applicable

A Remote Desktop Connection (RDC) client can exist in a variety of forms. Thin-client hardware devices that run an embedded Windows-based operating system can run the RDC client software to connect to an RD Session Host server. Windows-, Macintosh-, or UNIX-based computers can run RDC client software to connect to an RD Session Host server to display Windows-based applications. This combination of RDC clients provides access to Windows-based applications from virtually any operating system.

Developer audience

Developers who use Remote Desktop Services should be familiar with the C and C++ programming languages and the Windows-based programming environment. Familiarity with client/server architecture is required. The Remote Desktop Web Connection includes scriptable interfaces to create and deploy scriptable virtual channels within Remote Desktop Services web applications.

Run-time requirements

Remote Desktop As A Service

Applications that use Remote Desktop Services require Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, or Windows Vista. To use Remote Desktop Web Connection functionality, the Remote Desktop Services client application requires Internet Explorer and a connection to the World Wide Web. For information about run-time requirements for a particular programming element, see the Requirements section of the reference page for that element.

In this section

Describes how to use the Remote Desktop ActiveX control.

You use the Remote Desktop Protocol Provider API to create a protocol to provide communication between the Remote Desktop Services service and multiple clients.

Virtual channels are software extensions that can be used to add functional enhancements to a Remote Desktop Services application.

Remote Desktop As A Services

The RemoteFX Media Redirection API is used in a Remote Desktop session to identify areas of the server that are displaying fast changing content, such as video. This content can then be video encoded and sent to the client in encoded format.

Describes how to use the Remote Desktop Connection Broker client API.

The personal desktop task agent API is used to handle scheduled updates to a personal virtual desktop.

Remote Desktop Services (formerly known as Terminal Services) provides functionality similar to a terminal-based, centralized host, or mainframe, environment in which multiple terminals connect to a host computer.

Free remote desktop services

The Remote Desktop Management Services (RDMS) Provider manages virtual desktop infrastructure (VDI) environments.

Documentation of property methods that you can use to examine and configure Remote Desktop Services user properties. Remote Desktop Services functions, structures, and Remote Desktop Web Connection scriptable interfaces are also documented.

Vdi As A Service

A list of the Remote Desktop Services shortcut keys.

The Remote Desktop Services WMI provider provides programmatic access to the information and settings that are exposed by the Remote Desktop Services Configuration/Connections Microsoft Management Console (MMC) snap-in.

Remote Desktop Services Is Currently Busy

How to program in the Remote Desktop Services environment and how to extend Remote Desktop Services (formerly known as Terminal Services) technology to the web by using Remote Desktop Web Connection.

Remote Desktop Services Manager

Related topics