macos local user changed to admin in hexnode keeps reverting to standardSolved

We ran into a very similar issue, and when we talked with support, it turned out to be a bug with older agent versions causing the role to revert!

Before jumping to the agent update, you should check a few scenarios first, since this can also happen if the local account state on the Mac is being refreshed after the role change:

1. Confirm whether the affected account is a local macOS account linked to an IdP account, rather than a manually created local-only account.
2. Review whether any macOS policy or account management setting is configured to migrate or synchronize local accounts as network accounts.
3. Check the device action history to confirm whether the admin role change completed successfully and whether any later sync or account-management action occurred.

If those all look good, make sure the Hexnode agent on the Mac is updated to the latest version.

Hi @aurora,

@jayceon is exactly right! A known issue in earlier agent builds could cause the local user role on macOS to revert from Administrator to Standard after being changed from the portal. This was fully addressed in Hexnode agent version 29.0.5.

Here are the recommended steps to resolve it:

1. Update the Hexnode agent on the affected macOS devices to version 29.0.5 or later.
2. Allow the device to sync with Hexnode after the update.
3. Run the Hexnode action to change the local user role to Administrator again.
4. Verify the user role locally on the Mac and in the Hexnode Local Accounts view.

If the user still reverts to Standard after the agent is updated, let us know and we can check for any specific macOS policies managing your local account migrations!

Best regards,
Eden Pierce
Hexnode UEM

That was exactly it. I checked the affected devices and they were on an older agent version, so I updated to 29.0.5 and the accounts have stopped reverting to standard. Thanks for the help!