Locking down computer...

Locking down computer...

Post by Mike » Wed, 24 Aug 2005 23:29:35


I have a computer being used by 4-5 different people that recently some of
the users complained that (work-related!) programs wouldn't work.
When looking at it I found more games than I've seen on some kid's
computers! What would be the easiest way to set the computer so no one but
an administrator can install programs? Keep in mind, I have a couple of
programs that need to run under an administrator account, so it seems I'm
kind of caught in the middle here.
Also, when one of the users logs in, she first gets a message:
"Cannot find the file 'C:\DOCUME~1\ADMINI~2\LOCALS~1\Temp\djtopr1150.exe'
(or one of its components). Make sure the path and file name are correct and
that all required libraries are available."
Followed by an "Install Program As Other User" dialog box.
I can hit ok or cancel & things seem to be fine from there, but I'd like to
stop this, as well.
I can't find anything in the startup folder that would appear to be causing
this.
Any suggestions?
 
 
 

Locking down computer...

Post by Mike » Sat, 27 Aug 2005 14:46:27

I have a computer being used by 4-5 different people that recently some of
the users complained that (work-related!) programs wouldn't work.
When looking at it I found more games than I've seen on some kid's
computers! What would be the easiest way to set the computer so no one but
an administrator can install programs? Keep in mind, I have a couple of
programs that need to run under an administrator account, so it seems I'm
kind of caught in the middle here.
Also, when one of the users logs in, she first gets a message:
"Cannot find the file 'C:\DOCUME~1\ADMINI~2\LOCALS~1\Temp\djtopr1150.exe'
(or one of its components). Make sure the path and file name are correct and
that all required libraries are available."
Followed by an "Install Program As Other User" dialog box.
I can hit ok or cancel & things seem to be fine from there, but I'd like to
stop this, as well.
I can't find anything in the startup folder that would appear to be causing
this.
Any suggestions?