Yup, you can’t use icacls or any of those tools to view who owns a file/ folder. Got to use the dir command with a /q switch.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
C:\Users\Rakhesh>dir /q Volume in drive C is WINDOWS Volume Serial Number is FA14-803C Directory of C:\Users\Rakhesh 02/18/2015 10:47 AM <DIR> BUILTIN\Administrators . 02/18/2015 10:47 AM <DIR> NT AUTHORITY\SYSTEM .. 02/16/2015 05:35 PM <SYMLINK> BUILTIN\Administrators .gitconfig [d:\Dropbox\AppData\.gitconfig] 02/18/2015 10:57 AM <DIR> CAIN\Rakhesh .ssh 02/19/2015 02:45 PM <DIR> CAIN\Rakhesh Code 02/19/2015 05:44 PM <DIR> CAIN\Rakhesh Desktop 02/09/2015 10:11 AM <DIR> CAIN\Rakhesh Documents 02/22/2015 03:48 PM <DIR> CAIN\Rakhesh Downloads 10/14/2014 06:15 PM <JUNCTION> BUILTIN\Administrators Dropbox [d:\Dropbox] 02/04/2015 10:09 AM <DIR> CAIN\Rakhesh Favorites 11/22/2014 11:17 AM <DIR> CAIN\Rakhesh Searches 11/22/2014 11:17 AM <DIR> CAIN\Rakhesh Videos 12/30/2014 10:29 PM 3,211,264 CAIN\Rakhesh WAStorageEmulatorDb34.mdf 12/30/2014 10:29 PM 851,968 CAIN\Rakhesh WAStorageEmulatorDb34_log.ldf 4 File(s) 4,063,815 bytes 18 Dir(s) 12,382,769,152 bytes free |
Can run it against a particular file/ folder too to get the permissions of just that.
Weird! I mean, why not make this a part of the usual ACLs tools??