Ranger vs. BGINFO
We run BGINFO in a user script that sets the IP address, PC name, and username information in the top right-hand corner. I'm sure this was working when I first started at the school (Sep last year).
During the last few months this has stopped working for student accounts, yet is still working for the rangermanager account.
Specifically, when a student logs in it shows the BGINFO briefly, but it then vanishes. A desktop is set by group policy, but this remains in place.
Any ideas as to why BGINFO is not working for students?
Typically the BGInfo.exe is copied to the C:\Windows directory, although I only used this on XP and dropped it for Windows 7. The likelyhood is that it's a permissions problem.
We have BGInfo doing the same job as you describe but we run it from a central server share without any problems [Students and staff]
Client O/S: Windows 7 Pro: SP1: 64 Bit.
Yes, we run it from a server share: \\vc-dc1\NETLOGON\Bground\bginfo \\vc-dc1\NETLOGON\Bground\W7.bgi /timer:0 /NOLICPROMPT
The original desktop is set via group policy.
Fine on a PC without Ranger. Fine from the rangermanager account. Appears briefly on a student account, and then vanishes. I've tried cloning some of the settings from the rangermanager account, but still can't get it to appear continuously. Odd!
Not familiar with Ranger I am afraid [we are vanilla]
Is ranger doing something after the BGInfo script has run so that the information you want displayed is removed or hidden?
We had something like this happen on XP ages ago but I can't remember the specifics or how we dealt with it [sorry]
I'm guessing it must be doing something, but RM support aren't sure what, and I can't spot anything.
When you created the bginfo file did you set it to create the image in the temp directory.
I'm not sure. The command is as follows: \\vc-dc1\NETLOGON\Bground\bginfo \\vc-dc1\NETLOGON\Bground\W7.bgi /timer:0 /NOLICPROMPT
There doesn't seem to be any mention of where it's created.
The image itself is also taken via group policy from the vc-dc1 server.
I expect the problem is that it is enforcing the desktop image right over the top of the BGinfo - try setting the desktop image in the bginfo settings rather than elsewhere, if only to see what happens.