Timeline for Check 'effective permissions', 'effective access' from command-line, Windows/NTFS
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 15, 2020 at 5:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 13, 2020 at 5:57 | comment | added | LeeM | Also, for having to use your admin account to connect to a separate system, this is actually best practice. Look up "golden ticket exploits" to give yourself a fright. However, connecting to multiple boxes can be painful - if you have enough systems to maintain, perhaps consider asking for a "jump server" that you can log into with your admin account to maintain other systems | |
| Feb 13, 2020 at 5:55 | comment | added | LeeM |
If your users have Full Control over any NTFS directories, remove it. At most, they should be set to Modify. Assuming you set up your top-level directories so that permissions are inherited to all child files and folders, any such moves should not create this problem with odd permissions. by default files will inherit permissions at the destination folder. If you're copying files via xcopy or robocopy, stop using xcopy /x /o or robocopy /sec, /dats or /copyall switches
|
|
| Feb 10, 2020 at 20:52 | answer | added | Semicolon | timeline score: 2 | |
| Feb 10, 2020 at 19:56 | history | asked | gregg | CC BY-SA 4.0 |