I am working on this very same problem, and what I've got so far is a partial solution. First we restrict what the background can be via Local Group Policy. This ensures that even when a user is not connected to the domain (via a local user profile) there background is still locked down. To side step this I created a script (which I will share once I get back to work) that copies bginfo.exe and the custom.bgi to the system32 folder, and then I use sc to create a service called bginfo with local system privileges. I also add a description in the event I die or am fired other sys admins will know what it is and what it does. Hmmm, maybe I should take that out, huh? I digress; the final piece is where I am caught. I want the service to either start Automatically or at Boot and call the custom.bgi into action. Now keep in mind that using Local Group Policy you have to point it the bgi.bmp, or tell the custom.bgi to overwrite the .bmp file you Local Group Policy points to. So having said all that is there anyone who can tell me how to get the service to perform the necessary action? I have contemplated putting a shortcut in the “All Users Startup Folder” with the necessary switches. But I’d rather have a more polished registry fix or service call.
Robert
"Otis, a strong man stands up for himself, a stronger man stands up for others."
Army Strong!