PezzaD84
PezzaD84
Hi @teezyyoxo This error message is usually an indication that the device name or serial is incorrect. Can you share the logs please and I can have a look to...
@teezyyoxo I would look at your API account and check the permissions. I sometimes find if the account is new it needs to log into jamf as a user.
Really sorry for the delay on this ticket @MacJediWizard I completely missed this. Can you both provide some logs for me please? The JAMF policy logs and the LAPS logs...
@aanklewicz Can you please share the local logs from /Library/.LAPS/logs Also what OS version are you running?
@gitjoob your extension attribute key has been changed. The data string should be as follows `-d "$cryptIDLAPS CryptKeyString" ` The name value has been edited or removed. The other log...
Hmm I wonder if this is an OS 15 issue? I can see in the logs the password validation failed so possibly the passwords became out of sync and thats...
@aanklewicz I cant seem to replicate the issue and only get bad decrypt errors when the secret or crypt key are incorrect. Can you try the below and see if...
Thanks for flagging this @gitjoob Thats been updated now.
@aanklewicz It should definitely be changing the secret key otherwise the new unique password will not be able to be decoded. It should be failing if the key is not...
@aanklewicz I've just release v2.3.1 which includes a small debug mode which might highlight some of the issues you are seeing. Hopefully this will help us figure out whats going...