From 2f929f4ecdb0b0d86553113afebba5e078044d81 Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 09:44:10 -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 7d283eab8a..6ebfba5fa3 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 > 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" -> + > >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.