# get acl and dir commands

is there an easy way to possibly combine a DIR command and the powershell get-acl command to get a list of acl's for all folders (folders only, no files, or sub directories) in a share.

i.e.\\server\share\dir1 \\server\share\dir2 \\server\share\dir3

or any other way to acheive this within powershell?
LVL 3
###### Who is Participating?

Batchelor, Developer and EE Topic AdvisorCommented:
Something like this?
dir C:\temp\ee,c:\temp  | ? { $_.PsIsContainer } | get-acl  0 Author Commented: new to powershell, but can you explain what the -psiscontainer switch does, I need the command to automatically list only root level directories, as opposed to hard code them. 0 Batchelor, Developer and EE Topic AdvisorCommented: PsIsContainer isn't a switch, it is a property of filesystem objects. If set, the object is a folder, else it is a file. To explain above line, I'll have to dissect it: dir a,b,c,d: you need to use the comma here, because that makes an array, and you need to provide a string array if you want to stuff in more than one folder/file name. dir a b will use the default position resolution for the get-childitem cmdlet (which dir is an alias for), assigning "a" to the first (= path), and "b" to the second (= filter expression = wildcards). | ? {$_.PsIsContainer }   filter to get only folders. ? is where-object, and $_ is "the current object of a pipeline" (you can see that in a lot of commands). The result is then just pushed into get-acl, which knows about how to handle filesystem objects. It could also handle path names as plain string if needed, but passing thru the filesystem object is much more straight-forward if available. 0 Commented: New to Powershell? The biggest thing to remember is that when powershell returns things to you, it is NOT returning just the text you see but it returns entire objects. To see what it is returning use the Get-Member cmdlet. Example - create C:\Temp Then run: Get-ChildItem c:\temp| Get-Member  So you're running the Get-ChildItem command and it returns a powershelll object. Then you're piping that object to Get-Member that will show you all the properties (well, members really. Because it will also contain things like methods and other stuff) that the object contains. As Qelmo said, when you do$_ you are selecting the current object that has been returned and when you add .PsIsContainer you're selecting just that property of the current object.

Does that make sense?
0

Author Commented:
makes sense, thanks both..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.