AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() Those parent folders are out of scope and not part of the copy job. The answer to that question is typically that the source folder has inheritance enabled and is inheriting some permissions from one of its parent folders. We offer a file server and NAS migration product called CopyRight2 and from time to time our customer support gets asked why specific permissions, do not migrate to the target as expected. We discuss what share and NTFS permissions are and how they work in detail. For whatever reason, it is still one of the less understood topics. The concept of NTFS permission inheritance was introduced a long time ago with the release of Windows® 2000. This article explains Windows® share and NTFS level permissions including inheritance. ![]() But you also want to use it to your advantage when possible./ Categories: File Server Migration, NAS Migration How Share, NTFS Permissions and Inheritance Actually Work Keep the security inheritence in mind and remember that you can break that chain anywhere in the folder to subfolder to subfolder chain. Not sure if that helps but it sounds like you really want to think about the organization of the folders and the related security and how they need to be grouped to make the process more efficient and secure. Figure out how you can use the groups and not manage everything individually. Same ways that there are groups in Active Directory - if every user added to the domain would need individual security set on everything, it would be a nightmare. You likely want to step back, look at the reports, what groups need access to which ones, how to best align that with active directory groups, etc and figure out a security (folder) structure for the report server that suits the needs of the company without becoming a management nightmare. If you have hundreds of reports and every report has it's own folder and is off of the home folder, it will inevitably be ugly to manage. In the Accounting dept folder, you could have folders for the payroll group, receivables group, etc ![]() You could have a folder for the accounting dept, management, customer service. And you can manage security within each of these individual folders. So a "high level" folder (one right under the root home folder) can have multiple folders which in turn can have folders, etc. You can have folders with folders in them with folders in them. You'd want to have some type of grouping of the organization, reports and the two usually go together with AD groups in some way. If you have a lot of reports, you do want inheritance but probably not from the top level down all the way through to all folders and items. They don't necessarily need to just access everything from the Home folder. If you don't want to break inheritance when creating a new folder than you would need some type of grouping of the folders and reports, grant access the folders and have users access those folders directly rather than going from the Home folder to other folders. So if you don't want users to see all of the folders, they either can't be browsers at the home level or you need to break the inheritance. That's the whole inheritance from the parent. because of this permission any new folder I am adding then everyone is able to see that folder and I have to go manually and edit the permission every time I am adding a new folder. Verify that sufficient permission have been granted and windows user account control (UAC) restrictions have been addressed ", that is the reason I have given permission at Home page. If I try to remove user from Home page folder setting and directly give permission at folder level then user gets an issue while accessing the folder " User ( user ID ) doesn't have required permissions. I have given permission to user in Home-> Folder setting. ![]()
0 Comments
Read More
Leave a Reply. |