From fbfb5c9526f1e7471b604d7b5b016ec68743803e Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 14:33:50 -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 8fce97a0a4..5585ff163e 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -47,7 +47,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo > > 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: - > for cloud only user --> "There is no such global user or group : Azuread\Shenry" + > 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.