Re: Permissions not being inherited from parent directory to certain f

What access controls are there on these files?

I checked random files in my system32 folder on my Windows XP machine (I
could check Windows Server 2003 and Windows Server 2008 if it's important).

Every one I checked did not inherit permissions. This may be deliberate. The
permissions varied but were typically:

Intenet Guest Account denied Full Control
Users granted Read & Execute
Power Users granted Read & Execute
Administrators granted Full Control
SYSTEM granted Full Control

The system23 folder permissions were:

Users granted Read & Execute
Power Users granted Modify
Administrators granted Full Control
CREATOR OWNER granted Full Control
SYSTEM granted Full Control

Paul

"Roger Mellie" <RogerMellie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3E791E3F-CA80-47A2-8254-B584B5E1D641@xxxxxxxxxxxxxxxx
A minor problem but one which i'm curious about.

We have a number of Windows 2003 servers, basically those built from
around
May onwards, although it could be from earlier, where permissions are not
being inherited from the parent directory to 2 specific files. The files
in
question are:

C:\WINNT\SYSTEM32\wscript.exe
C:\WINNT\SYSTEM32\cmd.exe

Now there may well be other files that this applies to, but these are our
area of interest. Basically the USERS local group should be inheriting
permissions to these files for Read and Execute, but they are not. This
seems
to be happening to all builds. It's causing an issue with users logon
scripts
failing to run.

Of course this is eay enough to fix, but I'm more curious as to what is
causing this and why. My thoughts were that maybe a patch could be causing
this, but that doesn't really make sense. As if a patch was the cause,
surely
it would affect all existing machines.

As an aside a colleagues XP laptop also has the same setting. This was
last
rebuilt March/April this year, whereas my XP laptop doesn't have this. And
that was built in February this year.

So I'm guessing whatever it is, it is something that has occured between
February 2008 and April 2008, which is why it seems to be pointing a patch
being the cause.

I've had a good search through the net today, but cannot find anything
that
points at a likely cause.

Any info greatfully received.
--
Regards
Roger


.

Relevant Pages

  • Re: Permissions on the Distribution point shared directory
    ... > Is Everyone full control what SMS needs for this to work? ... PMFJI -- prior to Windows Server 2003, typically share level permissions ... adminstrators group & System group should have Full control. ...
    (microsoft.public.sms.setup)
  • Re: Server Operators Group
    ... to delegate the creation of shares on servers.... ... Configuration is done using TweakUI by using the “Access Control --> Manage ... MS-KBQ838777 - New network shared folders automatically assign Read permissions to the Everyone group in Windows Server 2003 ... "paperhat" wrote in message ...
    (microsoft.public.windows.server.active_directory)
  • Re: event 6161 - Domain Users Cannot Print
    ... server. ... It seems like it has to be a permissions issue. ... for me to give the users full control of the system32 folder. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: LDAP Authentication for Single Sign On
    ... Speaking of Who Am I control, it will be in Windows Server soon. ... know it is in Longhorn. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Power Users & Servers - Windows 2000 & 2003 Differences
    ... and control services remotely using services.msc or compmgmt.msc. ... Windows Server 2003 however, power users are unable to do that via ... What additional permissions must be granted to the power ...
    (microsoft.public.windows.server.security)