Skip to content

Commit 15bfd17

Browse files
authored
Minor change
1 parent 849223b commit 15bfd17

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/windows-server/remote/unable-to-install-rds-deployment-or-add-rds-roles.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ When you try to install the RD Connection Broker role, the installation fails wi
6161

6262
> Unable to install RD Connection Broker role service on server \<ServerName\> - Failed.
6363
64-
This is commonly due to the fact that the object "NT SERVICE\ALL SERVICES" has been removed from the **Logon as a service** security policy, or there's another policy denying the **Logon as a service** privilege to the corresponding service account.
64+
This is commonly because the object "NT SERVICE\ALL SERVICES" has been removed from the **Logon as a service** security policy, or there's another policy denying the **Logon as a service** privilege to the corresponding service account.
6565

6666
You might also see the following error event in the System event log:
6767

@@ -143,7 +143,7 @@ This behavior can be caused by different reasons. Here are some possible causes:
143143
The error message might vary. Commonly, the error message can be "Unable to configure the RD Session Host Server \<ServerName\>. Invalid Operation."
144144

145145
> [!NOTE]
146-
> Here's a list of common GPOS that might cause this behavior, but we recommend removing any RDS-related GPOs and testing:
146+
> Here's a list of common GPOs that might cause this behavior, but we recommend removing any RDS-related GPOs and testing:
147147
>
148148
> * **Require user authentication for remote connections by using Network Level Authentication**
149149
> * **Set client connection encryption level**

0 commit comments

Comments
 (0)