How to track dpwn programs that fail in Restricted User Accounts ?

  • Thread starter Thread starter John7
  • Start date Start date
J

John7

Hi,

Are there any tools or sources that help to track down why certain programs
fail to work (properly) in Restricted User Accounts.

I do not intend to grant every user Administrative rights.

TIA,
John7
 
John7 said:
Are there any tools or sources that help to track down why certain
programs fail to work (properly) in Restricted User Accounts.

I do not intend to grant every user Administrative rights.
Click to expand...
Hi,

One way is to use Sysinternals RegMon/FileMon utilities to try to find
what registry keys and file system folders the application need write
access to and set rights accordingly for the locked down user account.

RegMon/FileMon is available for free here:

http://www.sysinternals.com
 
The most common issue with these programs is that they attempt to write info
to places that the Restricted User doesn't have permission to write to - the
root directory and the Windows directory, etc
 
Hi,

This should help:
http://rickrogers.org/xpsware.htm

You will find that much depends on how the program installation routine was
written. There is generally no need to make all users administrators. The
majority of the time the users will need read and execute permissions added
to the program installation folder.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Like Nutcase says, very often it is just need for modify grant to Users
group on the c:\program files\application-install-point folder
so it is worth a try before digging in more deeply with the tools from
sysinternals. However, if you are dealing with an old application,
Win9x era or worse, this may well not be sufficient and for some
it may be impossible to make the prog work in limited account.
 
Torgeir Bakken (MVP) said:
Hi,

One way is to use Sysinternals RegMon/FileMon utilities to try to find
what registry keys and file system folders the application need write
access to and set rights accordingly for the locked down user account.

RegMon/FileMon is available for free here:

http://www.sysinternals.com


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx
Click to expand...

Thx for responding,

I knew these Sysinternal tools already but was curious
to learn about a All-In-One tool that covers all issues.

John7
 
And some times registry locations such as CLSID, if the program registers
DLLs on the fly

- Adam
 
Adam White said:
And some times registry locations such as CLSID, if the program registers
DLLs on the fly

- Adam
Click to expand...

Yes, but that is one grant I would not like to give to Users.
I have no real issue with granting Users write over the reg
key structure of a specific application in HKLM\Software
when that is needed by a misbehaved app.
 
Roger Abell said:
Yes, but that is one grant I would not like to give to Users.
I have no real issue with granting Users write over the reg
key structure of a specific application in HKLM\Software
when that is needed by a misbehaved app.
Click to expand...


Thank you all for responding.

So I would need to stick to Sysinternals, RegMon, FileMon, ProcExp(lorer).
Is there no All-In-One tool ?

Would these MS tools be of any use to track down Restricted User Account
issues?
- Pstat
- ACT (Application Compatibility Tool)


TIA,
John7
 
ACT is of use especially for older software, that is, when it is
not simply a permissions issue but one of the application using
depricated API calls, etc..

There is not, to my awareness, a all-in-one, point at the application
and provide the account and its password, and wait tool.
Things are probably too situational and the return on effort too small
for anyone to have developed such a tool.
 
Back
Top