But, uhmmmm that screen is not a GPO, which is done at the domain level.
You are showing GPP at the client level. Why are you doing per client via script vs at the domain so as machines are added to the domain, and user login, it's automatic? GPP of course in the way to go.
You cannot use New-Gpo for a local GPP setting. The PowerShell docs for that cmdlet specifically states...
New-GPO
Description The New-GPO cmdlet creates a GPO with a specified name. By default, the
newly created GPO is not linked to a site, domain, or organizational unit (OU).
# get function / cmdlet details
Get-Command -Name New-Gpo -Syntax
(Get-Command -Name New-Gpo).Parameters.Keys
Get-help -Name New-Gpo -Full
Get-help -Name New-Gpo -Online
Get-help -Name New-Gpo -Examples
In linking the GPO, you have to fully qualify the target and permissions. Again the above doc shows the following example...
new-gpo -name TestGPO |
new-gplink -target "ou=marketing,dc=contoso,dc=com" |
set-gppermissions -permissionlevel gpoedit -targetname "Marketing Admins" -targettype group
There is a tool you can get to assist here and they provide a sample scrip to do GPO drive mapping. See this...
Automating Group Policy Preferences Drive Mapping with PowerShell [VIDEO]
They sell a tool for this use case called...
'Group Policy Automation Engine (GPAE)'
SDM Software’s Group Policy Automation Engine (GPAE) provides the
industry’s only PowerShell interface for automating the reads and
writes of Group Policy settings.