Posted on 03-24-2022 11:28 AM
After the upgrade to MacOS 12.3, the Jamf login screen went away, i found that running this command would fix the issue :
/usr/local/bin/authchanger -reset -jamfconnect
Although after creating a policy and trying this through execute command i get the following error:
LLVM Profile Error: Failed to write file "default.profraw": Read-only file system
I tried the command in terminal manually with sudo permissions and it did work.
How can i fix it ?
Posted on 03-25-2022 07:20 AM
Executing the command via Jamf policy, I also got this as a script result.
Posted on 03-25-2022 07:45 AM
Hi Joshuaaclark, thanks for helping me out. I have created a new policy and added the above command under Execute Command in Files and Processes. Is that what you meant ? because i still get the error.
What am i doing wrong here ?
Posted on 03-25-2022 07:49 AM
No solution. I was posting here to say I am having the same issue. I am also looking for help.
Posted on 03-31-2022 12:50 PM
Same here. Applied the policy but getting the "LLVM Profile Error: Failed to write file "default.profraw": Read-only file system" error
Posted on 04-06-2022 07:59 AM
Also receiving this on a few macbooks after upgrading to Monterey.
Posted on 05-25-2022 11:21 PM
Posted on 07-29-2022 05:19 AM
Any one find a fix?
Im getting this as well
Posted on 07-31-2022 05:00 PM
Unfortunately, we ran into this issue with a Macbook from 2017 updating to Monterey. We ended up having to try the following in Recovery Mode to disable JAMF connect.
Posted on 10-11-2022 01:08 PM
the link you posted does not work...
Posted on 11-03-2022 06:27 AM
Faced the same with Jamf Connect v 2.5.0, so I'd suggest you to check yours and update if possible.
It was fixed in a Jamf Connect v 2.8.0:
Posted on 11-04-2022 08:13 AM
I'm getting this too, with Jamf Connect 2.16 installed on 12.6.1. Anyone have a solution? I'm just trying to reset authchanger to default (no Jamf Connect) for some testing.
Posted on 11-07-2022 12:39 PM
I am also getting this with Jamf Connect 2.16 installed on 12.5.1
Posted on 11-07-2022 01:01 PM
We saw this error but upgrading to 2.17 resolved it.
Posted on 11-28-2022 09:46 AM
I just got this on 2.17.0 trying to reset authchanger to Jamf Connect.
Posted on 12-07-2022 07:06 AM
Same.. Just pushed v2.17 and have seen this in the deployment logs. Does it affect any functionality?
Posted on 02-02-2023 10:08 AM
Im asking one of my users now about this. It says his failed and im not sure if its a problem or not