Windows 7 Pro Lock screen not applying.



  • I've been using C:\Windows\System32\oobe\info\backgrounds\ to drop in my custom Ctrl+Alt+Del Lock page wallpaper on about 60+ machines so far. Every time it applies instantly. I've come across one machine, however, that will not apply the change.

    I was looking into alternative ways to do this with the Registry, involving a navigation to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background, and selecting the OEMBackground value and changing the hexadecimal to 1 from 0 to kick things off... (I thought maybe, just maybe this instructor had somehow figured out how to set this, and that it would take precedence over my change), but when I double checked this value on the machine that will not apply the wallpaper, this value is still 0.

    Now, I know I could still use this last method, but not knowing why it's not applying is killing me.

    Anyone have any experience with this issue and might be able to explain why it wouldn't take?

    Also, I have tried restarting, shutting down, logging off, switching users to admin and trying, but none of these things have worked so far.

    Happy Friday.

    EDIT: I noticed the desktop wallpaper that's been assigned via right-click>set as desktop background kept dropping off to the default Windows 7 wallpaper upon reboot, so I set that in local Group Policy to pin it down for now. There is something fishy going on here. Ran sfc /scannow with Admin privileges but came up negative.



  • Are the correct permissions set on the folder in question?



  • @dashrender Yes. First thing I checked.



  • Anything on the event logs?



  • @dbeato Sorry, haven't had time to give this any more attention. I'll look at it today again and get back :D



  • Are you applying this to all machines via AD Group Policy? Or are you setting this locally on each computer?



  • One of the windows 10 major updates, 1607 or 1511 dropped the ability to set lock screen via GPO from Pro version, if I recall this correctly. When in doubt, nuke Windows from the orbit, and start over. It's usually quicker than trying to figure out why things don't work.



  • The lock screen is and can be different. I have our stations setup to use a custom image for the lock screen, and a custom image for the desktop wallpaper.

    I apply the lock screen very similar to the way you do:
    A custom image located here:
    C:\Windows\System32\oobe\info\backgrounds\backgroundDefault.jpg

    AND using an accompanying registry key:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background]
    "OEMBackground"=dword:00000001

    I apply the wallpaper like this:
    A GPO (settings "enabled"):
    Computer Configuration \ Policies \ Administrative Templates \ System/Group Policy \ "Configure user Group Policy loopback processing mode" = Enabled (Merge)

    User Conifguration \ Policies \ Administrative Templates \ Control Panel/Personalization \ "Prevent changing desktop background" = Enabled

    User Conifguration \ Policies \ Administrative Templates \ Desktop/Desktop \ "Desktop Wallpaper" = Enabled (C:\Windows\lmi_deskwall.jpg / Wallpaper Style: Stretch)

    My last two cents: The registry value needs to be set to "1" in order to force the custom lock screen image.



  • @shuey So I just figured this out this morning, and came back on here to tell you all I figured it out.

    I did have to set that registry value to 1. The confusion came when all those 60+ machines I was applying the change to were already set up from factory as having the oobe\info\backgrounds directory made and registry value was already 1 on those machines. So when I encountered a machine that didn't have it already, I thought something was wrong.

    Thanks for the reply!



  • @g-i-jones Glad you got it worked out! :)



  • @g-i-jones said in Windows 7 Pro Lock screen not applying.:

    e already set up from factory as having the oobe\info\backgrounds directory made and registry value was already 1 on those

    ewwww - a factory image?


Log in to reply
 

Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.