Setting up a terminal server based on Windows 2012 r2

Installing Active Directory + Terminal Server on Windows Server 2012 R2

Before starting the settings, you need to set the name of the server itself:

StartServer ManagerLocal Server → Click on the current computer name to change it.

After that, once on the System Properties page, click the Change button, after which we go to the page for changing the computer name. Specify the desired name, and click OK. As a result, we get a system message stating that a reboot is required to apply the new setting. A reboot can be performed either immediately or later on your own.

Setting up a terminal server

Setting up a terminal server

After rebooting the server, we can proceed directly to the installation of the Active Directory directory service:

StartServer ManagerAdd roles and features:

Setting up a terminal server

In the dialog box that opens, select Install roles and features:

Setting up a terminal server

Next, you need to select the server on which we will install the AD role. From the Server Pool list, select our SRV01 server and click Next:

Setting up a terminal server

Then a list of available roles to install on our server will appear. In this case, we are interested in a role called Active Directory Domain Services. By checking this item, we will open a list of all the necessary components that will be installed for the basic functioning of the AD role. You can also install the DNS server role during the selection of roles for installation. In all remaining dialog boxes, click the Next button. At the very last step, click Install to install the role:

Setting up a terminal server

Upon completion of the installation, go back to the menu item StartServer ManagerAdd roles and features. As in the image below, once a new role has been established, a yellow triangle icon will appear:

Setting up a terminal server

We promote the role of the server to the level of a domain controller by clicking the button of the same name.

Then, after selecting the Add new forest item, specify the name of our domain and click Next:

Setting up a terminal server

We leave the compatibility of the forest and the root domain to Windows Server 2012 R2. Check the DNS Server and Global Catalog (GC) items. Set a password to restore directory services if the need arises in the future:

Setting up a terminal server

On the next tab, we will get a warning that it is not possible to perform delegation for this DNS server, we ignore the message and go to the next window:

Setting up a terminal server

On the next NetBIOS tab, leave the name unchanged:

Setting up a terminal server

At the next stage, the paths to the database files will be displayed, we also leave them unchanged:

Setting up a terminal server

By clicking Next, we will proceed to the list of summary settings, after which you can proceed directly to the installation stage itself. Automatic checks for the correctness of the installed parameters and settings will be performed, after which the Install button will become available:

Setting up a terminal server

When the installation is complete, the server will be rebooted.

Centralized management of users, and groups, editing, adding, and deleting them can now be performed through the Active Directory Administrative Center snap-in in the Server Manager menu, from the Tools tab:

Setting up a terminal server

Let's start installing the terminal server: StartServer ManagerAdd roles and features. Leave the Install roles and features selected on the next dialog box and proceed further:

Setting up a terminal server

Setting up a terminal server

Select the Select a target server item in the dialog box and click Next:

Setting up a terminal server

Let's move on to choosing a specific role for the server that we want to install. In this case, Remote Desktop Services:

Setting up a terminal server

Move on to the next Components window. We leave everything as it is, without changes, and move on:

Setting up a terminal server

Read the description of Remote Desktop Services and click Next:

Setting up a terminal server

Now you need to select the role services to install. We need the Remote Desktop Licensing role. We mark the corresponding item, in the child window that opens, confirm the addition of the components of this role, proceed to the installation stage, and wait for its successful completion. After installation, you will need to restart the server:

Setting up a terminal server

Setting up a terminal server

After that, you need to license the terminal server. Run the Remote Desktop Licensing Diagnostic Tool. This item is available from the Server Manager:

Setting up a terminal server

As you can see when you open the Remote Desktop Licensing Diagnostic Tool, the number of available licenses is still zero. First of all, to install licenses, you need to set the licensing mode for the terminal server. In Windows Server 2012, this is done through the Group Policy Control Panel. Let's open the command line and write the gpedit.msc command:

Setting up a terminal server

This command will open the Group Policy Editor. Let's go along the path: Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostLicensing Here we are interested in two parameters: Use the specified remote desktop licensing servers and Set the remote desktop licensing mode:

Setting up a terminal server

Dedicated Server

Dedicated server

Check out SIM-Networks’ powerful pre-made server configurations

See packages

Let's open the first parameter for editing and specify the licensing server. Since it is located on our server, we specify the name of our server (SRV01) or our IP address and change the policy state to Enabled:

Setting up a terminal server

Change the second group policy setting. We need to choose how the licensing procedure will take place. There are two options: Per Device or Per User. With 5 licenses and Per Device mode, you can create an unlimited number of users on the server who will be able to connect via Remote Desktop only from 5 computers on which these licenses are installed. If you select the Per-user mode, then only 5 selected users will be able to access the server, regardless of the device from which they connect. In our example, we select the Per User licensing option.

Setting up a terminal server

Let's go back to the Remote Desktop Licensing Diagnostic Tool snap-in and see an error saying that the license server is listed but not enabled:

Setting up a terminal server

Let's fix this error by activating the license server. Let's go to the Remote Desktop Licensing Manager:

Setting up a terminal server

We see that the status of our licensing server is Not activated. To activate it, right-click and select Activate Server. from the context menu that appears. After that, the server activation wizard will open:

Setting up a terminal server

Setting up a terminal server

Click Next and go to the next item for choosing the connection method, leaving the item Auto:

Setting up a terminal server

Next, you will need to enter information for the organization, where all fields are required. As well as additional information about the organization, which are optional:

Setting up a terminal server

Then a message appears to activate the license server. It remains to install licenses on the server. Let's leave the Run the license installation wizard option enabled in the final window for activating the license server:

Setting up a terminal server

The license installation wizard will start:

Setting up a terminal server

We need to select the program based on which our licenses are obtained in the next window. The example considers the type of Agreement «Enterprise Agreement»:

Setting up a terminal server

Go to the next window and enter the number of our agreement:

Setting up a terminal server

Specify the product version, license type, and a number of licenses by our licensing program:

Setting up a terminal server

Let's wait until the installation wizard activates the licenses:

Setting up a terminal server

Make sure the license server is running and check the number of installed licenses in the license manager:

Setting up a terminal server

In the Remote Desktop Licensing Diagnostic Tools menu we see that there are no errors and the number of installed licenses is equal to the one that we entered in the previous steps:

Setting up a terminal server

After that, you can perform multi-user connections of clients, for example, through the built-in client in Windows Remote Desktop Connection. It should also be noted that the user who needs access to the Remote Desktop connection must be a member of the Remote Desktop Users group..

Dedicated server configuration selection here: https://www.sim-networks.com/dedicated

Did you like the article?

Cookie consent

By clicking «I agree», you consent to our website's use of cookies to give you the most relevant experience by remembering your preferences and repeat visits. However, you may visit «Manage сookies» to provide controlled consent. Learn more

Cookies settings

functional

Necessary cookies are crucial for the basic functions of the website and the website will not work in its intended way without them.

Analytics

Analytical cookies are used to understand how visitors interact with the website.

Advertisement

Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns.