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

Update connect-to-remote-aadj-pc.md

Browse Source 
Changing the wording explaining Admin privileges requirements to run PowerShell to add user to local group
This commit is contained in:
Sergii Cherkashyn 2022-01-14 11:51:17 -05:00 committed by GitHub
parent 6232c9f066
commit 84842e36b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -55,7 +55,7 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu
``` ```
where *the-UPN-attribute-of-your-user* is the name of the user profile in C:\Users\, which is created based on the DisplayName attribute in Azure AD. where *the-UPN-attribute-of-your-user* is the name of the user profile in C:\Users\, which is created based on the DisplayName attribute in Azure AD.
This command only works for AADJ device users already added to any of the local groups (administrators). In order to execute this PowerShell command you need to already be added local Administrators group.
Otherwise this command throws the below error. For example: Otherwise this command throws the below error. For example:
- for cloud only user: "There is no such global user or group : *name*" - for cloud only user: "There is no such global user or group : *name*"
- for synced user: "There is no such global user or group : *name*" </br> - for synced user: "There is no such global user or group : *name*" </br>