New answers tagged

2

What blaughw said. You might want to look into group policy. Specifically, restricted groups--if you restrict the administrators group, this setting will add users and groups to to the administrators group as well as kicking other users and groups out--or a start up script that includes a line along the lines of net localgroup administrators yourdomain\...


2

Domain Admin should have permissions. Typically, the Administrators built-in group on a workstation lists Domain Admins group for the domain in question. Has the user logged off and logged back on to the workstation since having rights assigned? Open up lusrmgr.msc (Local Users and Groups) on the target workstation and ensure the domain groups in ...


4

If the user is going to log in, they're going to have to be able to read some bits of the file system. You simply can't launch an interactive shell without access to certain files. If all they need to do is authenticate far enough to tunnel other connections (including, as in this case, taking advantage of the ssh SOCKS proxying facility), it's better to ...


0

Could you use a chrooted ssh user or group instead? I've never implemented it myself, but it seems this may help: https://www.howtoforge.com/chrooted-ssh-sftp-tutorial-debian-lenny The tutorial is for Lenny, but hopefully this wouldn't of changed too much.


1

No, nothing unexpected will happen, since the system uses the SYSTEM principal and you aren't planning to delete that. However, what you are planning to do won't stop an administrator from modifying or removing the object. Administrators always have the SeTakeOwnershipPrivilege privilege, which allows them to set the owner of any object to themselves (or a ...


0

Run groups command using jenkins. Do you see a docker group? If not, try to reboot that Jenkins slave. Or just kill the Jenkins slave.jar process: ps aux|grep jenkins



Top 50 recent answers are included