Re: ReadAccess to C:\WINDOWS\WIN.INI as User (not Admin)?

From: Roger Abell [MVP] (mvpNOSPAM@asu.edu)
Date: 04/04/03 

From: "Roger Abell [MVP]" <mvpNOSPAM@asu.edu>
Date: Fri, 4 Apr 2003 08:18:06 -0700

Your differences may be due to you not using NTFS
on your test machine.

In a correctly installed XP, using NTFS for its boot
partition and at default permissions, Users have read
and execute on win.ini, Power Users have also write,
and Administrators have Full Control.

Your customer that found a plain account did not
have read either was using an account that was not
in Users group (by default, when joined to a domain
all Domain Users will be Users), or a machine with
NTFS but with permissions different from the install
default.

You installer could test these factors, and allow the
installing user the decision to make adjustment if it
finds Users do not have the default grant of read and
execute. I for one would consider it rude of the install
to do this without providing an interface to inform me
and ask for a decision. 

-- 
Roger Abell
MS MVP (Security, Windows), MCDBA,  MCSE both
Associate Expert - Windows XP ExpertZone
http://www.microsoft.com/windowsxp/expertzone
"Dr. Oliver Maas" <o.maas@metrohm.de> wrote in message news:4d1ba0cc.0304040600.5406ba29@posting.google.com...
> Hello,
> 
> i have the following problem: we sell a program which - under certain
> circumstances - needs to read a section from win.ini.
> Now this works of course if an Admin is logged in. 
> 
> I tested this issue on XP on a local account (User, not Admin), and i
> could manipulate win.ini via sysedit (read and even write).
> 
> Now our customer tested this issue on another XP machine using another
> account (User, not Admin, at the moment i dont know whether this was a
> local account or from the network - i guess this could be an issue
> too?!) and he told me that he had no read access to win.ini under his
> circumstances.
> 
> Situation:
> 1) my local user account: read and write access into win.ini 
> 2) our customer user account: no access to win.ini at all 
> 
> The goal is the following:
> 1) read access to win.ini for the User Account.
> 2) Writing into win.ini should only be possible for the Admin.
> 
> any suggestions?
> 
> thank you in advance
> 
> Oliver Maas

Relevant Pages

  • Re: Client Installation Issues: SMS 2.0 SP5
    ... Log on locally as LOCAL admin and install. ... Log on Locally as domain user who has LOCAL admin rights. ... The SMS Service account IS a domain admin ...
    (microsoft.public.sms.setup)
  • Re: New install, login not accepted
    ... install SPS. ... I got through the install following the steps in the Admin. ... a admin account, that account needs admin rights to SQL and the local box, ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Client Installation Issues: SMS 2.0 SP5
    ... Lets say the account I use for> the SMS Services is SMSAdmin. ... I setup the Client> Installation Account as what was listed above being our local admin ... password on some> of those, but any other idea's why prior to this, the client didn't want to> install? ... Grant the>> service account admin rights on every box, ...
    (microsoft.public.sms.setup)
  • Printer will only work in Admin Account
    ... > other programs I install, for that matter) show up on all ... > will only work in the Admin account. ... I then gave a user account Admin rights and it ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Lost admin access to ADAM
    ... admins) as ADAM admin principal, as opposed to a specific user. ... use your domain account to connect (provided this account is a member of ... This posting is provided "AS IS" with no warranties, and confers no rights. ... If I install with my account (which has has local ...
    (microsoft.public.windows.server.active_directory)