Unable to run programs as a "Limited User"

[flynbrian99]

Certain programs will not run if I am logged in with a Limited User Account. If I log in with an Admin account it works fine. Is there a way around this issue...so that I can log in as the limited user and run the program with out having to be logged in as Admin?

THanks!!

 

[Beowulf005]

Would this be with or without the users knowledge?

These programs need admin assess to run os the only way to run them on a limited account is to use the "runas" command.

When frustrated remember, in the computer world there is almost always a backdoor.

 

[flynbrian99]

yeah...I am looking for a way around that since the users will need to run the application and will not have the admin login to use with "RunAs". Anything else that I could try?

Thanks!!

 

[linney]

Our own forum member gpalmer711 has created a special program for just such circumstances, it can be downloaded for free from -

http://www.palmersoft.co.uk/main.asp?content=runasuser

 

[flynbrian99]

Thank you...I'll give it a try.

 

[Rick998]

I tend to use Greg Palmer's excellent 'RunAsUser' utility as a last resort after other efforts have failed.

Are you able to say what programs won't run with limited privileges?

Have you tried amending the rights on program folders. shortcuts and registry keys of the offending programs?

Hope this helps...

 

[gpalmer711]

<Thread Hijack>
Incidently i'm am about to start work on the next version of the software. Updating it to dot net and improving the look of the interface.

Likewise with the AppKiller software.

If anyone has any suggestions for the software feel free to let me know.
</Thread Hijack>

Greg Palmer
Freeware Utilities for Windows Administrators.

http://www.palmersoft.co.uk

 

[Rick998]

<Hijack response>

Hi Greg,

Any particular reason why you're going to move to .NET?

I've managed to avoid having to install any flavour of the .NET support files so far (in the interests of keeping disk images as small as possible).

Rick
</Hijack response>

 

[gpalmer711]

Hi Rick,

Mainly because I do most of my programming in .Net now and Microsoft have officially ended support for the Visual Studio 6 range of products.

I will continue to support the VB6 versions of the software though and may update them as well if the response is that VB6 versions are prefered.


Greg Palmer
Freeware Utilities for Windows Administrators.

http://www.palmersoft.co.uk

 

[HughLerwill]

The reason why they will not run may be because they are trying to write to their application folder in the Program files folder, that is not allowed under a restricted account. I also seem to remember that trying to grant write permissions to the offending folder for a restricted user even under an Admin account is difficult if the folder remains in Program Files.
You can avoid this in XP at least by avoiding the Program Files Folder and installing the app into something like c:\MyApp. By default the restricted user will not have write permissions to that either but they can be granted without problem by a User with an Admin account.

 

[Rick998]

Hi Greg,

Many thanks for the info.

Just my opinion but I've been trying to keep my computing needs as portable as possible. RunAsUser is one of those indispensable utilities that, when I need it, I just run from my USB stick without having to install it.

(Most PC's at work aleady have COMDLG32.OCX installed/registered. I have a 137k mini-installer for the few that don't).

 

[Rick998]

There shouldn't be any problem for an Administrator to amend permissions on program file folders, i.e. by giving 'write' permission (but you must usually give 'full access' to the shortcut that runs the program as well).

What is often a problem is that on PC's where 'normal' users have limited privileges, it means that an Administrator has to carry out the install. Unfortunately this usually means that the installer creates the application settings folder in the Administrator's profile (e.g. C:\Documents and Settings\Administrator\Application Data\...), not the profile of the user who is going to be using the program.

This is often the case with specialist assistive software, e.g. Dragon NaturallySpeaking, Jaws, Read and Write, etc. What's worked for me is to add the user to the Adminstrators group temporarily to install the program then to remove them from the group afterwards.

This overcomes the problem of the correct profile being amended but still means that desktop and Start menu shortcuts, program file folders and sometimes registry settings all have to have their permissions amended.

If the program uses speech then you have to jump through a few more hoops as well. It can be a real pain... but in my opinion is still better than letting users have admin rights as a matter of course.

Hope this helps...

 

[gpalmer711]

Nice!!

In that case I may just stick with VB6 for now - there is nothing I need to do that cannot be achieved with VB6.

Greg Palmer
Freeware Utilities for Windows Administrators.

http://www.palmersoft.co.uk

 

[Rick998]

Must admit... portability and program size is why I'm sticking to VB6. Most of my own home-grown utils for use at work are between 18k and 96k (and 5k of that's the icon <grin>).