Update windows/client-management/connect-to-remote-aadj-pc.md

Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com>
This commit is contained in:
NagaCSC 2019-10-15 14:34:41 -06:00 committed by GitHub
parent 07aa9914e0
commit 88de333268
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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). > 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: </br> > Otherwise this command throws the below error. For example: </br>
> for cloud only user --> "There is no such global user or group : Azuread\Shenry" </br> > for cloud only user --> "There is no such global user or group : Azuread\Shenry" </br>
> 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" </br>
> >
>In Windows 10, version 1709, the user does not have to sign in to the remote device first. >In Windows 10, version 1709, the user does not have to sign in to the remote device first.
> >