Source
r/crowdstrike•
SeriouslyUser59

M1 Macs, JAMF and the MDM profile

Troubleshooting

Just a heads up for anybody else fighting this. On any M1 macs I couldn't get the MDM profile to load after I signed it and pushed it through JAMF with the fun error 'The operation couldn't be completed. (SPErrorDomain error 1.)'.

The solution seems to be editing the mobileconfig file a bit:

  • drop the <dict> section containing the old kernel extension stuff (be sure to leave everything else)
  • on line 6 & 8 replace the UUID with a new one
  • change line 14 to something like 'Falcon Profile M1'.

(Those last changes are due to the fact JAMF won't import the 'same' profile twice.)

Once you do that, resign the profile and upload it, then scope it to your M1 Macs (excluding them from the old profile) and boom

Note: M1 mac's might not be supported yet not really sure

Posted Mar 10, 2021, 10:55 PM UTC · edited

75
snoobo0•

Not supported yet but thanks for the info.

2
bkrivelow1•

What are you using to edit the config file? Just started at a new company and several of the m1 macs are facing this issue.

1
SeriouslyUser59OP•

I was just using VSCode, it's just an XML file. Then I used security to sign it before uploading to JAMF

security cms -S -N "NameOfCert" -i Unsigned Falcon\ Profile.mobileconfig -o Signed Falcon.mobileconfig

1
bkrivelow1•

Sorry, I'm super new to this, do I grab a new uuid like from Online UUID Generator Tool ?

Also, I'm assuming the old kernel extension information is in lines 112-129?

1
SeriouslyUser59OP•

Yep any UUID should work, it just has to be unique. Also that looks correct, line 112-129.

1