The situation presented by 'computermike' was not access TO the program file, but rather the requirement of apropriate permissions to USE a program. They can have full access control over the directory that the prog is in, to include full access control of the program's executable itself. That is having access TO the program. But if they are a regular user, and that program is trying to make modifications to the system, or access areas of the system that a member of the user group does not have permissions for, then it will not work even if they have been given full control as described above. That is an example of not having the required permissions for a program to operate.
Example - I have laptop users that can not successfully run various programs (i.e., Reflections for IBM, and certain dial-up SW) if they are not power users. They have full access to the executables, they can see the programs, they can execute the programs, but when they double click on it, the program tries to execute and by design of the OS it uses the users permission level, which if it is a user level, then it craps out.....if it is a power user level or admin level, it runs perfectly.
This is why I advise 'computermike' to determine why the users must be admins. If it is because they can not see the executabl, then I agree that he needs to add the users group to the security settings of that program. If they need to be admins because the program needs to interact with the OS with a permision level higher than that of a user, then he needs to address it as such.
Perhaps 'computermike' should give an example of which app will not run when logged on as a regular user.
I don't think we are disagreeing as much as answering different scenarios. 'Computermike' should clarify if the problem is access to an installed product, or required permissions or the program to operate properly, and he should also give examples of which programs he is dealing with in this case.
~Bill
