Discussion Locked

installing programs

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

Been able to install programs as administrator but when another user logs in to same pc they can't run program and get message about needing to be in admin group. Putting them in power users group only works if they have local profile but they are currently pulling their profile from server as a roaming profile. Any advice? Thanks.

13 replies

by ewgny

You can get most programs to run under a user account, by editing the security settings in the programs associated registry keys.
Start by looking in HKEY_LOCAL_MACHINE with regedt32 (you can't use regedit to modify security settings)
when you find the key for the program, under the security menu add "authenticated users" and then give authenticated users full permission.
You may also have to modify the security permissions for the programs folder structure, as well as any *.ini files created by the program.
If this does not work for your specific program, reply and I will give you more alternatives

by eservando

Thanks but there has to be less evasive way to run programs in 2000 or XP for that matter. Was told about right clicking on program an choose run as and select administrator. In the past, putting user in power user group usually worked but once again since i'm using server profiles instead of local, this doesn't work. Thanks again.

by jose_12650

Did you try right clicking the program and click RunAs?. Then Run the program as Administrator? Or reinstall the program and choose for all users' option?

by curlergirl

I believe that answer #1 is the only way to do this. Many programs will run in a Power User context, but only if the program does not require the user to be able to edit the HKLM registry hive. By default in Win2K/XP, only users with Administrative Rights have access to most parts of this registry hive. Therefore, the only way to allow non-administrative users to edit it would be to manually add them and give them the rights to do so. I know it's annoying, but the only other alternative is to add the users to the local administrators group and let them have full rights to their workstations. Personally, I don't like to do this, but sometimes it's the most logical answer to the dilemma. Then, just advise them that if they do bad thingsto their machine (like install programs that don't work right or cause corruption in the OS), then their rights will be taken away and they won't be able to run the programs they need. Of course, this depends on your management being onboard for this kind of statement. Hope this helps!

by eservando

Thanks, at least i won't go nuts trying to find a workaround that isn't there or feasible. The only thing i wanna clarify is when you said put them in local admin group do you mean by going through local users path on pc or in user manager for domains since i use NT not Win2k server?

by curlergirl

Response to your comment on my answer - you put them in the local admins group by going through Computer Management on the local workstation (assuming they are Win2K/XP Pro). In Computer Management, open Local Users and Groups, then go to Groups and add them to the Administrators group there. If the workstations are NT4.0, you use the User Manager on the workstations to do the same thing. What you want to do is add their domain user account to the local administrators group, so when you're adding the user, be sure you have the domain selected at the top and are seeing your domain user account list. If you had them added locally as users and/or had their domain user account on the Power Users list, you would want to remove the local user account and remove them from that group, too, just to clean up. Hope this helps!

by cwjudd

Your group policy is configured to only allow domain administrators to install programs via editing files on the local system. You need to go into the group policy of the domain server and allow the users to edit file on the local clients. When some applications are run, they must create log files or batch files on the local machine. If the local policy that is set on the domain is configured to not allow the users to edit these file (hence power users) then they will not be able to run these applications.

by desktop jinx

If you're really averse to allowing users to be local Administrators, and the application doesn't explicitly require local Administrator privileges, you may be able to figure out specifically what the app is trying to access by monitoring its activity using a profiling tool like ZDNet's InCtrl5. You can then open up only those files, folders, and registry keys the app needs. This is a lot of work, but less work than supporting desktops where users are local Administrators :)

This discussion is closed to new replies.