|
Home > Archive > Windows 2000 track general > March 2001 > Preventing Permissions Inheritance
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Preventing Permissions Inheritance
|
|
| Daviet 2001-03-07, 6:47 pm |
| You have three options for Preventing Permissions Inheritance In Windows2000 permissions option Tab under security, They Are Copy, Remove And Cancel.. Can anyone explain in laymens terms What the Copy and Remove option do.. I read a few Articles On it but It is still not sticking.. So can anyone Put this into baby terms for me
Goo Goo, Gaa gaa..... Thanks In Advance  | |
|
| This thread belongs in Windows 2000 general forum. | |
|
| Very True, And im sorry, I did Find It a bit strange however having my Post moved, I asked this question in the general Forum because I thought more would be able to help out, I see others asking questions about MCSE related topics So I Just figured...
Again, My apologies | |
|
| Daviet,
What we are talking about here is preventing the inheritable permissions from the parent object from applying to the child object.
Say we have a folder called cadman (c:\cadman). We have a folder under it called rules (c:\cadman\rules). If we set the security to Full Control on c:\cadman and allow it to propagate down to c:\cadman\rules, then c:\cadman\rules inherits Full Control by virtue of being a child of c:\cadman.
Now we decide we want to break the security tie. We decide that for the security tab of c:\cadman\rules that we want to uncheck the checkbox for Allow inheritable permissions from parent to propagate to this object. we are immediately asked if we want to copy the parent security (remember, currently security is from above) to this object, remove the parent security, or cancel. Cancel is obvious and puts the check mark back.
Copy puts Full Control on c:\cadman\rules, but breaks the tie to c:\cadman for security purposes. It you change security on c:\cadman to just Read, you will still have Full Control on c:\cadman\rules, because c:\cadman\rules has it's own security settings now, not dependent on the parent c:\cadman folder.
If you remove the parent security settings, you can set the security from scratch, because you didn't carry (or copy) it down from above.
If parent security is >50% what you want for child, copy it down, then change it. If parent security is <50% what you want for child, remove it, then set it the way you want.
Help any? | |
|
| Actually that was A great explanation, I really understand How it works now.
Thank you very Much, I really appreciate the help | |
|
| Say you have two files under c:\cadman. Both files are set to inherit security permissions from the parent. You make c:\cadman Read-only. The two files have Read-only permissions on them. Change permission on c:\cadman to Full Control. Now both files have Full Control permissions because they inherit from c:\cadman. Set permission on c:\cadman back to Read-only. Take the first file and uninherit the permission from parent, copy the current permission (Read-only). Now the first file has Read-only permission (static, if you will). While the second file continues to inherit permission from parent (dynamic, if you will). Change parent to Full Control. Parent (c:\cadman) and second file now have Full Control permission, first file is still Read-only.
Again, whether you want to copy or remove is based on whether you want to break the inheritance tie and still maintain the current security settings or you want to remove the current security settings and set them yourself. | |
|
| Didn't see your post until too late. Sorry. (Didn't mean to overkill) | |
|
| When the post is moved, people still see a link to it in the General forum. Pretty cool.
Sorry, I can't answer your actual question at this time. |
|
|
|
|