LinkBack URL
About LinkBacksrunning BGInfo in startup script works well, I run this on all workstation (Servers have their own one).
Command Line used:
bginfo.exe CNCSWorkstations.bgi /timer:0 /silent /nolicprompt
running BGInfo in startup script works well, I run this on all workstation (Servers have their own one).
Command Line used:
bginfo.exe CNCSWorkstations.bgi /timer:0 /silent /nolicprompt
Cheers, saved me doing the testing!!
@RichardDS how did you change the logon picture please?
I see Richards been attacking Gina
and FN-G, easiest solution on KVM, bright coloured background with the server name on below where the "this computer is logged on and locked" message goes works well. Or just get a KVM that supports names as mine does.
@FN-Greatermanchester - BGInfo can alter the default login wallpaper to make KVM use easier, you just run it in GUI mode and click on the "Desktops..." button you can then select which desktop to apply the background to. You could also use the above command lines and add the /all switch to them which will apply the background to all desktops(user, login, terminal services login)
We use the security settings on group policies to change the security of the bginfo.bmp so that auth users can change the bitmap.
I'm having a bit of bother with this.
It works and looks fantastic. But once deployed, it doesn't always appear for users.
I've created a MSI which deploys the .exe my config and a wallpaper to a folder on the C Drive.
I've then got a startup batch file that runs the .exe (as a Startup via GPO)
Is there anything wrong with that?"C:\HABSBOYS\BGInfo\bginfo.exe" "C:\HABSBOYS\BGInfo\HABSBOYS.bgi" /timer:0 /silent /nolicprompt
You could try running it from a network share?Originally Posted by Arcolite
It works from it's current location, I can see everything I have set on the login screen, but when I log in as a user, I get nothing but the usual Blue Desktop.
You need to add the /all switch to the end of your command as this is what applies it to the login, default user and terminal services background as well. Your current command will only apply it to the active user desktop. probably the login background as that is the user that has context at startup. You also want to make sure that there is not anything in Group policy that specifies a background that is over-riding your BG on a user basis.
Perfect, thanks for the pointers.
I've now got it sorted.
We wanted certain User specific data shown on the desktop (Logon Server, Username...) so we've created two profiles. One for the desktop and one for users.
On Startup it applies the Desktop and on Logon it applies the User one.
When the user logs out the Desktop one is re-applied.
Hmmmm - same problem as Arcolite, I used to use this to ID servers in my last job on Citrix farms so it was rather good.
A little odd why it does not work on a simple 2003 AD Domain. I get mine to run but then it displays errrrrrrrr nothing. Even with the /all switch...
HA HA HA - been playing around a bit more with this, I now have 2 sets of BGinfo on top of each other !!!
Have you tried running it in GUI mode while applying to all desktops to see if it spews an error at that point, maybe dropping the /quiet switch for testing if you are running it at machine start.
If this doesn't shed any light on it you could try running it with both Filemon and Regmon running which should tell you if there are any file or registry permissions getting in your way.
When I run this on servers I usually add the command line to the Run section of the registry so that it is run each time the system is logged in.
Mattx, Have you set the option that controls where it tries to save the new bmp? It uses the windows folder by default but you can save the bgi with the user profile set instead.
Yeah I changed that to the users app data dir which is re-directed to their home directory....Mattx, Have you set the option that controls where it trys to save the new bmp?
I did get an error message stating it would only run in Admin mode but sorted that, it then ran, but displayed nothing.Have you tried running it in GUI mode while applying to all desktops to see if it spews an error at that point, maybe dropping the /quiet switch for testing if you are running it at machine start.
I did have it working though, but it only showed the info when the user logs off !!! It works fine for an Admin though which is odd.....
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
