I'm trying to configure both a desktop wallpaper and BGInfo through Group Policy. The wallpaper policy uses the local copy option and is linked to users, while BGInfo runs from a batch file as a user logon script. The files are stored in separate folders under the domain's SYSVOL scripts path. I configured BGInfo to preserve the existing wallpaper, expecting the policy wallpaper to apply first and BGInfo to add its system information over it. Instead, BGInfo only works when the wallpaper policy is unlinked. Is there a reliable way to make both work together, or do they conflict by design?
3 Answers
BGInfo generates a new wallpaper image rather than placing a live layer over the existing desktop. If the wallpaper policy reapplies after BGInfo runs, it can replace the generated image; if BGInfo runs afterward, it may also detect or overwrite the policy-managed wallpaper. A more reliable approach is to have the logon script copy the desired wallpaper locally, run BGInfo against that image, and then set the resulting image as the user’s wallpaper. You may also need to control the execution order or add a short delay so Group Policy finishes first.
Many teams have moved away from BGInfo because it can expose useful system details to anyone viewing the desktop and it is another executable to maintain. If the goal is troubleshooting, a shortcut to a small system-information tool or a script that displays only the needed values may be safer and less disruptive.
The main reason I wanted it was to let users and support staff quickly verify the computer name and a few basic details without opening other tools. I’ll look into a more limited or PowerShell-based alternative.
Consider replacing BGInfo with a PowerShell-based solution that writes the computer name and other required details onto a copy of the wallpaper, then sets that generated file as the desktop background during logon. A PowerShell module such as PowerBGInfo can automate this and work with a chosen image, but test it carefully before deploying it broadly.
The “keep wallpaper” option generally means BGInfo will use the current wallpaper as its background when creating its output image. It does not create a separate overlay that remains independent of later wallpaper policy refreshes.