From 88de3332688b11a2ab5a2a1c1a8fb9b33be8966d Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 14:34:41 -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 0ab77950b7..6c1b6665b6 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -48,7 +48,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 synced user -->"There is no such global user or group : baz\user2" + > 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. >