My Profile Photo

An IT Engineer with a love for all things IT including (but not limited to), Microsoft Azure, Automation and Service Management!

BgInfo Configuration & User Deployment using Group Policy


BgInfo is beneficial for Endpoint device support by displaying the Asset number, IP address and logged on username overlaid on top of the wallpaper, it is OS independent and can be used across other Windows Desktop and Windows Server environments.

BGInfo is a free Windows Sysinternals utility created by Microsoft engineer, Mark Russinovich.

This utility runs under the user’s context. This does not need admin rights. As such this we will create this as a User Based group policy which runs upon logon.

How do I create a BGInfo package?

Use the following guide to create the BG Info package…

Download BGInfo –

Run and extract it to a folder – for example c:\temp\bginfo

Run BGInfo, you will be prompted with the default configuration

You can delete the Fields from the Black window, as applicable in this example we are just going to use x3 fields:

Host Name:    

IP Address:    

User Name:    

To add more you can select Fields, and Add. If there is a field that you may need, that isn’t selectable from the defaults you can also query Environment Variables, Registry and WMI by clicking on the Custom button. We are sticking with the defaults so click Apply to review changes.

We want to also replace the Background so it isn’t the default – Black color – so click on Background…

Because this will be rolled out to multiple users, we either need to have a BMP or JPG that will be on every single computer in the same location or accessible to all authenticated users on the network. We will be going with option 2 – using the domains namespace, and net logon folder to store BGInfo and the wallpaper. Copy the Wallpaper you want to an easily accessible share that authenticated users have Read access too. I am using a Wallpaper folder, under the Net Logon folder.

Select navigate to: \DOMAIN\netlogon\Wallpaper\Desktop.jpg and select Stretch as the Wallpaper position and click Ok.

For future wallpaper changes. This will need to be modified again to point towards the newest wallpaper. Click Apply

Verify that the settings are correct and it looks ok. If so now we need to save the configuration so it can be reused – click on File and select Save As.

Name it: config.bgi

Restart your computer to lose the changes and you can now test the configuration file from the Command Line, open PowerShell or Command Prompt (as a normal user) and navigate to the place where the BGInfo executable and you have saved the configuration file too and type:

bginfo.exe config.bgi /accepteula /silent /timer 0

Press Enter and that should force BGInfo to load with your changes without any user prompt.

How do I deploy BGInfo package?

Use the following guide to deploy the BG Info package. Because this is a user based application and needs to run under user context on login, we are going to use a logon script using a user based group policy – for specific users only.

Open Active Directory Users and Computers and create an application group to assign users too that you want to have the BGInfo wallpaper – for example _APP_BGInfo and add your user account to that group.

Open Group Policy Management tool using an account that has access to create Group Policies and right click on the OU with your user account or Computer – if you have Loopback enabled and select Create a GPO in this domain, and Link it here…

Specify a name for the Group Policy, such as BgInfo-UserPolicy –and click Ok

Right click and Policy and select Edit…

Navigate to: User Configuration\Policies\Windows Settings\

Click on: Scripts (Logon/LogOff)

Double click Logon to open the Logon Properties

I prefer to keep my scripts, source files replicated across Domain Controllers and located in the same location as my Group Policy – so click Show Files…

Copy your BGInfo executable and configuration file into the folder. If you get errors, you may need to launch Explorer or map a drive using Domain Admin credentials which usually has write access to the SYSVOL.

Now we need to create a batch script, that will be ran by the group policy to launch BGInfo. Right click a blank space in the folder and select New, Text Document

Rename file to: Run_BGInfo.bat

Right click bat file and Open with, Notepad

Go back to Windows Explorer; we now need to get the Group Policy location/path. Right Click on the Address pane and select ;Copy as Text

Enter in the following detail (the \DOMAIN till the Logon path is the location of your Group Policy, copied from Step 13) and click Save:

@echo off

\DOMAIN\SysVol\\Policies{8BBCd98E-4907-4D45-B662-8034A55B0352}\User\Scripts\Logon\Bginfo.exe \DOMAIN\SysVol\\Policies{8BBCd98E-4907-4D45-B662-8034A55B0352}\User\Scripts\Logon\config.bgi /accepteula /silent /timer 0


Double click the Run_BGInfo.bat to confirm it works, and if not modify the batch script to work – it needs to point towards the exact BGInfo and configuration file and to avoid extra spaces it may be best to run it on the same line with a space between BgInfo.exe and the path to the configuration file only.

Once it has confirmed working, go back to the Group Policy created in Step 3 and before we add the script we need to set the Scope so the policy doesn’t affect users that are not supposed to be get the BGInfo wallpaper.

Under the Scope tab, remove Authenticated Users from the Security Filtering and add the Active Directory group created earlier – ie _APP_BGInfo – also check the Delegation Tab and make sure Authenticated Users is added for Read Rights.

Now right click the BGInfo group policy – select Edit and navigate back to: User Configuration\Policies\Windows Settings\

Click on: Scripts (Logon/Logoff)

Double click Logon to open the Logon Properties

Click Add and Browse

Select Run_BGInfo.bat and click Open and click Ok

You have now successfully created the User base policy that will run the Run_BGInfo.bat script on user logon

Restart and verify that your Desktop wallpaper has now been changed. Other users of the Active Directory group will need to restart or Log off and back in – to pick up the changes.

comments powered by Disqus