Re: Software Restrictions
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 22 Aug 2005 19:39:46 -0500
The software does not have to be installed in the Program Files folder but
the users need the proper permissions to the folder, any other folders, and
possibly the registry to run the application. By default user should already
have read/list/execute permissions to a folder created off of the drive
folder but you should double check that.
Try temporarily add a user to the power users group to see if that allows
the user access to the application. If it does you should be able to tweak
permissions to allow regular users to use the application. There is a
security template called compatwks.inf that will modify permission of a
computer to give regular users the same permissions as power users without
the extra privileges such as creating shares and user accounts.
It is not always possible with older applications to get them to function
for a regular user. There are free tools from SysInternals called filemon
and regmon that can also help you troubleshoot problems with running
applications. Basically you logon to a computer as a regular user, and then
use "runas" to start filemon or regmon with administrator credentials just
before you try to run the application and then stop filemon/regmon from
logging as soon as the application fails. Then look in the log of
filemon/regmon for access denied entries, make changes in permissions for
the pertinent users group, and try again in a trial and error process.
http://www.sysinternals.com/Utilities/Filemon.html -- filemon
If you are forced to allow user to be local administrators because of issues
with old application you still can use Software Restriction Policies to
restrict what applications a user can run or install by configuring
enforcement to include local administrators. The catch is that a local
administrator can bypass SRP by booting into safe mode assuming they know
such. --- Steve
"UC_Bearcat_99" <UCBearcat99@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E9F41E26-3660-432D-AD79-1E0C4FB6238E@xxxxxxxxxxxxxxxx
> Thank you Steve. I knew I was at the cross-roads of "admin'ing" people or
> telling them that they just have to ask. And like you said, giving them
> any
> more destructive rights is not going to do anybody any good.
>
> One follow up question as this has me a little confused but maybe could be
> solved with Software Restrictions. The users have software that was made
> for
> Windows 95/98 (I know - don't ask). When I, as logged in as admin,
> install
> the software on their machines, it runs perfectly fine under my account.
> However, when the user logs in, the software bounces back errors and
> generally won't even start.
>
> Looking into this (haven't test it), the software installs itself to its'
> particular folder on the root c:\ (not in program files). Example is
> Artist 5.0 will install to the C:\Print Arist 5\ folder.
>
> Does software need to be installed the 'Program Files' folder in order to
> get all the proper permissions to run under 'user' accounts?
>
> Thank you,
> Jim
.
- References:
- Software Restrictions
- From: Cincy
- Re: Software Restrictions
- From: Steven L Umbach
- Re: Software Restrictions
- From: UC_Bearcat_99
- Software Restrictions
- Prev by Date: GP - Pushing out Software
- Next by Date: Re: _ How to prevent multiple logon by one account
- Previous by thread: Re: Software Restrictions
- Next by thread: Domain users unable to change password
- Index(es):
Relevant Pages
|