weird casper ssh oddity

[tlarkin]

I have a client machine that has been imaged, has the jamf binary present and updated to 7.2 but it does not show in the JSS inventory. I then ssh into this machine using the same account Casper uses to verify I can ssh, and it works. When I run recon I get the "bad user name" error when it tries to update the inventory.

However, I have not changed the ssh account it uses, and no one but me in the whole enterprise has that password. the account is never used outside of authentication for the casper client.

I am at a loss, anyone ever see this?

Pointers?

Thanks

Tom

[#2]

Hey Tom-

We have seen that when the local account password is correct but
the management password for that system in the database is housed. For us
this happened because the local account was setup correctly but the password
hash in the recon command that adds the machine to the DB was messed up. To
fix it, we used a policy to reset the management password. Make sense?

Jon

[tlarkin]

Yeah what I did, was reset the ssh account, then added the machine manually by MAC address then recon, all is good. Some how something got corrupted in there.

Thanks