From 07aa9914e0f7b26195c751f217439c07a8f61caf Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 14:34:00 -0600 Subject: [PATCH] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 5585ff163e..0ab77950b7 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -46,7 +46,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo >`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 only works for AADJ device users already added to any of the local groups (administrators). - > Otherwise this command throws the below error. For example: + > 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" >