Skip to content

Commit 903b00b

Browse files
committed
update registry
1 parent 135444c commit 903b00b

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/windows-server/remote/troubleshoot-unexpected-rds-session-locks-or-disconnections.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,8 @@ Disconnects occurring without a consistent timing pattern are more likely caused
2929

3030
On a Windows computer, when **MaxIdleTime** or **MaxConnectionTime** are configured, RDS sessions disconnect when conditions are met with distinct messages. Additional RDS session time limit policies determine the behavior after a session is disconnected.
3131

32+
The two registry values locate at `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp`.
33+
3234
| Configuration | Set time limit for active but idle RDS sessions | Set time limit for active RDS sessions |
3335
| :------------------------ | :-------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- |
3436
| Registry (Type:REG_DWORD) | MaxIdleTime | MaxConnectionTime |
@@ -40,8 +42,6 @@ You can use the following two methods to configure the above registry values.
4042

4143
The default configuration for these session limits should be set at the **Collection** > **Properties tasks** > **Session** on the server that manages the RDS deployment. Usually, the server is the Remote Desktop Connection Broker. These settings are then applied to the registry of the Remote Desktop Session Hosts in that collection.
4244

43-
Registry path: `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp`.
44-
4545
> [!NOTE]
4646
>
4747
> - If users connect to the RDS Deployment through a Remote Desktop Gateway (RDGW), similar configuration can be done in **RDGW manager > Policies > Connection Authorization Policies > Timeouts tab**. Users that bypass the RDGW won't be affected.

0 commit comments

Comments
 (0)