6000 folders permissions set using Cacls -permissions meaningless

G

Guest

I created about 6000 folders for users and now I find in 321470 Unexpected
Results Occur if you use calcs. I set it up so only the user and an
administrator would have access but thanks to the way Microsoft has this set
up it's worthless and all the user data is at risk beacuse all users can
access the data and have full control.The user folders are under upper level
folders that I need to be able to give a limited number of users access to
and at least read access on all lower level folders.

Does anyone know how to fix this #$%##$% mess?

Thanks for any help C. R. McMurray
 
P

Pegasus \(MVP\)

crmcmurray said:
I created about 6000 folders for users and now I find in 321470 Unexpected
Results Occur if you use calcs. I set it up so only the user and an
administrator would have access but thanks to the way Microsoft has this set
up it's worthless and all the user data is at risk beacuse all users can
access the data and have full control.The user folders are under upper level
folders that I need to be able to give a limited number of users access to
and at least read access on all lower level folders.

Does anyone know how to fix this #$%##$% mess?

Here are the first few steps you need to take to "fix
this mess" (your words):

- Post the exact command you use.
- Post the error message you get - verbatim, please!
- Report if the error occurs on any folder or on one specifif
folder.
- Report what happens if you move this folder out of the
way, then re-run cacls.exe.

You write "thanks to the way Microsoft has this set up it's worthless".
Have you considered giving the parent folder limited access rights
so any child folder you create will have the same restricted access
rights? If so then there would be no need to fix things retrospectively.
 
G

Guest

Pegasus (MVP) said:
Here are the first few steps you need to take to "fix
this mess" (your words):

- Post the exact command you use.
- Post the error message you get - verbatim, please!
- Report if the error occurs on any folder or on one specifif
folder.
- Report what happens if you move this folder out of the
way, then re-run cacls.exe.

You write "thanks to the way Microsoft has this set up it's worthless".
Have you considered giving the parent folder limited access rights
so any child folder you create will have the same restricted access
rights? If so then there would be no need to fix things retrospectively.

That's just it, there is no error message and if you dump the acl it looks exactaly the way it is expected to look. The upper level folder does not inherit permissions and the second level folder acl hast two users with access, the administrator and the assigned user. However every user in the system has rights to the folder.
Look at Article ID: 321470(the 4th bullet), it describes the problem very
well. What is unclear to me is how to fix it.
 
P

Pegasus \(MVP\)

looks exactaly the way it is expected to look. The upper level folder does
not inherit permissions and the second level folder acl hast two users with
access, the administrator and the assigned user. However every user in the
system has rights to the folder.
Look at Article ID: 321470(the 4th bullet), it describes the problem very
well. What is unclear to me is how to fix it.

Use workaround 3.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top