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

Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
This commit is contained in:
ImranHabib 2019-11-03 22:55:31 +05:00 committed by GitHub
parent 2c317cf4a1
commit d88962d915
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -53,7 +53,7 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu
4. Enter **Authenticated Users**, then click **Check Names**. If the **Name Not Found** window opens, click **Locations** and select this PC. 4. Enter **Authenticated Users**, then click **Check Names**. If the **Name Not Found** window opens, click **Locations** and select this PC.
> [!TIP] > [!TIP]
>When you connect to the remote PC, enter your account name in this format: `AzureAD UPN`. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant. > When you connect to the remote PC, enter your account name in this format: `AzureAD UPN`. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant.
> [!Note] > [!Note]
> If you cannot connect using Remote Desktop Connection 6.0, then turn off new features of RDP 6.0 and revert back to RDP 5.0 by tweaking a few changes in the RDP file. See the details in the [support article](https://support.microsoft.com/en-ph/help/941641/remote-desktop-connection-6-0-prompts-you-for-credentials-before-you-e). > If you cannot connect using Remote Desktop Connection 6.0, then turn off new features of RDP 6.0 and revert back to RDP 5.0 by tweaking a few changes in the RDP file. See the details in the [support article](https://support.microsoft.com/en-ph/help/941641/remote-desktop-connection-6-0-prompts-you-for-credentials-before-you-e).