Windows server 2012 r2 несколько одновременных сеансов rdp

Май 16, 2016 11:24

This guide will explain how to allow multiple sessions in a Windows VPS. A common usage case for this would be to allow a developed application or a remotely accessed support desktop. Additionally, there will be some information on where to purchase the RDS CAL license directly from Microsoft to allow for many users.

It may be best to consider a higher specification VPS or a Dedicated Server if you wish to use more than 3 users per machine, as the overall performance of the VPS will degrade per user.

How to Enable Multiple Remote Desktop (RDP) Sessions

Step 1. Connect to the Windows Server session by RDP.

Step 2. Click The Search button next to the start menu (Windows 2016) or typing into the start menu (Windows Server 2012)

Step 3. Enter in gpedit.msc

Step 4. Once Group Policy Editor had loaded, navigate to Computer Configuration, next Administrative Templates, then Windows Components, Remote Desktop Services, and Remote Desktop Session host.

Step 5. From there, you should see a folder marked as Connections. Click on it.

Step 6. Next right click with your mouse on Limit Number of Connections and click Edit.

Step 7. From there, you can set the number to the limit you wish to have or turn it off.

To access more than two sessions at a time, you will want to purchase an RDS Cal license from a certified provider. You can purchase a Remote Desktop Service Client Access License from Microsoft.

Step 8. Next, click Next Setting until you are at the Restrict Remote Desktop Services users to a single Remote Desktop Services session screen so you can edit this setting.

Step 9. In this window, you can click Disabled to turn off the user restrictions.

Step 10. Finally, reboot the server from your Cloud Control Overview page, and the group policy changes should automatically apply.

Reversing These Changes

The process to reverse the changes is easy. You would follow the same steps above and set the desired Group Policies to Not Configured and select Enabled or Disabled.

As everyone knows with the introduction of Windows Server 2012 & 2012 R2, there are various changes and no more availability for RDSH configurations or Remote Desktop Service Manager;
now we can manage all the settings under Server Manager and group policy.

Configuration 1: Remote Desktop Timeout settings:

Here, we will see the Remote Desktop timeout settings. You can maintain the settings under below mention path (Figure 1 and Figure 2).

1. Open the
   Server Manager, select Remote Desktop Services.
2. In Remote desktop Services, in right side you can drop down to
   collections.
3. Select the
   collection which you want to edit the settings.
4. Under
   collections Properties, select Task and then Edit Properties.
5. In Properties dialog box, select
   Session.
6. You can find all the
   timeout settings under session collection properties; edit according to your requirements and then
   OK.

Figure 1: Selecting Collection Properties

Figure 2: Configuring screen for Timeout and reconnection Settings

Group policy setting:

The same settings can also be applied by Group Policy.

You can also configure timeout and reconnection settings by applying the following Group Policy settings, you can check the figure 3 for graphical view.

—         
Set time limit for disconnected sessions

—         
Set time limit for active but idle Remote Desktop Services sessions

—         
Set time limit for active Remote Desktop Services sessions

—         
End session when time limits are reached

In addition to this another group policy available with the help of which you can bale to set time limit for logging off the RemoteApp according to our desired time. This setting
can be applied with addition to above mentioned policy.

—         
Set time limit for logoff of RemoteApp Sessions

These Group Policy settings are located in the following locations:

Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostSession Time Limits

User ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostSession Time Limits

These Group Policy settings can be configured by using either the Local Group Policy Editor or the Group Policy Management Console (GPMC).

Note:

These Group Policy settings will take precedence over the settings configured in Remote Desktop Session Host Configuration. If both the Computer Configuration and the User Configuration policy
settings are configured, the Computer Configuration policy settings take precedence.

Figure 3: Group Policy for setting Timeout and reconnection setting

Configuration 2:
Restrict & Enable user to a single & multiple session

Under Windows Server 2012 & 2012 R2, there is no specific setting under RDP-TCP as it is not available.

1. Restrict User to Single session:

To restrict the user to single session (Disable Multiple RDP Session) you can configure the setting under group policy (Figure 4).

Computer Configuration Administrative Templates Windows Components Remote Desktop Services Remote Desktop Session Host Connections

Restrict Remote Desktop Services users to a single Remote Desktop Services session     Enabled

Figure 4: Group policy for Restrict user to Single session

