From 631a16f00a2a655c90dd850b90b96153229e43ae Mon Sep 17 00:00:00 2001 From: RavennMSFT <37601656+RavennMSFT@users.noreply.github.com> Date: Tue, 12 Jan 2021 12:21:01 -0800 Subject: [PATCH] Update windows/client-management/connect-to-remote-aadj-pc.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@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 149f0759fe..b0d82b4ca2 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -58,7 +58,7 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu - for synced user: "There is no such global user or group : *name*"
> [!NOTE] - > For devices running Windows 10, version 1703 or earlier, the user must to sign in to the remote device first before attempting remote connections. + > For devices running Windows 10, version 1703 or earlier, the user must sign in to the remote device first before attempting remote connections. > > Starting 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.