Re: Local admin rights?

From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 10/29/04


Date: Fri, 29 Oct 2004 20:55:52 GMT

I have not seen a lot about that either. If you want to see more info about
Windows Installer and .msi installations the link below and the section on
How Windows Installer Works may be helpful though it is geared more for a
domain environment. --- Steve

http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/techref/en-us/w2k3tr_gpswi_how.asp
http://tinyurl.com/4jjt3 -- same link as above, shorter.

"illingsk@cityofrochester.gov" <anonymous@discussions.microsoft.com> wrote
in message news:292b01c4bdc1$9a67acc0$a301280a@phx.gbl...
> You know, I have tried very hard to drill down to this
> article in the MSDN Library though its Table of Contents
> without success. I sometimes find it useful to do this so
> as to identify what subtle associations the author is
> making about this subject matter.
>
> Alternatively, I can find this article by searching
> for 'elevated permissions' ok.
>>-----Original Message-----
>>There is not a user right that can accomplish that but
> if the software
>>install is a .msi package or can be converted into
> a .msi package then you
>>can modify the local Group Policy so that .msi
> applications are always
>>installed with elevated permissions. Local Group Policy
> is opened via
>>gpedit.msc and on a local computer will apply to ALL
> users that use the
>>computer. You would have to enable always installed with
> elevated
>>permissions in both computer and user configuration. The
> link below explains
>>more. --- Steve
>>
>>http://msdn.microsoft.com/library/default.asp?
> url=/library/en-us/gp/324.asp
>>
>>"illingsk@cityofrochester.gov"
> <anonymous@discussions.microsoft.com> wrote
>>in message news:234a01c4bcea$343cb760$a301280a@phx.gbl...
>>>A small handful of users needs to be able to install
>>> programs periodically on WinXP workstations. We have no
>>> Windows Domain here, and by default all users are made
>>> members of the Power Users group.
>>>
>>> Rather than make these users members of the local
>>> Administrators group, I was wondering if one of the
> local
>>> User Right settings could be modified to allow them to
>>> accomplish a periodic software install?
>>>
>>>
>>>>-----Original Message-----
>>>>Add the user's domain account to the local
>>> Administrator's group on each
>>>>individual workstation. Be sure to add only the domain
>>> account of the user
>>>>who "owns" that machine, so that they cannot access
> each
>>> others'
>>>>information.
>>>>
>>>>--
>>>>*****************
>>>>Laura E. Hunter - MVP
>>>>Replies to Newsgroup only
>>>>All advice offered as-is, no warranties expressed or
>>> implied
>>>>"Shane White" <ShaneWhite@discussions.microsoft.com>
>>> wrote in message
>>>>news:039257B8-7EA0-46EE-BDC0-
>>> 2DCCD0E9F080@microsoft.com...
>>>>> Hello,
>>>>>
>>>>> I have a client running a Novell and WindowsNT4.0
>>> environment. When users
>>>>> log into Novell, they are also logged onto the domain
>>> (since passwords
>>>>> match). Currently, no one has local admin access to
>>> their own machine, so
>>>>> they cannot install software, use Windows Update,
>>> etc. What is the
>>>>> easiest
>>>>> way to give a user local admin rights to their own
>>> machine under WinNT4.0?
>>>>> I
>>>>> tried creating a local account on the workstation,
> but
>>> then realized that
>>>>> the
>>>>> user never logs on to this workstation account since
>>> they are
>>>>> authenticating
>>>>> to the domain. Users need to be able to install
>>> software, use Windows
>>>>> Update, etc. The only stipulation is that users
>>> should NOT be able to
>>>>> view
>>>>> another machine's C: drive (i.e., \\machine-name\c$).
>>>>>
>>>>> Thanks for any advice-
>>>>> Shane
>>>>>
>>>>
>>>>
>>>>.
>>>>
>>
>>
>>.
>>



Relevant Pages

  • Re: Error crystal websetup 9 install
    ... MSI: Cloaking enabled. ... MSI: Package name extracted from package path: ... The installer has encountered an unexpected error installing this ... The error code ...
    (microsoft.public.dotnet.framework.aspnet)
  • The installer was interrupted
    ... MSI: Cloaking enabled. ... MSI: Package name extracted from package path: 'my.msi' ... Action start 12:08:13: FatalErrorForm. ... The installer has encountered an unexpected error installing this ...
    (microsoft.public.dotnet.framework.setup)
  • Re: How I overcame Error 1321 and got a new MSI--Thanks Mary!
    ... I blew off Norton. ... I used a Beta RC1 MSI 3.0 installer. ... I got a 1911 error that gave me the chance to say no to wisptis and I got ...
    (microsoft.public.office.misc)
  • Re: how to upgrade windows installer service: *Repair and Replace MSI Questions*
    ... repairing and they had Win XP with a native MSI 2.0, ... This KB does not list that the download is for XP but does give the ... Windows XP with this download though? ... Or does the Windows Installer ...
    (microsoft.public.officeupdate)
  • Re: Uninstallation Hangs
    ... That 1618 error means that another MSI setup is already running. ... Definitive Guide to Windows Installer ... > Files\Beehive Systems Ltd\Wasp'3D Drone Designer\ ... > The installer has encountered an unexpected error installing this package. ...
    (microsoft.public.dotnet.framework.setup)