Jun 08 2017 09:27 AM
Jun 08 2017 09:27 AM
Is there a best practice to set default wallpapers and lock screen backgrounds to deal with corporate branding?
There seems to be lots of different methods with a combination of scripts/Group Policy settings. Is there any plans to simplify how to deal with corporate branding when you only have Windows 10 Professional?
Jun 08 2017 09:35 AM
We have had success with using Group Policy to force a specific lock screen for our users. The image file is put on the computer with a setup script that we've been running manually (we are still in a small-scale pilot deployment), but we plan to add that to our SCCM Task Sequence. We aren't speficfying desktop backgrounds, but I imagine it would work just as well.
Jun 08 2017 09:37 AM
I am using GPO for these tasks, but you need to decide where to place the images, if it is on network, you will run in problems if the machine is offline, e.g. screensaver will still lock the machine, but with a black screen. Therefore, we decided to deploy the image set in a msi via ConfigManager (pictures are always named the same) to the clients, but if you run always connected machines calling the pictures from network is working great
Jun 08 2017 09:50 AM
If you want to use images on a network share, then making them always available in Offline Files is an option for disconnected machines. We've done that with shared Office templates and it worked reasonably well, so I'd imagine it would work for lock screen or background images as well.
Jun 08 2017 10:01 AM
Here's our batch file we deploy as an application through SCCM. img100.jpg should be your custom image and in the same directory as the batch file. This overwrites the default images because there isn't just one way to do this depending on the build.
"\Windows\Web\Screen\custom_win10.jpg" is used by a GPO with the Computer > Admin Templates > Control Panel > "force a specific default lock screen and logon image" set
takeown /F C:\Windows\Web\Screen\ /R /A /D Y
ICACLS C:\Windows\Web\Screen\ /grant Administrators:F
ren \Windows\Web\Screen\img100.jpg img106.jpg
copy /B img100.jpg \Windows\Web\Screen\
copy /B img100.jpg \Windows\Web\Screen\custom_win10.jpg
takeown /F SystemData /R /A /D Y
del /Q /F SystemData\S-1-5-18\ReadOnly\LockScreen_Z\*.*
del /Q /F SystemData\S-1-5-18\ReadOnly\LockScreen_P\*.*
Jun 08 2017 12:59 PM
Keep in mind, if you ever run a system file check (sfc /scannow), the images will be restored to the default Windows images.
Jun 08 2017 02:14 PM
It seems like provisioning packages (especially once they get the kinks worked out) would work for this: Provisioning Packages (advanced setup, not basic) are the way to go by way of the Windows Configuration Designer (you can find it in the app store) ...
Runtime settings --> DesktopBackgroundAndColors
Runtime settings --> Personalization --> LockScreenImageUrl