Casper Remote "An incorrect Username/password is entered for this computer

@EliasG did you try physically logging into the machine, and are you getting the same issue?

I had this problem on some of my machines, I was using an older version of Casper imaging and it was not creating the Management Account. Or it is possible the Management account in your JSS does not match the Management Account password on the machine. I would check to see if this is the case first.

@GaToRAiD I was able to log in the laptop and still the same issue.

@rlandgraf all casper is up to date. We dont image our laptops. i'm pretty sure the account management password is accurate in the jss. I will double check. It's weird because it only happens to a few machines.

@EliasG When I've seen that, I:

(either seems to work just fine)

/usr/sbin/jamf removeFramework
or
sudo jamf -removeFramework

Then I re-enroll it:

sudo jamf enroll -prompt

Using the proper account info for enrollment. Alternatively, you can install a new QuickAdd.pkg. Once that is done, it is usually cleared up. Might be a simpler way, but that has worked for me.

If you do a jamf removeFramework, then you will have to use a QuickAdd to re-enroll since the jamf removeFramework removes the jamf binary, so a jamf enroll command would not be possible.

This happened to us A LOT just recently. It was suggested at our Jump Start to randomize the management password, so we did. It has bitten us in the butt because somehow half of our machines' mgmt pw got "out of sync" with the JSS' mgmt password.

I tried removing the framework as suggested here, but that does not actually solve the problem because removing the framework doesn't remove the management account (in all of our cases, at least). So we had to -removeFramework, delete the user through dscl, manually remove /var/jamfadmin account, then re-enroll with a QuickAdd package.

After painstakingly either having to touch or remote into machines to fix the issue, I had forgotten that the Jamf binary contains a "resetPassword" command that specifically resets the mgmt pw. I also noticed these machines could still run policies, so I created a run once policy with the "jamf reset password -username ourMGMTaccount -password ourPassword". We have seen a drastic decline in the wrong username/password error since this implementation.

Most likely you've got set in a Imaging Configuration, under management, a management account. However NOT ticked "Create the management account during imaging if it does not already exist".

We experienced this result and found that machines were being imaged and the management account wasn't being created after imaging. What really confused us was the management account wasn't present on the mac however was able to run policies etc just as if the machine had the account.

In configurations, and in quick_add.pkg's. Be sure you select create management account if does not exist.