RE: Running programs for non-previleged users on XP

From: Drumgod (Drumgod_at_discussions.microsoft.com)
Date: 05/24/05 

Date: Tue, 24 May 2005 11:22:01 -0700

Sounds like a permission problem. Check your NTFS permissions on the folder
where the program has installed. Verify the user can / cannot acces that
folder. Also check the root drive for the presence of "Creater Owner" in the
NTFS Permissions. That group will only give the creater of folders/files
permission to read. All other non adims will be denied.

"Sathyaish" wrote:

> Scenario
> ===========
>
> (1) You write a program using some programming language, say, C#.
>
> (2) You make an assembly out of the program by compiling it. It is a
> single module assembly.
>
> (3) You create a setup program for this.
>
> (4) During the setup, the user, an administrator group user, selects
> the option, "Install this program for all the people who use this
> computer, and not just for me."
>
> (5) The administrator group user finishes installing the program. Then
> he goes on to use it. He is able to use it.
>
> (6) The administrator group user logs off.
>
> (7) Another user, let's call him by the name John, who's only a
> "regular user" who does not belong to the administrator group (not even
> a Power User), logs in and wants to use the program. He double-clicks
> on the program exe icon on the desktop. It doesn't work for him.
>
>
> Questions:
> ============
> (1) Is is even possible or a reasonable demand that the user who does
> not have administrative previliges be able to use the program. It must
> be noted that the intention is so, since the administrator who
> installed the program supplied the choice "Install for everyone" while
> installing it.
>
> (2) If it is possible and a reasonable demand, how can it be
> accomplished?
>
>
> * I present an oversimplified version of the problem only to focus on
> the bare essentials of the problem.
>
>

Relevant Pages

  • Re: Block AOL Inst. Messenger???
    ... and usb ports are disabled in cmos if they are not needed. ... installed The other main thing to do is to tighten up ntfs permissions. ... Other folders added to the root folder since installation should probably ...
    (microsoft.public.win2000.security)
  • Re: Creating "Home" dirs via script
    ... But share access is only half the story; what NTFS permissions ... This script can be "wrapped" in another to create MANY home folders at ... If doesFolderExist = 0 then 'If Folder does not exist, ... Set ace = CreateObject ...
    (microsoft.public.windows.server.scripting)
  • Re: temp internet folder cookies listing
    ... Tea Timer) *before* installing SP2. ... Settings\\Cookies <=this folder contains and shows your cookies. ... that there are cookies on my computer. ... cookies no longer appear in the Temp Internet Folder. ...
    (microsoft.public.windowsxp.general)
  • Toggle between SP1 and SP2
    ... there was a discussion about installing SP1 and SP2 side by ... Moricons.dll is normally present in the system32 folder by default. ... This is the file that switches to SP1, for the other one just replace SP1 ... Dim sc As Shell32.ShellLinkObject ...
    (microsoft.public.windowsxp.embedded)
  • SP/3 Cleanup
    ... In the past for SP/2 we deleted stuff after SP/2 was installed and wondered if anyone knew if SP/3 has same that can be deleted. ... Installing SP2 leaves a lot of space on your hard disk taken up by files you would only ever need if you were to uninstall SP2. ... Delete the hidden folder of files that would be restored by an uninstall: C:\Windows\$NTServicePackUninstall. ... Do not delete this - it will be used in future by Windows File Protection - but on an NTFS disk you can compress it to save about 200MB of disk space. ...
    (microsoft.public.windowsupdate)