So why do you care about a program that is not even officially supported?
You can also save information from BGInfo to a text file or even a database without even displaying on the desktop, so if you are looking for a quick way to capture information on all the computers in your network, you can use BGInfo and some batch scripts to solve your problem.
It’s worth noting that BGInfo displays information by writing text over top of your wallpaper, if you have wallpaper set.
When nurses and doctors switch from one physical client to another (typically stationary thin or zero clients), Bg Info’s values are not updated and were now displaying stale IP/MAC values for the physical client.
The secondary problem was that monitor resolutions vary, sometimes forcing the Bg Info content out of view.
For example, if you are running a server or you are an IT professional, it will provide you valuable data at a glance.
There are several customizable parameters such as, but not limited to, Boot Time, IP Address, DNS Server, Domain, Storage, RAM, etc.
Additionally, the Help Desk could ask a user to run “gpupdate” to refresh Bg Info at will. When a user logs into their VMware View desktop from another location, Event ID 25 (Log: Microsoft-Windows-Terminal Services-Local Session Manager/Operational; Source: Microsoft-Windows-Terminal Services-Local Session Manager) appears in the virtual machine’s Event Logs.
If I could get Bg Info to run every time this event occurred in the logs, then the Bg Info would remain accurate as the user moves from one location to another.
The solution was to leverage Group Policy Preferences, Scheduled Tasks, and Event Logs.
I wanted to use these three tools to trigger Bg Info to run whenever a user moved their VMware View virtual desktop from one location to another. Open your Group Policy Management Editor, create a new Group Policy, and click Edit.
However, the program generates the background image only when the settings are applied after a reboot (or shutdown).