1. Enable user to multiple session:

To enable the user to multiple session you can configure the setting under below (Figure 5).

Computer Configuration Administrative Templates Windows Components Remote Desktop Services Remote Desktop Session Host Connections

Restrict Remote Desktop Services users to a single Remote Desktop Services session     Disabled

Figure 5: Group Policy for Enable user to Multiple Session

In addition you can also edit the registry setting for allowing multiple RDP session as per below (Figure 6).

HKEY_Local_MachineSYSTEMCurrentControlSetControlTerminal Server

fSingleSessionPerUser     REG_DWORD     0x00000000

Note: By default the registry value is set to 1, but you need to change to 0.

Figure 6: Display the registry settings

Also you can edit the policy “Limit number of connections” and set RD Maximum collection as per your company
requirements (Maximum limit: 999999) for above mention group policy path (Figure 7).

Figure 7: Group Policy for Limit number of Connections

Apart from this, if you have not specified any policy or registry setting and still you want to restrict the new session, then in Windows Server 2012 & 2012 R2 there is option where you
need to follow below steps (Figure 8 and Figure 9).

1. Right click a Remote Desktop Session Host in specified location of Host Server and select “Do not allow new connections”.
2. After clicking that it will ask you for your confirmation, click yes and no new connection will be allowed.
   

Figure 8: Setting displaying “Do not allow new connections”

Figure 9: Confirmation popup

RD Gateway Connection Properties:

If you have deployed RD Gateway under your environment you can also limit the number of simultaneous connections through RD Gateway by configuring
policy under RD Gateway Manager. For this you need to follow below mention path.

1. Open RD Gateway Manager, select the server which you want to modify.
2. Right click Properties.
3. Under General Tab

—Limit maximum allowed simultaneous
connections to:Specify the number of connection you want to able to provide connection.

—Allow the maximum
supported simultaneous connections:This
setting will allow maximum supported connections at a time.

—Disable new connections:This
setting will not allow new connections through RD Gateway but Active connection will not be automatically disconnected.

Select the option as per requirement which able to allow the connection

Figure 10: Connections setting under RD Gateway Manager

Configuration 3: Configure keep-alive connection interval

As per above mention in initial post you can able to change the setting for Keep alive connection interval. In addition to this also verify the
registry setting must be set as per following (Figure 11 and Figure 12).

HKEY_Local_Machine SOFTWARE Policies Microsoft Windows NT Terminal Services

KeepAliveEnable       REG_DWORD           0x00000001 (1)

KeepAliveInterval     
REG_DWORD           0x00000001 (1)

Figure 11: Group Policy setting for Keep alive

Figure 12: Registry setting for keep alive

If you need further assistance, welcome to post your questions in our
Remote Desktop Services (Terminal Services) forum.

If you would like to achieve this in Windows Server 2008 or Windows Server 2008 R2, please move on to the next post.

Hello,

I have setup RDS on Server 2012 R2 with the following roles:  (RD Connection Broker, RD Session Host, RD Gateway, RD Licensing, RD Web Access).  My sole purpose for this setup was to enable this server and only this server to allow more than 2
concurrent RDP connections. 

Here is some background information:

1.  I will not be using RemoteApps or the Web access, I only only need to RDP into this server with more than 2 concurrent connections.

2.  The licensing server is activated and I have a 50 user CAL installed on it. It has issued licenses to 3 users that have logged into the server while I was looking at the Web site features.  So I know the licensing is working properly.

3.  This server does reside in a domain but I’m looking to have everything self contained on just the one box.  I do not want to put anything on my domain controller or a separate machine.

4.  Everything looks to be fully configured in all of the roles.  I have no warnings about things not being configured correctly.

5.  When I attempt to login with a 3rd user to this system, it still prompts to have me remove one of the previous 2 sessions.

I know I must be looking right past the setting or it is in a very convoluted space, but how do I enable this server to allow more than 2 RDP sessions?  I’ve made the change in group policy for (Administrative TemplatesWindows ComponentsRemote Desktop
ServicesRemote Desktop Session HostConnectionsLimit number of connections) to 50 but this still not seem to correct the problem.

Thanks for any answers you can provide,

Fred Levario

Hello,

