Search code examples
windowspowershellkiosk-modewindows-10-desktopsuperuser

Local user account created with Powershell is NOT shown in settings "Family & Other people"


I am working on Windows 10 Assigned Access for Desktop for version 1607.

Mission: I need to get Assigned Access to work with Powershell.

Steps done: I create a new LocalUser account with New-LocalUser and I enable the account with Enable-LocalUser. To check if the account is added, I run Get-LocalUser and see that the account is created (see attachment).

Issue: To double check I go to the PC settings for Accounts-Family & other people, but I cannot see the new local user account "KioskTest".

I have restarted the computer but the account is not added to "Family & Other people".

I have spent some time on this and I would really appreciate your help, How can I make sure that the added Local user "KioskTest" is shown in the PC Accounts settings-Family & other people, when using Powershell?

I can Set-AssignedAccess, when I do Get-AssignedAccess I can see that it is there. Trouble is, I cannot login to the local user account because I cannot find the account in the settings for the PC.

It's like powershell has "hidden" the local user account from my client computer!!!

ADDED information + updated images: After some trial and error I found out the following:

  • Using NET USER username password/ADD --works perfectly! I can find the user account and login as a customer would. The account is part of the LocalGroupMember
  • The local user account created with New-LocalUser with Powershell does NOT appear in the PC account settings BUT if you click on set assigned access in the Family & other people the system finds the local user account (see attachment). However you cannot login to the account as it seemingly does not have a group membership! Not great for testing :(

Thanks for taking the time, Karina

See attachment: Powershell Get-AssignedAccess PC Account settings Family & other people


Solution

  • This isn't really a PowerShell issue and might be better suited for SuperUser. But I would guess that this is an issue with group membership. Unfortunately get-localuser doesn't give membership. So something like this would be the PowerShell way to check which user objects belong to which local groups.

    Get-Localgroup | % { "`n$($_.name)`n"; get-localgroupmember $_}
    

    Then check through which groups other user objects are a member of and add the KioskTest account to that group using this:

    Add-LocalGroupMember -Group "ExampleGroup" -Member "KioskTest"