Unfortunately, there are just some apps that require administrator privileges to install properly. For whatever reason, that's how they were written. Sometimes, if you contact the Tech Support people of the application's publisher, they will provide a work around. But this isn't guarenteed.
A possible work-around (we tend to use this in our organization): The RunAs option will allow a user to run a process (i.e. a software installer) with the credentials of an account with elevated privileges. It would work something like this:
1. Create a generic domain account with administrator privileges. Give it a password only you know.
2. When someone needs to do something (like load software) that requires administrator privileges, you can toggle the temporarily change the password on this generic account and give the userID/password to the user. The user can run the software installer using the RunAs option. When the user is done, you can then cahnge the password again to your secret password. This prevents users from using this feature when you don't allow it.
3. Ass an alternative, you could enable and disable this account when needed, instead of changing passwords back and forth.
The end result is that your users can use administrative privileges when they really need them (and you allow it), without making them administrators.
Hope this helps.
