deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

corrected per product group feedback

Browse Source
This commit is contained in:
Jeanie Decker 2019-03-29 12:16:20 -07:00 committed by GitHub
parent 8b78780b21
commit d487fcb110
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
windows/client-management/connect-to-remote-aadj-pc.md
View File

@ -41,13 +41,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo
>[!NOTE] >[!NOTE]
>You can specify individual Azure AD accounts for remote connections by having the user sign in to the remote device at least once and then running the following PowerShell cmdlet: >You can specify individual Azure AD accounts for remote connections by having the user sign in to the remote device at least once and then running the following PowerShell cmdlet:
> >
>`net localgroup "Remote Desktop Users" /add "AzureAD\FirstnameLastname"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD. >`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD.
>
>Depending on the chosen identity model, Cloud-only or Federated, you will need to use:
>
>`/add "AzureAD\the-UPN-attribute-of-your-user"`
>`/add "the-UPN-attribute-of-your-user"`
>`/add "the-SAMAccountName-attribute-of-your-user"`
> >
>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.
> >
@ -56,7 +50,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo
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\<AzureAD UPN>`. In some Windows builds, the *AzureAD* prefix is no longer required. You can just use your *AzureAD UPN*. >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.
## Supported configurations ## Supported configurations