GeneratedUID: ABCDEFAB-CDEF-ABCD-EFAB-CDEF00000050 Normally the admin group would look something similar to this on almost all Macs: dsAttrTypeNative:record_daemon_version: 4850000 If it's there, check the contents of the admin group with dscl. list /Groups A group named "admin" should be one of the items that shows up in the list. Taking a shot in the dark with this, but, have you confirmed that the local admin group still exists on these affected Macs? This would be done with something like dscl. Sorry for the long winded post, but no one in my organization knows what to do. My conclusion is that the permissions are wrong and that's why sudo fails, but I know nothing of why this has happened or if this is the only anomaly regarding these permissions and how to repair it. On the non working Macs, Fetching is in place of admin, wheel is read only, and everyone is no access. Admin and wheel are read only, everyone is no access. I looked at permissions of the sudoers file on a working Mac. They were not imaged, they all work as expected with this exception. OS and apps from our JAMF server and worked normally until I noticed sudo failing Wednesday. These are computers that were installed with a fresh 10.14. I do know that I have not edited the sudoers file, I can log into a local admin account and run normally if I don't use terminal requiring sudo, I can log in as an AD admin and get the same error message sending terminal commands using sudo, and logging in as a standard AD user I can su to a local admin account, but can't run commands using sudo. I am not a Unix or Linux expert to understand why this is occurring or how to fix it. I am trying a simple jamf recon and the result is: I have tried local admin user, ARD send Unix command as root, and JAMF Remote. A random number of Macs in my environment have lost the ability to use sudo from a terminal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |