The management account name and/or password on those Macs may not be matching up with what the JSS has stored for them in its database. If the jamf binary can't use a local account to authenticate because the information its using is wrong, its going to end up prompting the user instead. Check that and try them again.

You're good!! Happy new year!

is there a way to force them back to defaults... easily?

To get the client back in sync, I've had success deleting the management account on the client, and then re-running the QuickAdd package. This doesn't seem to damage any data in the JSS for that Mac.

Alternatively, a less invasive way is as follows:

1. Go into the JSS inventory information for the affected client, and click the ellipsis (...) on the Computer Information page.


2. Change the SSH password for the management account to something you'll remember for the steps that follow.


3. Go to the affected client, and change the password on the management account to match what you just set in the JSS for that client. This can be done using the passwd command from a root command prompt (sudo -s to get to a root command prompt, then type passwd <management account shortname>)


4. Wait for the inventory to refresh, the timeframe for which will vary depending on your environment. Or, try using Casper Remote to force an inventory refresh. If successful, all should be fixed.