In principle, the sequence of steps is not very different from installing Terminal Server on Windows Server 2008 R2, but there are some significant differences. So:
0. What you need:
- A computer (server) with Windows Server 2012 installed on it and administrator rights on this server.
- A valid Terminal Server CAL purchased through one of the existing licensing programs. (In this article I will use the agreement number found on the Internet for the Enterprise Agriment program. At the time of this writing, the workers were numbers: 6565792, 5296992, 3325596, 4965437, 4526017.)
- Access to the Internet for activating the licensing server and installing licenses (activation by phone is also possible).
1. Installing Remote Desktop Services
Launch Server Manager. It can be launched from the shortcut on the taskbar, or by running the command servermanager.exe(To do this, press the key combination Win + R, in the window that appears in the field “ Open» ( Open) write the name of the command and press " OK»).
In the menu, in the upper right corner, select “ Control» ( Manage) - « Add roles and components» ( Add Roles and Features) .
Will start " Add Roles and Features Wizard» ( Add Roles and Features Wizard)... Click " Further» (Next) on the start page.
Leave the switch on " Installing Roles and Features» ( Role-based or features-based installation) and again press “ Further» (Next).
We select the server from the server pool on which the Terminal Service will be installed. In my example, this is the given local server. Click " Further» (Next).
We celebrate the role of “ » ( Remote Desktop Services) in the list of roles and click " Further» (Next) .
We leave the components as they are. Without noticing anything, click " Further» (Next) .
We read the description of the Remote Desktop Service and click " Further» (Next).
Now you need to select the role services to install. At least it will be useful to us " Remote Desktop Licensing» ( Remote Desktop Licensing) (we also agree to the installation of additional components by clicking on " Add components» ( Add Features) in the appeared wizard)
and " » ( Remote Desktop Session Host) (again agree to the installation of additional components by clicking on " Add components» ( Add Features) in the window that opens). Having marked the required role services, click " Further» (Next).
All the parameters for installing the role are defined. On the last page, set the flag “ Automatically restart the destination server if required» ( Restart the destination server automatically if required), confirm the choice by pressing " Yes» ( Yes) in the window that appears and click " Install» ( Install) to start the installation of the service.
If everything went well, after rebooting, we will see a message about the successful installation of all selected services and components. Click " Close» ( Close) to complete the wizard.
2. Defining a licensing server for Remote Desktop Services.
Now let's run " "(RD Licensing Diagnoser). This can be done from the server manager by selecting in the upper right menu “ Facilities» ( Tools) - « Terminal Services» — « Remote Desktop Licensing Diagnostic Tool» ( RD Licensing Diagnoser) .
Here we see that there are no licenses available yet because the licensing mode for the RD Session Host server is not set.
The licensing server is now specified in local group policies. To start the editor, run the command gpedit.msc.
The Local Group Policy Editor will open. In the tree on the left, open the tabs:
- « Computer configuration» ( Computer Configuration)
- « Administrative Templates» ( Administrative Templates)
- « Windows components» ( Windows Components)
- « Remote Desktop Services» ( Remote Desktop Services)
- « Remote Desktop Session Host» ( Remote Desktop Session Host)
- « Licensing» ( Licensing)
- « Remote Desktop Session Host» ( Remote Desktop Session Host)
- « Remote Desktop Services» ( Remote Desktop Services)
- « Windows components» ( Windows Components)
- « Administrative Templates» ( Administrative Templates)
Let's open the parameters " Use Specified Remote Desktop Licensing Servers» ( Use the specified Remote Desktop license servers) by clicking 2 times on the corresponding line.
In the window for editing policy settings, move the switch to " Included» ( Enabled). Next, you need to define a licensing server for Remote Desktop Services. In my example, the licensing server is on the same physical server. Specify the network name or IP address of the license server and click " OK» .
Next, we change the policy settings " Set Remote Desktop Licensing Mode» ( Set the Remote licensing mode). We also set the switch to " Included» ( Enabled) and specify the licensing mode for the RD Session Host server. There are 2 options:
- « Per User
- « Per Device
In order to understand how these modes differ, consider a simple example. Let's say you have 5 licenses. In the mode " Per device»You can create an unlimited number of users on the server who can connect via Remote Desktop only from 5 computers on which these licenses are installed. If you select the " Per user”, Then only 5 selected users will be able to enter the server, regardless of which device they are connecting from.
We select the mode that is most suitable for your needs and click " OK» .
After changing the above policies, close the editor.
Back to the snap " Remote Desktop Licensing Diagnostic Tool» ( RD Licensing Diagnoser) and we see a new error indicating that the licensing server is listed but not enabled.
To start the licensing server, go to " » ( RD Licensing Manager). You can find it in the Server Manager, the tab " Facilities» ( Tools) - « Terminal Services» - « Remote Desktop Licensing Manager» ( Remote Desktop Licensing Manager) .
Here we will find our licensing server, with the status “ Not activated» ( Not Activated). To activate, click on it with the right mouse button and select “ Activate server» ( Activate Server) .
The Server Activation Wizard starts. We press " Further» (Next) on the first page of the wizard.
Then we select the connection method (" Auto» ( Automatic connection) by default) and click " Further» (Next).
Enter information about the organization (these fields are required) and then click " Further» (Next).
Enter additional information about the organization (optional) and click again " Further» (Next) .
The license server is activated. Now the licenses should be installed. To do this, click " Further» (Next) leaving the flag " Run the license installation wizard» .
3. Installing Licenses on the Remote Desktop Licensing Server
Then we select the licensing program you need. In my example, this is “ Enterprise Agreement"". We press " Further» (Next) .
We indicate the product version, license type and number of licenses in accordance with your licensing program. We press " Further» (Next) .
Well, we are waiting for the completion of the license installation wizard with a message that the requested licenses have been successfully installed.
In the licensing manager, we make sure that the server is running, and also see the total and available number of installed licenses.
And finally, we return to " Remote Desktop Licensing Diagnostic Tools» ( RD Licensing Diagnoser) and we see that there are no errors, and the number of licenses available to customers corresponds to what we entered in the previous step.
This completes the installation of Terminal Server on Windows Server 2012.
New to Windows Server 2012R2? I was already "lucky" to set up a terminal server on it. To be honest, it is completely unclear why it was necessary to shove the new ribbon interface into the server - Microsoft's logic has defied explanation lately.
But this is not the worst thing. From now on, to install the role of the terminal server, you need to raise the domain. I didn’t expect such a surprise ... I don’t need a domain in principle. Setting up a domain does not take much time, but why spawn entities where they are not needed.
However, everything turned out to be solvable, albeit with some additional steps, which I learned about from technet.microsoft.com.
Configuring the role of the terminal server on WinServer 2012 without raising the domain
There are no fundamental differences in installing Windows Server 2012 from Windows Server 2008 R2, so we will skip this step. Note that the operating system is perfectly installed from a flash drive on which the image was recorded (I have not used CD / DVD for a long time - it is slow and tedious). Let's go directly to installing the RDS role on the server.
To do this, start the Server Manager, and go to the Local Server field
How to install and configure Terminal Server on Windows Server 2012R2-01
We select a server from the pool.
We set the checkbox "Remote Desktop Services"
It is possible to install all the components of the RDS role at once, but on Technet, for a better understanding of the process, it is advised to divide this process into two stages. We will also follow this advice. Install the Remote Desktop Licensing component first
We confirm the addition of components for the terminal table on Windows Server 2012 R2.
We check the summary information, and if everything is correct, then click the "Install" button.
After completing the process, launch the Remote Desktop Licensing Manager (RD Licensing Manager), in which we activate our license server and install the terminal license package (for example: Windows Server 2012 - RDS Per User CAL, 5 pcs.).
Activation takes place through a right click.
There are no innovations here, and therefore I will not describe this process in detail (perhaps I will open the topic in one of the future articles - I am waiting for your suggestions and comments).
The wizard takes over the entire process of activating and installing a license package, our task is to choose the right licensing program, type of licenses, quantity, etc.
The second step is to install the Remote Desktop Session Host component.
After installing this component, we will have the "Remote Desktop Licensing Diagnostic Tool (RD Licensing Diagnoser)", which will inform us about the absence of a server that distributes terminal licenses (unfortunately, I did not make a screenshot with an error, the server version is already working).
It should be noted that the snap-in lacks the management tools that were in Windows Server 2008 R2, i.e. there is no possibility of adding a license server.
Configuring local policies for servers located in a workgroup
The most interesting thing remains. It is not difficult to fix this situation - it is enough to configure only two local policies. In the terminal line, write gpedit.msc and change the corresponding keys.
Computer Configuration \ Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop Session Host \ Licensing - Use Specified Remote Desktop Licensing Servers (add our server name)
Computer Configuration \ Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop Session Host \ Licensing - Set the Remote Desktop Licensing Mode (select the license type)
Good afternoon, dear readers of the blog site, today I want to tell you in this article how to set up a terminal server in Windows Server 2008R2. In part one, we went over the initial part of installing Remote Desktop Services and rebooted the server. After a reboot, the automatic continuation of the role installation is initiated. When windows server 2008R2 informs you that the role has been successfully delivered, go to Administration-Remote Desktop Services-Remote Desktop Licensing Manager.
Terminal Server 2008 r2 licensing
As I said earlier, you will need to license your role, we will deliver them either to the user or to the devices, they are also called CAL (Client Access License). Ideally, CAL data should be purchased from Microsoft, considering the option that is more profitable for you, either a bunch of users are sitting, or a bunch of devices. In terms of prices, I want to note that they are very biting, but in principle the terminal pays for itself, especially if you use remote app applications, the savings will be on the face, if finances allow you, be sure to make a license activation.
In the snap-in that opens, right-click your server and select Activate Server from the context menu.
The Server Activation Wizard will open and it will allow you to activate the Terminal Server 2008 r2, click on
We leave the connection method automatically, this is suitable in 99 percent of cases, this is our option 🙂.
We fill out a small questionnaire with the following sample:
- Surname
- Name of the organization
- Country
Everything can be filled with left values, you can, like in my picture, no one will scold unless of course they get caught by the hand, but in my test environment, do not care.
You do not have to fill in the information about the organization and immediately click on, knowing Microsoft's love of collecting what is needed themselves, they will find you if they wish.
The process of activating the server will begin, you must have access to the Internet from this server, otherwise you will receive an error, it takes a couple of seconds in time.
Next, a window will appear about the successful activation of the terminal server, but that was not the case, now microsoft will require from you a code for how many licenses you are applying for and what type of license your Remote Desktop Services has.
Select another agreement in the Licenses field.
We indicate in the license field Another agreement, it implies entering a digital key.
We enter the magic number to activate licenses on your friend, namely 4965437. There are also codes for licensing the terminal server 2008, they are easily googled in a couple of minutes, if this did not work for you, write to me, I will help you and I will share.
We select the version of the product to which you will receive licenses, in my case it is windows server 2008 R2, select the client or device and write the number at the very bottom, it all depends on greed. A maximum of 9999 RDS server licenses can be obtained.
We click to complete and in fact, the activation of the terminal server 2008 r2, is almost finished.
Now let's make sure everything was activated well on the terminal server. Right-click and select check setting.
We can see that everything was hooked up perfectly and our RDS licensing server is activated. Be sure to check that it is present in the licensing server group, otherwise add.
As you can see, activation of Terminal Server 2008 r2 is a rather trivial thing and knowing the steps takes a couple of minutes. I hope that you understand this material on the topic of terminal server very well and are ready for the third part of the article, where we will analyze how to register a licensing server for other terminal servers.
Today I will talk about how to raise a terminal server based on Windows Server 2008 R2. In general, this is quite simple, but there are a few subtle points, so:
1. What you need
- Powerful computer (server) with Windows Server 2008 R2 installed on it. (From how to install this axis, I wrote)
- A valid Terminal Server CAL purchased through one of the existing licensing programs. (In this article I will use the agreement number found on the Internet for the Enterprise Agriment program. At the time of this writing, the workers were numbers: 6565792, 5296992, 3325596, 4965437, 4526017.)
2. Installing Remote Desktop Services
We start the server manager ( "Start" — "Administration" — Server Manager). We open the tab “ Roles"And click" Add Roles ".
Will start " Add Roles Wizard". We press " Further", Then select the role" "And press 2 times again" Further» .
We will see a window for selecting role services. In it we select “ Remote Desktop Session Host" and " Remote Desktop Licensing"And again 2 times" Further» .
We select the authentication method “ Do not require network level authentication " so that old clients can connect. Then we press " Further» .
At the next step, you need to select the licensing mode: " Per device" or " Per user "... To understand how these modes differ, consider a simple example. Let's say you have 5 licenses. In Per Device mode, you can create an unlimited number of users on the server that can 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 enter the server, regardless of which device they are connecting from. Choose the mode that suits you best and click " Further» .
At this point, you need to add the users or user group that will have access to Terminal Service. To do this, click " Add», « Additionally", In the opened window" Search", Select a user and click" OK". In order for all users, without exception, to be able to connect to our terminal server, we add the group “ Everything". Then we press " OK" and " Further» .
If you want to be able to listen to audio data and watch video via a remote desktop, check the corresponding box. Likewise with sound recording and Windows Aero. Having selected the necessary parameters, click " Further» .
Now you need to configure the discovery scope for Remote Desktop Licensing. If you have Active Directory installed, then select “ This domain" or " Forest", Depending on the structure of the domain. Otherwise, choose “ This working group"And click" Further» .
We check all the settings and click " Install».
A reboot will be required after installation.
3. Installing the Remote Desktop Licensing Server
If everything is done correctly, then after the reboot we will see a window with a message that the installation was successful, but with a warning that you need to configure the licensing settings on the RD Session Host server.
Let's specify the licensing server manually. To do this, run the " Remote Desktop Session Host Configuration» (« Start» — « Administration» — « Remote Desktop Services"). There we see that the Remote Desktop Licensing Server is not specified.
We click 2 times on this line, in the opened window “ Properties", Select the tab" Licensing"And press the button" Add» .
We select servers from well-known licensing servers. In our case, the licensing server is located on the same computer as the terminal server. Add it and click " OK» .
Now, if you go to the deposit " Diagnostics of licensing»We will see that the licensing server is selected, but not enabled.
To start and activate the Remote Desktop Licensing Server, run " Remote Desktop Licensing Manager» (« Start» — « Administration» — Remote Desktop Services"). In the dispatcher we see our server and the status “ Not activated". Click on it with the right mouse button and select “ Activate server» .
Will start " Server Activation Wizard a" . Click " Further". In the next window, select the connection method " Auto (Recommended)"And press again" Further". We fill in the information about the organization. Then, filling in additional information (optional) and clicking " Further", We will see a message about successful server activation.
Now you need to install the licenses. If this is not done, then the license server will issue temporary licenses that are valid for 120 days. To install licenses, click " Further", Leaving a check mark" Run the license installation wizard". Alternatively, you can run this wizard from " Remote Desktop Licensing Manager"By right-clicking on the server and selecting" Install licenses". We can also check that the server is activated there.
In the launched " License Installation Wizard"Click" Further"And we get to the window for selecting the licensing program. The following steps depend on how you purchased your licenses. In my example, this is “ Enterprise Agreement". Having chosen the required type of licensing, click " Further» .
Enter the agreement number and click " Further". In the next window, select the product version: “ Windows Server 2008 or Windows Server 2008 R2", We select the same type of licenses that we selected when adding roles (" per user" or " per device») And enter the number of required licenses.
Click " Further"And wait for the message about the successful installation of the license. (I want to note that, for reasons I do not understand, this procedure does not always end positively. If the wizard said that it was not possible to install the license, try repeating the procedure some time later. Sooner or later the license will be installed. It has been checked more than once.) If everything went well in In the server manager, we should see the parameters of our license.
And we will make sure that there are no problems by going to the tab " Diagnostics of licensing"In Server Manager. 
That's it, this completes the installation of the terminal server. You can connect to the server using the built-in Windows client.
Did this article help you?
In this article I will give detailed step-by-step instructions on how to install a terminal server, or, in other words, Remote Desktop Services in Windows Server 2012. In principle, the sequence of actions is not very different from the installation, but there are a number of significant differences. So:
1. What you need
- A computer (server) with Windows Server 2012 installed on it (I wrote about installing this OS) and administrator rights on this server.
- A valid Terminal Server CAL purchased through one of the existing licensing programs. (In this article I will use the agreement number found on the Internet for the Enterprise Agriment program. At the time of this writing, the workers were numbers: 6565792, 5296992, 3325596, 4965437, 4526017.)
- Access to the Internet for activating the licensing server and installing licenses (activation by phone is also possible).
2. Installing Remote Desktop Services
Launch Server Manager. It can be launched from the shortcut on the taskbar, or by running the command servermanager.exe(To do this, press the key combination Win + R, in the window that appears in the field “ Open» ( Open) write the name of the command and press " OK»).
In the menu, in the upper right corner, select “ Control» ( Manage) — « Add roles and components» ( Add Roles and Features) .
Will start " Add Roles and Features Wizard» ( Add Roles and Features Wizard)... Click " Further» (Next) on the start page.
Leave the switch on " Installing Roles and Features» ( Role-based or features-based installation) and again press “ Further» (Next).
We select the server from the server pool on which the Terminal Service will be installed. In my example, this is the given local server. Click " Further» (Next).
We celebrate the role of “ » ( Remote Desktop Services) in the list of roles and click " Further» (Next) .
We leave the components as they are. Without noticing anything, click " Further» (Next) .
We read the description of the Remote Desktop Service and click " Further» (Next).
Now you need to select the role services to install. At least it will be useful to us " Remote Desktop Licensing» ( Remote Desktop Licensing) (we also agree to the installation of additional components by clicking on " Add components» ( Add Features) in the appeared wizard)
and " » ( Remote Desktop Session Host) (again agree to the installation of additional components by clicking on " Add components» ( Add Features) in the window that opens). Having marked the required role services, click " Further» (Next).
All the parameters for installing the role are defined. On the last page, set the flag “ Automatically restart the destination server if required» ( Restart the destination server automatically if required), confirm the choice by pressing " Yes» ( Yes) in the window that appears and click " Install» ( Install) to start the installation of the service.
If everything went well, after rebooting, we will see a message about the successful installation of all selected services and components. Click " Close» ( Close) to complete the wizard.
3. Defining a License Server for Remote Desktop Services
Now let's run " "(RD Licensing Diagnoser). This can be done from the server manager by selecting in the upper right menu “ Facilities» ( Tools) — « Terminal Services» — « Remote Desktop Licensing Diagnostic Tool» ( RD Licensing Diagnoser) .
Here we see that there are no licenses available yet because the licensing mode for the RD Session Host server is not set.
The licensing server is now specified in local group policies. To start the editor, run the command gpedit.msc.
The Local Group Policy Editor will open. In the tree on the left, open the tabs:
- « Computer configuration» ( Computer Configuration)
- « Administrative Templates» ( Administrative Templates)
- « Windows components» ( Windows Components)
- « Remote Desktop Services» ( Remote Desktop Services)
- « Remote Desktop Session Host» ( Remote Desktop Session Host)
- « Licensing» ( Licensing)
- « Remote Desktop Session Host» ( Remote Desktop Session Host)
- « Remote Desktop Services» ( Remote Desktop Services)
- « Windows components» ( Windows Components)
- « Administrative Templates» ( Administrative Templates)
Let's open the parameters " Use Specified Remote Desktop Licensing Servers» ( Use the specified Remote Desktop license servers) by clicking 2 times on the corresponding line.
In the window for editing policy settings, move the switch to " Included» ( Enabled). Next, you need to define a licensing server for Remote Desktop Services. In my example, the licensing server is on the same physical server. Specify the network name or IP address of the license server and click " OK» .
Next, we change the policy settings " Set Remote Desktop Licensing Mode» ( Set the Remote licensing mode). We also set the switch to " Included» ( Enabled) and specify the licensing mode for the RD Session Host server. There are 2 options:
- « Per User
- « Per Device
In order to understand how these modes differ, consider a simple example. Let's say you have 5 licenses. In the mode " Per device»You can create an unlimited number of users on the server who can connect via Remote Desktop only from 5 computers on which these licenses are installed. If you select the " Per user”, Then only 5 selected users will be able to enter the server, regardless of which device they are connecting from.
We select the mode that is most suitable for your needs and click " OK» .
After changing the above policies, close the editor.
Back to the snap " Remote Desktop Licensing Diagnostic Tool» ( RD Licensing Diagnoser) and we see a new error indicating that the licensing server is listed but not enabled.
To start the licensing server, go to " » ( RD Licensing Manager). You can find it in the Server Manager, the tab " Facilities» ( Tools) — « Terminal Services» — « Remote Desktop Licensing Manager» ( Remote Desktop Licensing Manager) .
Here we will find our licensing server, with the status “ Not activated» ( Not Activated). To activate, click on it with the right mouse button and select “ Activate server» ( Activate Server) .
The Server Activation Wizard starts. We press " Further» (Next) on the first page of the wizard.
Then we select the connection method (" Auto» ( Automatic connection) by default) and click " Further» (Next).
Enter information about the organization (these fields are required) and then click " Further» (Next).
Enter additional information about the organization (optional) and click again " Further» (Next) .
The license server is activated. Now the licenses should be installed. To do this, click " Further» (Next) leaving the flag " Run the license installation wizard» .
4. Installing Licenses on the Remote Desktop Services Licensing Server
Then we select the licensing program you need. In my example, this is “ Enterprise Agreement"". We press " Further» (Next) .
We indicate the product version, license type and number of licenses in accordance with your licensing program. We press " Further» (Next) .
Well, we are waiting for the completion of the license installation wizard with a message that the requested licenses have been successfully installed.
In the licensing manager, we make sure that the server is running, and also see the total and available number of installed licenses.
And finally, we return to " Remote Desktop Licensing Diagnostic Tools» ( RD Licensing Diagnoser) and we see that there are no errors, and the number of licenses available to customers corresponds to what we entered in the previous step.
This completes the installation of Terminal Server on Windows Server 2012.
5. Connecting to Terminal Server
You can use the Windows built-in client to connect to a Terminal Server.
Did this article help you?
