Skip to main content

I am testing moving users from Admin to Standard and I am running the command below in Files and Processes in a policy and it works and makes the user Standard, but when I reboot it reverts back to Admin. The machine was bound to the domain (we are working to get away from that), so I thought maybe that had something to do with it, and I unbound and ran the policy again and when I rebooted, I was back to Admin again. I have no policies applying post reboot and none of my profiles appear to be doing anything in terms of user rights. Does anyone know what I may be missing and how I can keep this from happening?

 

dseditgroup -o edit -d myusername -t user -L admin

We are testing Jamf Connect and turns out it was Jamf Connect elevating the account. Whoops.... nothing to see here, please disperse. 

@mfletch we are doing something similar. We want to change everyone from Admin to Standard accounts on the Mac but on reboot, the accounts are reverting back to Admin. 


Context: we're on Okta and using OICD. Looking through the Jamf Connect Documentation, I can't figure out what setting for the config profile for login and/or connect that elevates or changes this. 


Which key or setting would this be?

@mfletch we are doing something similar. We want to change everyone from Admin to Standard accounts on the Mac but on reboot, the accounts are reverting back to Admin. 


Context: we're on Okta and using OICD. Looking through the Jamf Connect Documentation, I can't figure out what setting for the config profile for login and/or connect that elevates or changes this. 


Which key or setting would this be?


Assuming you're using Jamf Connect, when you set up Jamf Connect with Okta, there should have been a group that you put all users in to be either Admin or Standard user, in your case it sounds like everyone was added to the Admin group. My guess is that you may need to do some investigation work to find out what group everyone is in and test removing someone and ask them to reboot and log back in and if they are then Standard user, you've found your culprit. 

Reply


Terms & ConditionsCookie settings