deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 11:53:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #2950 from VLG17/patch-2

Browse Source 
update to reflect Cloud-only or Federated identity model
This commit is contained in:
Jeanie Decker
2019-03-29 12:16:57 -07:00
committed by GitHub
parent 82977b7f47 d487fcb110
commit feba817289
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -41,7 +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.
> >
>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.
> >
@ -50,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: `AzureADName\YourAccountName`. >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