I've been spending a bit of time recently thinking about wallpapers and lock screens for domain computers. For a long time I've used a static image for the computer's lock screen and then BGInfo for the user's wallpaper. The problem is that, at least in my experience, BGInfo seems to fail for everyone's first logon to a machine. This leaves users with the default Windows 10 wallpaper which isn't bad, but it isn't the branded photo they should be getting.
So to cut a long story short I decided it was time to find a new way of doing wallpapers, and ideally creating a lock screen image with the computer's hostname on it.
PowerShell is what I wanted to solve this issue with. I knew it could modify images and figured it could be used for this. Logon and Startup scripts have been pretty reliable for me in the past so I wanted to bring that reliability to this problem.
As with all things I hopped on Google before I started and found this post on EduGeek giving me exactly what I needed. Following on from that the author had created a GitHub repository with their latest code in. With some minor tweaks to the code I got it to spit out an image which was great but it didn't work quite as well as I wanted.
The first issue I had with it was purely cosmetic, a transparent box background was not an option. As we had one image to work with it's easy to pick a suitably contrasting colour.
The second problem was that it needed you to edit the
.ps1 file to change the settings. Not an issue for me but within Ed-IT Solutions I like to operate a no code edits system where scripts always take no more than 2 or 3 options to do a job.
What I'm leading up to here is that I've created my own script. Full Credit to DJ-1701 for their original work, its safe to say I wouldn't have this script working as well as it does without the leg up they gave me.
The big difference is the way it accepts config. My script uses a
.ini file like the one below to configure the output.
I also swapped out the system for getting the screen resolution to one that uses a WMI query. Might be less reliable than the original method but all my test machines haven't had an issue with it, and it works both at boot and during logon removing the need to dump the values into registry.
1[files]2; Background image to use. @@ is replaced with the scripts execution point. ## is replaced with the temp directory3inputImage = "@@\wallpaper.jpg"4outputImage = "##\user.jpg"5; Apply the image as the current users wallpaper. 1 for yes, 0 for no6applyToUser = 17[header]8; The text to display, use # to create a new line.9; Variables:10; %user - The current username.11; %computer - The Computers Hostname.12; %time - The time at generation, time of logon or boot13text = Ed-IT Solutions (UK) Ltd.##User: %user#Computer: %computer14textSize = 1215textRed = 25516textGreen = 25517textBlue = 25518textAlpha = 25519boxRed = 020boxGreen = 021boxBlue = 022boxAlpha = 023; Allowed values left,center,right24alignment = right25[footer]26; Same as header.text27text = Logged On: %time28alignment = left
The above file would create an image and apply it to the current user's wallpaper. Setting
0 would turn this off and have it only save the output to a file.
This gives a single script to run both lock screens and wallpapers as its simply down to the ini file used. To supply an ini file the script takes an option of
-ini <path> where
<path> is the path to the ini file.
The scripts are only half of the battle, getting it out to every computer is just as important.
As with BGInfo I used GPP Files to copy
wallpaper.jpg to the C drive of every computer. In my case I always have a folder in the root of C that matches the domain name, so
arcath.net would become
C:\Arcath which is I where I copied them to.
PowerShell needs some setup before it can run scripts without warnings. In a GPO I set Computer Configuration / Policies / Administrative Templates / Windows PowerShell / Turn on Script Execution to Allow local scripts and remote signed scripts. This is where copying the scripts to each machine becomes nessasary as if you run them out of
NETLOGON they would need to be signed.
If you download the script directly from GitHub you might find that Windows flags it as a remote script even if its copied to each computer. You can fix this by going into properties of the script on the server and ticking Unblock
Once all the files are deployed its then a simple matter to use a GPO to add a Start-up and Logon PowerShell script. I found that trying to use
$PSScriptRoot doesn't work as expected in start-up and logon which resulting in errors. So whilst there is an option to use it in the file paths I don't and instead specify the full path to the wallpaper.
## to use the temp directory works fine which I use in the output of users wallpapers.
With all that I'm now getting reliable images generated every logon and startup.
Some examples of the output.
A Lock Screen:
A users wallpaper:
All content is my own unless otherwise stated.
My content is licensed under the CC-BY-NC-SA 4.0 license