Skip to content

Commit 4d0c329

Browse files
author
Simonx Xu
committed
Update remote-desktop-licensing-mode-not-configured-warning.md
1 parent f82fdd1 commit 4d0c329

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

support/windows-server/remote/remote-desktop-licensing-mode-not-configured-warning.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: troubleshooting
88
ms.reviewer: kaushika, v-lianna
99
ms.custom: sap:Remote Desktop Services and Terminal Services\Licensing for Remote Desktop Services (Terminal Services), csstroubleshoot
1010
---
11-
# Remote Desktop licensing mode is not configured warning when you connect to a RD Session Host
11+
# Remote Desktop licensing mode is not configured warning when you connect to an RD Session Host
1212

1313
This article helps you troubleshoot a licensing warning message when you connect to a Remote Desktop (RD) Session Host.
1414

@@ -26,13 +26,13 @@ When you use the Remote Desktop Web portal (RD Web portal) or a direct remote de
2626

2727
## The licensing mode isn't properly configured or the RD Session Host can't communicate with the RD license server
2828

29-
By default, a newly created RD Session Host has a grace period of 120 days. If the licensing mode isn't properly configured in the RDS deployment, or if the RD Session Host can't communicate with the RD license server, you receive one of the pop-up messages each time you log in.
29+
By default, a newly created RD Session Host has a grace period of 120 days. If the licensing mode isn't properly configured in the RDS deployment, or if the RD Session Host can't communicate with the RD license server, you receive one of the pop-up messages each time you sign in.
3030

3131
> [!NOTE]
3232
> The pop-up message isn't always a sign of a problem. In the following scenarios, you receive the message even if all the settings are as expected:
3333
>
34-
> - When you connect with a local account and the licensing mode is set to **Per User**.
35-
> - When you connect with an administrative session.
34+
> - Connecting with a local account and the licensing mode is set to **Per User**
35+
> - Connecting with an administrative session
3636
3737
## Check the RD Licensing configuration
3838

@@ -65,7 +65,7 @@ To check the licensing configuration by using Server Manager, follow these steps
6565

6666
To check the licensing configuration by using Group Policy, follow these steps:
6767

68-
1. Depending on whether you want to configure Group Policy centrally from your domain or locally on each session host, do one of the following:
68+
1. Depending on whether you want to configure Group Policy centrally from your domain or locally on each session host, perform one of the following operations:
6969

7070
- If you manage Group Policy at the domain level, open the Group Policy Management Console (GPMC), right-click the Group Policy Object (GPO) that targets your RD Session Hosts, and then select **Edit**. This operation opens the Group Policy Editor.
7171
- If you manage Group Policy at the server level, open the Local Group Policy Editor on the RD Session Host.

0 commit comments

Comments
 (0)