Login Screen background

[alfatec]

Does anybody know if they have fixed the login screen background in 1703 yet, holding back from upgrading until this is fixed. 1511 and 1607 work fine.

[3s-gtech]

https://partnersupport.microsoft.com/en-us/par_clientsol/forum/par_win/lock-screen-not-changing-as-per-gpo-in-1703/f002961c-f6fe-4592-a963-13bd0cb55863?auth=1 Edited May 23, 2017 by 3s-gtech

[alfatec]

Thanks for that, hopefully will fix it.

[alfatec]

Looks like the update has been delayed as it was not released.

[thebicesterschool]

well the update finally came out on the evening of 25th May, and the fix for this isn't working properly as far as i'm concerned.

If you build a new machine, update it, then add to the domain, when it receives the logon/lock wallpaper gpo it applies successfully, so that part is fixed.

however if you update an existing domain joined machine, the update installs successfully and afaik fixes a few bugs (scroll bar on logon being one of mine), but the wallpaper is still not fixed.

 

I'm not rebuilding 90 machines that already have this policy

 

guess we'll have to wait another month for them to fix it properly, this issue and Edge browser being a totally unresponsive pain, are the only things holding the rest of my deployment back.

[thebicesterschool]

I should also add, changing the gpo wallpaper file/name etc doesnt kick it into action (seen that work before on various file related policy settings over the years), neither does setting the policy to copy/replace the wallpaper file - should you choose to copy the file to the machine then apply via gpo, rather than point to a file on a server.

Not that we should have to try these common workarounds in the first place.

 

oh, and the bug doesn't seem to be hardware specific, tried a VMware test, physical test on a dell optiplex 380, and dell optiplex 3020.

[Spence_101]

Yup... not working here either. Incredibly annoying!

[Spence_101]

Can people please add your voices to here?

 

MS are under the impression it is fixed...

[3s-gtech]

I now have it working again, fully automated but clunky. The GP setting is still used, so if you set that as you did for 1607, you then need to:

 

Change the ownership and permissions on HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen using Computer Configuration/Policies/Windows Settings/Registry

 

 

Select "Configure this key then: Propagate inhertiable permissions to all subkeys". Make the Owner the current account you're logged onto GP with and set Everyone to have write access to the key (or lock this down to an account if you're bothered).

 

Now go to Computer Configuration\Preferences\Windows Settings\Registry.

 

Create Delete entries (with the "Apply once and do not reapply" flag under Common) for these keys:

 

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\CacheFormat_P

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\GPImagePath_P

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\SizeX_P

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\SizeY_P

 

 

Note I have another key which forces the lockscreen here (HKLM\SOFTWARE\Policies\Microsoft\Windows\Personalization\LockScreenImage - REG_SZ \\networkpathtoimage.jpg. Up to you if you want to try this, but it shouldn't be needed.

 

Now test on a client that is running an up to date version (I have only tested with the 2017-06 updates so far). Your lock screen should now work without having to re-visit workstations.

Edited June 15, 2017 by 3s-gtech

[Spence_101]

I now have it working again, fully automated but clunky. The GP setting is still used, so if you set that as you did for 1607, you then need to:

 

Change the ownership and permissions on HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen using Computer Configuration/Policies/Windows Settings/Registry

 

[ATTACH=CONFIG]43865[/ATTACH]

 

Select "Configure this key then: Propagate inhertiable permissions to all subkeys". Make the Owner the current account you're logged onto GP with and set Everyone to have write access to the key (or lock this down to an account if you're bothered).

 

Now go to Computer Configuration\Preferences\Windows Settings\Registry.

 

Create Delete entries (with the "Apply once and do not reapply" flag under Common) for these keys:

 

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\CacheFormat_P

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\GPImagePath_P

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\SizeX_P

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SystemProtectedUserData\S-1-5-18\AnyoneRead\LockScreen\SizeY_P

 

[ATTACH=CONFIG]43866[/ATTACH]

 

Note I have another key which forces the lockscreen here (HKLM\SOFTWARE\Policies\Microsoft\Windows\Personalization\LockScreenImage - REG_SZ \\networkpathtoimage.jpg. Up to you if you want to try this, but it shouldn't be needed.

 

Now test on a client that is running an up to date version (I have only tested with the 2017-06 updates so far). Your lock screen should now work without having to re-visit workstations.

 

Would this work if you changed the lockscreen again? Or would you need to re-delete those 4 keys?

 

Thanks

[3s-gtech]

It'll work if you leave the Group Policy applied, though you may have to remove the "Apply once and do not reapply" flag.

[alfatec]

Have tried the fix on 3 computers with 1703 on but I only get a single colour screen after applying.

[3s-gtech]

Do a gpupdate /force on them - I get that then the proper screen applies on refresh.

[alfatec]

Still no joy. Image is showing in the preview, group policy is applied correctly, reg entry removed correctly but still showing single colour.

[3s-gtech]

Hmmmm, not sure then. Have you tried adding the reg entry from my post? There's another step you can do, which is working for me. Set the lock screen image to be C:\Windows\System32\oobe\info\backgrounds\backgroundDefault.jpg in Group Policy - "Force a specific default lock screen and logon image". Then use Computer Configuration/Preferences/Windows Settings/Files/File and target %windir%\system32\oobe\info\backgrounds\backgroundDefault.jpg with your custom background. It seems to work more reliably than a UNC file.