BGinfo - need to block

[slp]

BGinfo is sent out to all the workstations on our domain. 2003 servers and
XP Pro and W2K workstations.

I'm locking down 6 workstations for the public. I've got them where I want
them but can't get rid of BGinfo. I don't want the public to see the
information it displays.

It was not in add/remove programs. I deleted everything I coulf find in
windows explorer about it. I went into the registry and deleted everything I
could find about it. I went into the domain controller and blocked all
policy inheritance to the OU the computers and user resides in.

How in the world do I get BGinfo off the 6 public access locked down
workstations?

 

[Steve Halvorson]

bginfo does not need to be installed it is called from a script. Check that
there are no login scripts or startup scripts being processed.

 

[nass]

BGinfo is sent out to all the workstations on our domain. 2003 servers and
XP Pro and W2K workstations.

I'm locking down 6 workstations for the public. I've got them where I want
them but can't get rid of BGinfo. I don't want the public to see the
information it displays.

It was not in add/remove programs. I deleted everything I coulf find in
windows explorer about it. I went into the registry and deleted everything I
could find about it. I went into the domain controller and blocked all
policy inheritance to the OU the computers and user resides in.

How in the world do I get BGinfo off the 6 public access locked down
workstations?

Check out the Config file been saved on your System and also remove from the
Startup list.
Also you can send your question here:
How do I remove BGInfo.exe
http://forum.sysinternals.com/forum_posts.asp?TID=6958
BgInfo v4.12
http://technet.microsoft.com/en-us/sysinternals/bb897557.aspx
Try this tool:
http://www.ccleaner.com
HTH.
nass

 

[VanguardLH]

BGinfo is sent out to all the workstations on our domain. 2003
servers and
XP Pro and W2K workstations.

I'm locking down 6 workstations for the public. I've got them where
I want
them but can't get rid of BGinfo. I don't want the public to see
the
information it displays.

It was not in add/remove programs. I deleted everything I coulf
find in
windows explorer about it. I went into the registry and deleted
everything I
could find about it. I went into the domain controller and blocked
all
policy inheritance to the OU the computers and user resides in.

How in the world do I get BGinfo off the 6 public access locked down
workstations?

Don't select to use the BGinfo background for the desktop.

 

[slp]

I blocked all policies from applying to the UO containing these computers and
users. BGInfo still gets through.

Selecting not to use the BGInfo wallpaper only works until the computer
restarts and then it's back again.

Any other thoughts on getting rid of it on these 6 PC's in their oen OU?

 

[VanguardLH]

in message

I blocked all policies from applying to the UO containing these
computers and
users. BGInfo still gets through.

Selecting not to use the BGInfo wallpaper only works until the
computer
restarts and then it's back again.

Any other thoughts on getting rid of it on these 6 PC's in their oen
OU?

Policies push registry entries. The registry is where the screensaver
is specified that gets used. As I recall, BgInfo would create a
screensaver file (.scr). So couldn't you delete the .scr file that
BgInfo created? Then when the domain policy told that host to *use*
the BgInfo .scr file, that file won't be found. I suppose login
scripts could be used to force a rerun of BgInfo to create the .scr
file but then maybe a batch file in the Startup menu could delete the
..scr file. Do you actually push the BgInfo program onto those hosts?
If not, why not just delete the BgInfo program (and its .scr file)?

 

[slp]

I've gotten rid of BGInfo several times and it keeps coming back.

I've changed screensavers. Removed any thing related to BGInfo from the
registry. It keeps coming back.

 

[VanguardLH]

I've gotten rid of BGInfo several times and it keeps coming back.

I've changed screensavers. Removed any thing related to BGInfo from
the
registry. It keeps coming back.

So how many users are allowed to log onto the host? Sounds like
someone is putting back what you want gone. If you are locking down
workstations for the public, why aren't you using kiosk software to
prevent them from ****ing up your setup? Microsoft has their
SteadyState program for free but you might want to look at other kiosk
programs.