Remote Desktop without Active Directory: installation and configuration

Windows Server 2012R2  Windows Server 2016  Windows Server 2019

Introduction

In this tutorial, I will explain how to install and configure remote desktop on Windows Server without Active Directory environment.

This solution does not allow full use of the Remote Desktop solution, but helps provide a working environment for users.

What you cannot do:

  • Multi-server farm
  • Collections management
  • RemoteApp
  • No broker
  • No centralized administration

Prerequisite

You just need a server, for this tutorial, I used a virtual machine with Windows Server 2019.

For use in Workgroup, device CALs are required.

Installing roles

To have a Remote Desktop environment, you have to install two roles:

  • Remote Desktop Session Host
  • License Server (Remote Desktop Services License Manager)

From the server manager, click on Add roles and features 1.

Server manager

When the wizard starts, click on Next 1.

Roles and features installation wizard

Choose the type of installation: Installation based on a role or a feature 1 and click on Next 2.

Install type

Select the server 1 and click on the Next button 2.

Select server

In the list of roles, check the Remote Desktop Service 1 box and click Next 2.

Select the Remote Desktop Services role

Skip the features by clicking Next 1.

Features list

An explanation of Remote Desktop Services is displayed, click Next 1.

Overview Remote Desktop Services role

Check the Remote Desktop Services License Manager service 1.

Select licenses server

Click on Add additional features 1 to install the administration console.

Then check the box for the Remote Desktop Session Host 1 service.

Select Remote Desktop Session Host

Click on Add Features 1.

The necessary services are selected, click on Next 1.

Services selected

Click on the Install 1 button.

Start install

Wait during installation …

Wait while installing Remote Desktop Services

Once the installation is complete, exit the wizard by clicking on the Close button 1.

Restart the server

Configuration of user accounts

Now you have to create the users and place them in the remote desktop users group.

Create users locally

Not being in an Active Directory environment, the user accounts must be created in the local server database.

Right click on the Start button 1 and click on Computer Management 2.

From the navigation panel, go to Users 1.

Right click in the central area and click on New User 1.

New user

Enter the username 1, enter the password 2 then configure the password options 3. Then click on Create 4.

By clicking on create the form is reloaded, create all the users and once finished, click on Close.

The users are created 1. Now go to Groups 2.

Add users to the Remote Desktop Users group

To allow users to connect to the remote desktop, they must be added to the local group: Remote Desktop Users

From the navigation panel click on the Groups 1 folder.

Double click on the Remote Desktop Users group 1 to access the properties.

Click on the Add 1 button.

Select the users created 1 who will be able to connect to the remote desktop and click on OK 2.

The users are members of the group, click on Apply 1 and OK 2.

It is also possible to add the Users group as a member of the Remote Desktop User group, by doing so, the users will have the direct right to connect to the server.

Remote Desktop Connection

The server is now ready to receive connections.

To go into production, you have to think about installing the applications …

Launch a Remote Desktop client.

On the General tab, enter the IP address or the DNS name in the Computer 1 field, then enter the identifier 2 in the User name field. Then click on Connection 3.

Enter the password for the account 1 and click OK 2.

Validate certificate security alerts if displayed.

We are connected to the remote desktop on the Windows server.

On the screenshot below, we can see that 4 connections are active.

Configure licenses

All that remains is to configure the license server. The subject was treated in another tutorial, I put the links to you:

Custom Remote Desktop Server

If you want to customize the Remote Desktop server by changing the service counter, I invite you to read this lesson: Customize the server (in French).

Conclusion

Although this solution is not optimal for managing a remote desktop environment, setting up an RDS server is possible and can be used for small structures that do not need more for teleworking for example.

Another advantage of this solution is the possibility of renting a server (VPS) and creating a teleworking environment with a single server.





Related Posts


RDS Farm: High Availability Service Broker Configuration

As a follow-up to the article: Deploy a RDS Windows 2012 R2 / 2016/2019 farm, we will see in this tutorial how to configure the high availability service broker. This configuration is optimized for cl

Hyper-V: Enable Extended Sessions

Presentation Extensive sessions on Hyper-V with virtual machines can enhance the user experience with: Device Sharing File transfer Extended resolution Copy / Paste through the console ... We find par

Connecting to Remote Desktop Session Host servers by the Broker

Problem If you followed the article: Setting up an RDS farm under Windows 2012R2/2016, the client connection configuration is done using a Round Robin on the DNS. What happens if the server returned b