I have setup RDS on Server 2012 R2 with the following roles:  (RD Connection Broker, RD Session Host, RD Gateway, RD Licensing, RD Web Access).  My sole purpose for this setup was to enable this server and only this server to allow more than 2
concurrent RDP connections. 

Here is some background information:

1.  I will not be using RemoteApps or the Web access, I only only need to RDP into this server with more than 2 concurrent connections.

2.  The licensing server is activated and I have a 50 user CAL installed on it. It has issued licenses to 3 users that have logged into the server while I was looking at the Web site features.  So I know the licensing is working properly.

3.  This server does reside in a domain but I’m looking to have everything self contained on just the one box.  I do not want to put anything on my domain controller or a separate machine.

4.  Everything looks to be fully configured in all of the roles.  I have no warnings about things not being configured correctly.

5.  When I attempt to login with a 3rd user to this system, it still prompts to have me remove one of the previous 2 sessions.

I know I must be looking right past the setting or it is in a very convoluted space, but how do I enable this server to allow more than 2 RDP sessions?  I’ve made the change in group policy for (Administrative TemplatesWindows ComponentsRemote Desktop
ServicesRemote Desktop Session HostConnectionsLimit number of connections) to 50 but this still not seem to correct the problem.

Thanks for any answers you can provide,

Fred Levario

Обновлено: 02.11.2017
Опубликовано: 13.09.2016

Удаленный рабочий стол применяется для дистанционного администрирования системы. Для его настройки нужно сделать, буквально, несколько шагов.

Включение

1. Открываем сведения о системе. В Windows Server 2012 R2 / 2016 или 10 кликаем правой кнопкой мыши по Пуск и выбираем Система.

В Windows Server 2012 / 8 и ниже открываем проводник или меню Пуск. Кликаем правой кнопкой по Компьютер и выбираем Свойства.

2. Настраиваем удаленный рабочий стол. В меню слева кликаем по Настройка удаленного доступа.

В открывшемся окне ставим переключатель в положение Разрешить удаленные подключения к этому компьютеру.

* желательно, если  будет установлен флажок Разрешить подключение только с компьютеров, на которых работает удаленный рабочий стол с проверкой подлинности на уровне сети. Но если компьютер, с которого мы будем заходить с устаревшей операционной системой, это может вызвать проблемы.

Предоставление доступа

Очень важно, чтобы у пользователя был установлен пароль. Без него зайти в систему с использованием RDP будет невозможно — это программное ограничение. Поэтому всем учетным записям ставим пароли.

У пользователей с правами администратора права на использование удаленного стола есть по умолчанию. Чтобы обычная учетная запись могла использоваться для удаленного входа в систему, добавьте ее в группу Пользователи удаленного рабочего стола. Для этого открываем консоль управления компьютером (команда compmgmt.msc) — переходим по разделам Служебные программы — Локальные пользователи и группы — Группы и кликаем дважды по Пользователи удаленного рабочего стола:

В открывшемся окне добавляем необходимых пользователей.

Для проверки правильности настроек, используйте программу Подключение к удаленному рабочему столу (находится в меню Пуск или вызывается командой mstsc) на любом другом компьютере в сети.

Ограничение по количеству пользователей

По умолчанию, в серверных операционных системах Windows разрешено подключение для одновременно двух пользователей. Чтобы несколько пользователей (больше 2-х) могли использовать удаленный стол, необходима установка роли удаленных рабочих столов (терминального сервера) и активации терминальных лицензий — подробнее, читайте в инструкции Установка и настройка терминального сервера на Windows Server.

В пользовательских системах (Windows 10 / 8 / 7) разрешено подключение только одному пользователю. Это лицензионное ограничение. В сети Интернет можно найти патчи для его снятия и предоставления возможности подключаться удаленным рабочим столом для нескольких пользователей. Однако, это нарушение лицензионного соглашения.

Доступ через глобальную сеть (Интернет)

Для возможности подключения по RDP из вне необходим статический внешний IP-адрес. Его можно заказать у Интернет провайдера, стоимость услуги, примерно, 150 рублей в месяц (некоторые поставщики могут предоставлять бесплатно). Для подключения нужно использовать полученный внешний IP.

Если компьютер подключен к Интернету напрямую, никаких дополнительных действий не потребуется. Если мы подключены через NAT (роутер), необходима настройка проброса портов. Пример того, как это можно сделать на Mikrotik.

v. 1.2