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 09:44:10 -06:00 committed by GitHub
parent 95496c68f7
commit 2f929f4ecd
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
> 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 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. >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. >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.