Bginfo Rollout

A[L]C · 2 Oct 2006 at 15:43

Has anyone ever rolled out BGinfo?

Ive been tasked to investigate the best way. We have about 1200 machines, running either XP or 2k. One thing is group policy is currently blocking users from changing their wallpapers. How does it work with bginfo though?

Thanks

The_KiD · 2 Oct 2006 at 16:07

Hi ALC,

We recently rolled out bginfo accross our 80 site network, I did it through a basic login script and because it is done this way it didnt matter that users werent allowed to change their desktop pic.

Here is the section of our login script:

Code:

REM =====================Check for and install BGInfo================

IF %computername% == LCH-CTX GOTO BGEND ELSE
IF %computername% == LCH-CTX2 GOTO BGEND ELSE
IF %computername% == LCH-CTX3 GOTO BGEND ELSE

IF EXIST "c:\bginfo\Bginfo.exe" GOTO BGCOPY2 ELSE GOTO BGCOPY

:BGCOPY
	MD c:\bginfo
	COPY "\\serverfile\itdept\utilities\bginfo\bginfo.exe" "C:\bginfo"
	COPY "\\serverfile\itdept\utilities\bginfo\bgsettings.bgi" "C:\bginfo"
	COPY "\\serverfile\itdept\utilities\bginfo\*.ver" "C:\bginfo"
	GOTO BGCOPY2

:BGCOPY2

IF EXIST "c:\bginfo\120406-01.ver" GOTO BGCOPY3 ELSE
	COPY "\\serverfile\itdept\utilities\bginfo\bgsettings.bgi" "C:\bginfo"
	COPY "\\serverfile\itdept\utilities\bginfo\*.ver" "C:\bginfo"
	GOTO BGCOPY3

:BGCOPY3
IF EXIST "c:\documents and settings\%username%\Start Menu\Programs\Startup\bgshortcut.lnk" GOTO BGEND ELSE

	COPY "\\serverfile\itdept\utilities\bginfo\bgshortcut.lnk" "C:\Documents and Settings\%username%\Start Menu\Programs\Startup"
	C:\bginfo\bginfo "C:\bginfo\bgsettings.bgi" /TIMER:00

:BGEND
REM =====================\END\========================================

The first part was making sure it didnt set it for our citrix users, but it does work for them if needed.

Then it checks to see if bginfo is actually there already and if it is it makes sure it is the right version. If not it sticks it on and configures it for the user.

The .ver file is just a txt file with the bginfo settings in that we made just to track if we made changes.

A[L]C · 2 Oct 2006 at 16:33

cool thanks. A few problems that I can see. First one is a biggy. The majority of users do not have access to their local hdd. I think this means the script is going to fail on a copy.

What OS do your machines run?

A[L]C · 3 Oct 2006 at 11:07

The_KiD · 3 Oct 2006 at 12:56

sorry missed it!

We use Win2K, but if they dont have access to their local disk, then I am sure you could just drop the files in their user area too.

We always keep some part of the local disk the user can access just for this situation.