deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Command for adding users into RDP group doesn't work

Browse Source 
This command works only for the user , who already added into the AADJ device any of the local group (administrators)
Otherwise this command throws the below error. For example: 
 for cloud only user --> "There is no such global user or group : Azuread\Shenry"
for synced user -->"There is no such global user or group : baz\user2"
This commit is contained in:
NagaCSC 2019-10-08 18:56:19 -06:00 committed by GitHub
parent 87db4dd55d
commit aeeb4a1a27
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
windows/client-management/connect-to-remote-aadj-pc.md
View File

@ -44,7 +44,11 @@ From its release, Windows 10 has supported remote connections to PCs that are jo
>You can specify individual Azure AD accounts for remote connections by having the user sign in to the remote device at least once and then running the following PowerShell cmdlet:
>
>`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD.
>
> This command works only for the user , who already added into the AADJ device any of the local group (administrators)
Otherwise this command throws the below error. For example:
for cloud only user --> "There is no such global user or group : Azuread\Shenry"
for synced user -->"There is no such global user or group : baz\user2"
>In Windows 10, version 1709, the user does not have to sign in to the remote device first.
>
>In Windows 10, version 1709, you can add other Azure AD users to the **Administrators** group on a device in **Settings** and restrict remote credentials to **Administrators**. If there is a problem connecting remotely, make sure that both devices are joined to Azure AD and that TPM is functioning properly on both devices.