The Golden Rules
One of the main challenges Windows administrators face is managing access to resources as efficiently as possible. A golden rule is to use groups instead of individual accounts to assign permissions to resources. Groups can create an abstraction layer in your authorization model that makes the assignment of permissions independent of account-level changes. This rule applies to Windows domains and standalone environments.
For example, in many organizations, users regularly switch between organizational roles. Each role typically requires specific permissions to Windows resources. In AD, you can create groups for organizational roles (e.g., help desk operators, developers) and assign resource permissions to these groups. If a user switches roles, you simply need to make that person's account a member of the associated group. This practice is much more efficient than resetting the account's permissions so that the user can access the resources needed for the new role. . . .
)
)
Register
1) Group A: Special modify access - Users can create file and edit but not delete other files.
2) Group B: Modify access - Users can create, edit, and delete files.
When the security setting was applied, users are able to create subfolders but cannot rename the file. Is there a solution for this or should we be considering other options?
Also, each time a member from Group A makes any changes to any Office app (Word, Excel, etc.) the temp files created are left there (since the group is restricted from deleting the files). Any advise on how to work around this?
Thanks.
DR25932 September 08, 2006 (Article Rating: