Adding permissions at top level folder

Let's say your top-level folder is d:\filestore\ You add Domain Admins to it with Full Control.
If the sub-folders have maintained inheritance of the perms from that folder then you're good.
However, if any of the subfolders have broken permissions, either by removing all permission and adding new ones or by copying the permissions and adding additional ones, then you're kinda screwed. Enforcing inheritance of the perms from your top level folder on that mess will almost certainly obliterate the existing permissions.
If you're semi-lucky you might be get away with finding a number of folders that you can apply the perms to that will then propagate to the rest.
If you're really unlucky, and it sounds like you are, then you may have to apply the permissions to many individual folders.

I have just migrated to a new 2012 R2 server and have my AD and file server on separate VM's. The previous server had the local Administrators group listed, but now I need to add the Domain Admins group to the top level of the folder tree and have that pass down throughout all other folders. But I don't want it to overwrite the existing permissions. Is there any way to do this?
The folder structure is insane and I want to redo it a better way, but that will take time and the OK from management. There are so many "individual" users added to many folders that it is currently impossible to keep track of.
This topic first appeared in the Spiceworks Community

Similar Messages

How to Delete Top Level Folder

I have a number of files in a hierarchy of folders and I wish to delete the top level folder but leave in place all the sub folders and files contained therein. There are only folders (no files) under the top level folder. Specifically, I do not want to just select and drag and drop all the subfolders.
Any help on how to do this appreciated.

First, to clarify the term - there are traditional VS projects (C# project, VB project, etc.) and with Team Foundation there are now Team Projects. Given the question, I take it you mean team projects (as created with the "New Team Project" option and going through the Project Creation Wizard).
When you create a team project called "foo", the folder for that project (assuming you had it create a folder during the Project Creation Wizard, which is the default) will be called $/foo. Based on your question, I take it you're referring to a folder called "bar" that would be at server path $/foo/bar since it's part of the "foo" team project.
The easiest way to rename or delete such a folder would be to bring up the Source Control Explorer (View | Other Windows | Source Control Explorer) and navigate to that folder. You'll want to make sure that you have the folder in your local workspace (this is a limitation when have in V1) so you may want to right-click on "bar" and do a "get latest version" first. If you don't already have it mapped, you'll be prompt to pick a local path to map it to.
When you right-click on the folder "bar" (once you have it in your workspace), among the entries in the context menu will be Delete, Rename (for the "rename to oranges" case), and Move (for "move it to another folder"). Note that each of these pends the operation on the workspace, and you'll need to check in before the change is committed to source control.
tiny screen shot: http://static.flickr.com/29/55040912_e3190835e6.jpg

How to move all files to the top level folder?

I want to move all files within a particular folder -- and all files in all sub folders -- to the top level. i.e. I want to collapse the folder structure to just one folder. Assume that there are no files with the same name.
*Method 1*
My first thought was to use Find:
1. Limit Find to the particular folder.
2. Find all files in the folder with Size > 0.
3. Switch to List view. All files are listed.
4. Select all files and drag to the top folder
5. Delete all sub folders manually.
Problem: Pages files are not found, and maybe others aren't.
This is a simple method and I'd like to stick with it.
*QUES 1*
What condition should I set within Find so that I can be guaranteed of finding all files?
*Method 2*
It was suggested in another thread that I use Terminal to move all files to the top level, but I couldn't get it to work. And there was a problem with files that consist of bundles.
*QUES 2*
What is the easiest way to consolidate all files within a folder to the top level -- assume no duplicate names -- and at the same time remove all sub folders?
Message was edited by: Guy Burns

Thanks for the suggestion of EasyFind.
To find all files in a certain folder I typed in *[a-z 0-9] as a Boolean search (this thread won't let me post the exact characters required by EasyFind). That should cover every file I've ever named. EasyFind came back with "11719found/12316done".
Any idea what the missing 500 files would be? I'm hoping they are files that I don't need to know about (invisible files, system files and so on).
Message was edited by: Guy Burns

Top Level folder doesn't show lowver level pictures - Lightroom2

I have my pictures stored by year and location on a hard drive    example
2009
    Heaven
       April
    Hell
         April
As I remember each upper level would show the counte of sub folders which allowed me to do sorts on ratings and the like
Now only the bottom most folder has the count..
2009                0
    Heaven       0
       April        20
    Hell            0
         April      5
I tried importing everything into a new catalog with np luck.. ONly the bottom most folers seems to have the count
how did I break it??

You have to enable include photos in subitems (I think that was the name) in one of the menus in Library.

Derived Hierarchy Permissions - cascading top level permissions to all subseuent levels

I have created a 3-level derived hierarchy in my MDS model.
Level 1 - divisions, Level 2 - groups, Level 3 - targets per year-month
We have divisional users that would use this structure. so when I add a user I set the permissions at the division level and would like those permissions cascaded down to levels 2 & 3 without going thru and setting permissions on each node in level
2 and level 3. Is it possible to do so? If yes, how? If not, then how do I maintain permissions for my users - how can I make sure that if a user enters a new group for a division, then he/she can use it to set targets?
Thanks,
Sonal

The permission will be inherited by the subtree.
https://msdn.microsoft.com/en-us/library/ee633750.aspx
On the Hierarchy Members tab, each hierarchy is represented as a tree structure. When you assign permission to a node in the tree, all children inherit that permission unless permission is explicitly assigned at a lower level.

Changing permissions on a top level public folder WITHOUT affecting the folders underneath it in Exchange 2007

Hello everyone,
We have a pubilc folder we woudl like to lockdown to just the IT techs, but we want eveything below to function as it normally has been. We have several folders underneath this folder with various permissions for our end users that we dont want changed.
How would you change the permissions on a top level folder without affecting (propagating) the folders underneath it? Also, If I go into the "Administration" tab of the properties of the top level Public Folder I see an option to
make this folder available to: "All users with access permission" or "Owners only". Would it be as simple to select "Owners only" here or will that restrict the down level folders as well to just the owners?
Thanks,
John

Hi,
You use PFDAVAdmin to customize your permission level for mailbox and public folder. This is good tool which helped me a lot in most of the permission issue for PF and Mailbox. Follow the below article for more detail of PFDAVAdmin Tool
http://www.nigelboulton.co.uk/2010/12/delegating-and-propagating-exchange-folder-permissions-using-pfdavadmin/
Exchange Queries

DFS-R Top level NTFS Permissions

Hi,
As part of my setup, I'm trying to implement a new DFS-R share between 2x Windows 2003 R2 and 1x 2008 R2 servers
I've been experimenting with the DFS-R, and I've found that if I try to change the NTFS partitions of the top-most folder, then these permissions are not replicated to the other duplicates on the other servers. Sub-file and sub-folder Perms are.
I've also found that if I do modify the top-level folder, than that server stops replicating to the others - with no errors in the event logs ! Disaster !! In my testing, all I did was add another users read access, and then that stops replication!!
So - if I need to control the top-level perms, do they all have to be in sync and setup manually ?

Hi Shaon,
Sorry I had to actually setup the server on the remote site. So no - I'm still seeing issues.
I ran that DFSutil on serv14. I don't know why it doesn't show the ClientApps DFS replication.
2 entries...
Entry: \Ubiq-serv1\Users
ShortEntry: \Ubiq-serv1\Users
Expires in 24 seconds
UseCount: 1 Type:0x81 ( REFERRAL_SVC DFS )
   0:[\UBIQ-SERV1\Users] AccessStatus: 0 ( ACTIVE TARGETSET )
Entry: \ubiquisys.local\sysvol
ShortEntry: \ubiquisys.local\sysvol
Expires in 562 seconds
UseCount: 0 Type:0x1 ( DFS )
   0:[\UBIQ-SERV14.ubiquisys.local\sysvol] AccessStatus: 0 ( ACTIVE TARGETSET )
   1:[\UBIQ-SERV1.ubiquisys.local\sysvol] ( TARGETSET )
   2:[\ubiq-serv9.ubiquisys.local\sysvol]
   3:[\ubiq-serv8.ubiquisys.local\sysvol]
   4:[\UBIQ-SERV10.ubiquisys.local\sysvol] ( TARGETSET )
DfsUtil command completed successfully.
I'm also seeing folders/files not replicate between 14 and 9. Some do, some dont. Seems to be zero byte files causing most of the issues.

Getting top level permissions?

Hello.
We have a bunch of folders on a fileserver that has folders shared directly to people instead of AD Groups. I want to get all top level permissions (IE the ones not inherited) and display the top level folder("the root folder") and the usernames
which have access to it.
With that information i will create Groups and share to the Group et cetera.
Is this possible to do powershell? How would i go about doing it?
Any tips welcome!

You could try
this module's Get-AccessControlEntry function. There is a screenshot on its download page that shows sample output. It also has a switch parameter to only show non-inherited ACEs. You could look at permissions at the root folder only, or you could show
non-inherited ACEs for any folders under the root:
Get-AccessControlEntry c:\root -NotInherited
dir c:\root -recurse | Get-AccessControlEntry -NotInherited
The results can be exported to a CSV, where each line will include, among other things, the path, the type of ACE (allow, deny), the principal, the access mask, and whether or not it is inherited.
You can also use the Select-Object and/or Group-Object cmdlets on the results to further analyze the permissions.
Let me know if you're interested in the module and have any questions about it.

Not all Top level folders showing item count

Hi there, I have Aperture 3.2.2 running on OSX 10.6.8.
I use referenced files and a folder structure with a top folder and projects nested.
Some of my top level folders when clicked, show ALL images in the projects nested below. Others do not. When I examine them in finder, nothing jumps out at me that is different. Have you any experience with this happening? Thanks, Deb

Here is a screen shot. Some of the blue folders will show all images nested in the projects below, some show nothing. ie: 2013 shows all, but 2012, shows nothing. You must click on each individual project to reveal the items contained. I would like to click on each top level folder and see all items nested beneath. There must be something I'm doing different, but for the life of me, can't figure it out. Why some show and some don't.

Only detect presence or absence of top level folders.

If a top level folder is missing, please have Lightroom assume that all subfolders are missing on revmovable drives. If the drive is reattached and LT sees the top folder again, please let it assume that all the subfolders are there also, until we use a file that is not actually there.
Long winded waiting on drives after reconnection is not necessary. Or at least give us an option to tell Lightroom that the drive is actually there, don't bother checking further.

Unfortunately it does not working. I am using jboss AS 7.
Structure details:
- ear contains war
- the war contains the beans.xml (with alternative entry) in WEB-INF
- jar B is located in war in WEB-INF/lib (jar B contains also beans.xml in META-INF)
- injection point is in a JSF controller (jar in WEB-INF/lib in war)
Always I1 is injected. But I do not know if I explained it clearly. I1 is always present. I2 is optional but shall have a higher priority.

Cannot Create Folder at Top Level of Documents Library

Operating System: Windows 7 Enterprise, 32-Bit
Environment: Windows 2003 domain
Security: Local Machine admin, and domain admin
Documents Library is redirected via Group Policy to
\\servername\home\username
Navigating to Libraries\Documents, there is no "New Folder" button available at that top level of the library. When using File menu => New => Folder, I get "Unable to create the folder 'New Folder' File system error (512)."
Looked that one up using Google, er, I mean Bing, and found articles about it being an old DOS\Win95 issue with the 512 max limit on the root drive. Am familiar with that problem, and this ain't it. Less than 30 folders at the root level, and none more
than 20 characters long.
From inside an Application, if I try to save to my Library\Documents folder, I cannot save a file to the root level. I get "To save here, you must first include a folder in the Library."
At this point where I am looking to save a file, I also cannot type a folder name for navigation, as I am used to doing with previous OS's. So in my address area, I have Libraries\Documents, then I have a subfolder called "important." If I type
the word "Important," expect the system fo navigate down into that folder. Instead I get "To save here, you must first include a folder in the Library." If I type "Important\" I still get the same error.
Navigating to \\servername\home\username, I am able to create a New Folder at the top level from a Windows Explorer window, or from inside an application such as Word.
Mapping a drive letter to \\servername\home\username also will allow me to create a New Folder at the top level, from a Windows Explorer Window, or from inside an application.
From a command prompt, I am able to get to the drive letter and create a new folder.
With the drive letter mapped, going back to Libraries\Documents, I am still unable to create a new folder that way.
I read these two threads, both of which sort of die off with no real answers. So I've started my own.
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/4ea2f28f-8487-40cf-abb0-745916e72b7a
http://social.technet.microsoft.com/Forums/en/w7itprosecurity/thread/ae2505ce-8a6b-493b-9473-a0dca215fd34
Any Help?

Hi,
Regarding your problem, it seems that the user didn’t have appropriate permissions to create folders. To get it work, NTFS and Share permissions must be configured
appropriately.
Here are the Share and NTFS Permissions needed on the File Server Shares and the steps to do so:
NOTE: The $ symbol should be used to hide the existence of the share.
User Home Share Configuration:
Here are the Share and NTFS Permissions needed for Home Directories:
a. The Share permissions (Sharing Tab): Share Named: <HOME>$
Administrators: Full Control
System: Full Control
Authenticated Users: Full Control
b. NTFS Folder Permissions (Security Tab): Turn off inheritance on the Folder named <HOME>, and copy the permissions. (Uncheck "Allow inheritable permissions
to
propagate to this object")
Administrators: Full Control
System: Full Control
Creator Owner: Full Control
Authenticated Users: Read & Execute, List Folder Contents, Read
c. On the NTFS Folder Permissions Click the Advanced Button. Then highlight Authenticated Users, Select View/Edit
d. On the Permissions Entry for <HOME>, "the Apply onto" change to: "This folder
only"
e. Click OK
f. Click OK again.
More reference, please read the following document:
Windows Server 2008 Share/NTFS permissions on home
directories/folders
Redirect the Documents folder to a network share
Please note: we provide the third party link for technical use
only. There may be some changes without notice, Microsoft doesn’t guarantee any accuracy on contacting information.
BTW, as this issue is relevant to Windows Server 2003, please post in
Windows Server forums for solution as well.
Hope it helps.
Best Regards
Dale
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Adding Content To the Top-Level of Navigation bar ?

Hi,experts ,
   i have a problem with adding content to the top-level of navigation bar ?
I have the authority of administration.I have added a customizing role with the entry-point property to myself userid . I have checked my navigation-target page's property can be visible in top-level navigation. I checked my my display level is set as 2 .
   However ,i dont get the folder content at the top-level navigation.Anyway,when i check the delta link trace,there is no folder that connect to my role .
   Anyone helps me out ?
Thanks in Advance .

Hi Eleanor,
If you already created a role with an entry point and assigned it directly to you user, you may just have to refresh the portal page. You may also check the authorizations of you role.

Did 10.6.5 alter the permissions of the top level of the startup volume?

Since applying the 10.6.5 update it seems that non-admin users have read/write access to the top level directory of the startup volume. That means that non-admin users can create items there.
I am wondeing if this is a normal change for 10.6.5 or if something is weird with my system.
We updated from 10.6.4 via Software Update. This machine has only ever had Snow Leopard installed on it.
(Note that top level sub-folders such as Library and System do not appear to be affected by this)

Are you referring to the ownership and privileges for the drive? If so then if they aren't set at the default it's because of something a user has done because the installer makes no such changes. You can return them to the default as follows;
1. Select the drive and Press COMMAND-I to open the Get Info window.
2. In the Ownership and Sharing section at the bottom is a checkbox labeled, "Ignore permissions on this volume." If the box is checked then click on the lock icon and authenticate. Uncheck the box.
3. Open the Terminal application in the Utilities folder and enter the following command then press RETURN:
sudo chown root:admin "/Volumes/Macintosh HD"
You will be asked to enter your admin password which will not be echoed.
If you now click onto the still open Get Info window you should now see the proper info:
Owner=system with r/w privileges
Group=admin with r/w privileges
Everyone is read-only
Click on the lock icon to prevent any changes. Close the window then quit the Terminal.

In List View, how can I move an item from within a subfolder up to the top level of the window's parent folder?

Up 'til now, from System 7.1 to Tiger—I skipped Leopard—you simply dragged the item onto the folder window's titlebar (since that folder's icon was, naturally, not in its own window) and BINGO! there it was, at the top level. Nothing I can think to do in Snow Leopard seems to work.

Thanks. Most definitely does, although when experimenting I found the left window edge was closer, and 'scrubbing' the item just out of the window and back in seemed to fit the underlying file and folder metaphor better to my mind than just dropping it any old where in the window.
And 'any old where', at any old speed doesn't always bring up the oh-so-subtle blue border that says, "I get it, you wanna add something to this window, hit me." That's The Clue. There seems to be an invisible line you hafta cross, and some kind of deliberate pace you hafta hit. Too fast and SL doesn't seem to always take it seriously. But that left edge scrub can be quite fast.
Sorry about the over hasty denial, I was checking my facts and editting to say you were right when the board was shut for some sort of maintenance, and my bad became permanent. Please forgive.

How do I keep folder settings below the top level

There's a certain Finder setting I prefer for folders regarding icon view. I use a size and arrangement that works very well for me. After replacing my older MacBook Pro with a new MBP and transferring all my data, the setting I prefer only works at the top level of any given folder. Any enclosed folder needs to be individually set to my preferred settings. Is there a universal setting in the Finder for folders that will include all enclosed folders?

There's a certain Finder setting I prefer for folders regarding icon view. I use a size and arrangement that works very well for me. After replacing my older MacBook Pro with a new MBP and transferring all my data, the setting I prefer only works at the top level of any given folder. Any enclosed folder needs to be individually set to my preferred settings. Is there a universal setting in the Finder for folders that will include all enclosed folders?

Adding permissions at top level folder

Similar Messages

Maybe you are looking for