[1809, ou] Forcea a specific default lock screen and logon image - Still Not Working!

[Fazza]

We have a group policy that sets the logon screen image to that of the school crest/logo etc. It works fine on Windows 8 but doesnt work on Windows 10 - I was hoping whatever the issue is/was would be resolved in Windows 10 1809 but clearly not!

 

Are there additional settings in Windows 10 I need to configure for this GPO to work or is there a new GPO setting somewhere specifically for Windows 10 that I dont know about?

 

[LeMarchand]

Not using 1809, but the below has been working up to 1803 here.

 

[AJWhite1970]

No solution from me I'm afraid but just to say I'm currently building a 1809 LTSC image and that won't take the lock screen image either. 1709 and 1803 did so something (else) has broken in this release.....

[Fazza]

I've just been told the lock screen image GPO works fine at one of our Primary Academies so no idea why it's not working here. The next step I guess is to create a new OU, Block Inheritance and then create a new GPO with just that setting in to see if it's something in another Group Policy affecting this setting or not.

[Fazza]

Just installed W10 1803 and the GPOs work as the Lock Screen Image changes to the Schools crest. The same PC in the same OU with Windows 10 1809 does not work

[AJWhite1970]

Just set in manually on a standalone 1809 LTSC PC with no GPO's associated and that doesn't work either....

[3s-gtech]

Do you have to do the old hack that we worked out last year? http://www.edugeek.net/forums/windows-10/184614-login-screen-background.html

[Fazza]

Getting strange now...

 

I re-imaged the PC to Windows 1803 and the lock screen image Group Policy worked. I did an in-place upgrade to 1809 and it still works! Must have done something in 1803 that remained when I did an in-place upgrade to 1809.

Edited November 21, 2018 by Fazza

[AJWhite1970]

So after playing with this the following does/doesn't work

 

Use the personalization right click menu from the desktop and set a lock screen image - nope (even though it shows a preview of the image)

Use a GPO and set Computer Configuration > Administrative Templates > Control Panel > Personalization > Force a specific default lock screen image.- nope

Login locally, run gpedit.msc and set the above policy - yup (as long as the path is local)

 

Onwards and upwards, one little step forward and several backwards

[Fazza]

Login locally, run gpedit.msc and set the above policy - yup (as long as the path is local)

 

Onwards and upwards, one little step forward and several backwards

 

I wonder what happens if you set a Group Policy to point to a file saved locally - I'm just trying my new 1809 'Golden Image' out so I'll have a look at this tomorrow.

[Fazza]

Not using 1809, but the below has been working up to 1803 here.

 

[ATTACH=CONFIG]51095[/ATTACH]

 

I replicated your settings yesterday, did a gpupdate /force and nothing changed. Despite this I left the Group Policy alone.... Just before I left work I set a PC imaging from my new 1809 SCCM 'Golden Image' and low and behold! This morning I'm greeted with our Academy crest on the logon screen!

 

Seems to have done the trick - just needed to wait for the GPO to sort itself out!

[smithson83]

I believe at some point, maybe 1709, they removed the option for 10 Pro. Only works on Ent or Edu

[LeMarchand]

I believe at some point, maybe 1709, they removed the option for 10 Pro. Only works on Ent or Edu

 

I've been using EDU, so you may have hit the nail on the head there.

[chazzy2501]

I'm using 1703 and it states it's only for enterprise or education, like Direct Access.

 

Also I hid a wookie in the lock screen, no one has seen it yet

 

Edited November 22, 2018 by chazzy2501
add wookie

[Arthur]

I replicated your settings yesterday, did a gpupdate /force and nothing changed. Despite this I left the Group Policy alone....

There was an annoying bug with the lockscreen/login screen on 1803. It's seems this part of Windows 10 is still quite buggy.

 

Windows 10 v1803: Custom login/lock screen image won’t show, until user login

[AJWhite1970]

Setting the lock image as a local admin user with the file on C drive does work for all users in 1809LTSC, and also as I've just discovered, survives a trip round sysprep (as does the credprovhost.dll.mui hack if you are doing that)

 

I think my gold image is good to go, now to find a PE teacher to test it

[Davida1992]

I know this is an older post, but I've spent several hours now after pushing out 1809 and wondering why the login background isn't our corporate background. I was cursing Microsoft thinking that it was an 1809 bug because it was working in our 1803 build and nothing much has changed...

 

After reading these comments though, I checked the Windows version and realised I have based my image off Windows 10 Pro and not Education... I have no idea how I managed to install Pro... Kicking myself now haha :') Changed to Education and all is working now!!

[liamrobbo]

I've been scratching my head for a few days with the same issue, just checked the version and its installed pro for some reason, i'm 99% sure its been set up as Edu on the task sequence using the default WIM file from MS. Will need to investigate now.

[Areku]

Same.. scratching head... task sequence is pushing out Enterprise... yet, machine has pro on it...

[atcoates]

Could the wrong Windows Mak code cause the issue?

[liamrobinson]

Could the wrong Windows Mak code cause the issue?

 

I'm using KMS, but i think my issue is i have a Pro KMS code installed on one of my servers (not sure what yet) and its activating the product against that, i've added the Edu KMS code and ive got 24 activations, hopefully when it reaches 25 it will stop changing back to Pro!

[Arthur]

I'm using KMS, but i think my issue is I have a Pro KMS code installed on one of my servers (not sure what yet) and it's activating the product against that

If you add the product key for Windows Srv 2019 DataCtr/Std KMS or Windows Srv 2016 DataCtr/Std KMS in VLSC, your KMS server will activate the Pro, Education, Enterprise and LTSC/LTSB versions of Windows.

 

https://docs.microsoft.com/en-us/windows-server/get-started-19/activation-19

[Areku]

i dont know why, but after repeated attempts to reimage this machine, it swapped back to pro until i installed the Enterprise key from https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612867(v=ws.11) and used VAMT to activate it.

 

it seems the previous key i was using to activate is able to activate all editions, and in this case repeatedly activated the wrong version (we use the multi installer disks), how every activating it using KMS+that key only allows it to activate Enterprise.