Skip to main content

Hi,

 

After following this documentation, as well as enabling and configuring the “Enable Apple Silicon Patching” worklet (with the correct admin credentials) I have been unsuccessful in my attempts to remediate the `_automoxserviceaccount` SecureToken authorization.

  1. First I tried sudo /usr/local/bin/amagent --adminuser '<admin_username>' --adminpass '<admin_password>' but received:
    1. ENABLE Automox service
      account given account not found 
    2. I tried this remotely (via mdm) and locally, same result.
    3. I confirmed that _automoxserviceaccount exists at /Local/Users/_automoxserviceaccount
    4. The admin user has SecureToken enabled
  2. Then I tried the supplied automox worklet “Enable Apple Silicon Patching”
    1. I supplied the same valid as variables in the worklet:
      1. SECURE_TOKEN_ACCOUNT="_automoxserviceaccount"
        SECURE_TOKEN_ADMIN_USER="<Admin user>"
        SECURE_TOKEN_ADMIN_PASSWORD="<Admin Password>"
      2. This did not use the supplied creds and instead prompted the logged in user to enter their password. Upon entering the password on the device, it enabled Secure Token

I’m trying to avoid prompting end users for credentials. Am I missing something?

 

Thank you. 

Hey ​@ddb! 

So first would try removing the Automox Service Account entirely using this command.

sudo dscl . -delete /Users/_automoxserviceaccount

Then try the process of passing it again.

Something to note is that if you have any MDM rules that rotate passwords this would interfere with the Service Account and break the password. You would need to exclude the account from rotating.

 

For the Worklet I would review the readme text in the to ensure its been configured properly. If the variables are input incorrectly or fail it will attempt to use the currently logged in user to grant the secure token causing the prompt to the end user.

Hopefully that helps! If not I would recommend submitting a support ticket so we can triage further.

 

Have a great day!

Terms & ConditionsCookie settingsAccessibility statement