Permissions to run applications

I'm setting up a laptop for Sales to use as a Demo for our printer/badge making application display.
I have full administrator permission.
I can install the software it runs just fine but when our director of sales (Power User) logs on he is denied permission to access certain files within the application.
If he is logged in with administrator permissions he has full access.
We don't want him to be an administrator.

Is there something I should have done when installing the software to give Power Users the ability to fully run this (or any) application?

I am able to go in and provide him with full rights for the application folder & subdirectories (and everything works fine) , but this means I have to do this with every application I have installed.
If I miss something...that's just not acceptable.

What's going on here?

Jimat

 

The application itself may be at fault (poorly written or not designed for an NT system so no real provisions for security). The other possibility would be that you missed an option to install for everyone or just for the logged on account doing the install.

Since the user is a Power User, his account should be able to install apps and if you log on with his account and install, he should be able to use it. Any problems uninstalling it and then trying again with his logon?

 

I have considred that, but logging in as a Power User prohibits system file mods which will stop an installation, wouldn't it?

We are seeing something similar with this same application on a production XP computer (and maybe a Win2K machine also).
I really hadn't made a connection before.

There never was an option to allow or disallow other users during the installation so I just thought maybe I had missed some global security setting.


Jimat

 

From http://www.kellys-korner-xp.com/xp_groups.htm

Power Users can:

• Run legacy applications, in addition to Windows XP Professional certified applications.
• Install programs that do not modify operating system files or install system services.
• Customize system wide resources including printers, date, time, power options, and other Control Panel resources.
• Create and manage local user accounts and groups.
• Stop and start system services which are not started by default.

Most program installs of 3rd party apps do not mess with OS files or install new system services.

The one you have might possibly do one or both but it would be worth a try at installing as a power user. Pretty good chance it will work.

If you are just dealing with a single application that is on this machine as a demo and will be on several others at some point, it might be worth just giving power users admin rights to the install folder unless you are worried about them messing things up and a power user can do that anyway.

 

The whole setup is quite strange.
To install from Power User a login window pops up demanding a login for a user with Administrator rights.
This XP install was just a standard o/s install on a clean hdd. No customization was done.

Something else from the Twilight Zone is that a sub-application in this application keeps asking for [something] from Office 2000 to be installed.
This is happening on both XP machines. [it doesn not happen on one of our production computers which is also XP] The programmers are looking at it, but they're on the other side of the planet so things are a bit slow.
It doesn't happen with admin. accounts.

We have a trade show this week so I've just given them my account to use until we get this straightened out.
So far I am completely disappointed in the way XP is handling this permissions thing.
I'm considering removing XP & installing 2000 just so we can get our focus back.

Jimat