Skip to main content

Hello,

 

I am trying to create a configuration profile on Jamf to deploy it to my mac laptop.

The .mobileconfig is built using the template mentioned here (docker.mobileconfig): https://docs.docker.com/enterprise/security/enforce-sign-in/methods/#macos-configuration-profiles-method-recommended 

When I try to upload this in Jamf (we use Jamf Pro) using the “Upload” option shown below, it fails with the error “File Cannot be processed”

 

I am able to create the profile using the “New” button where I copy and paste my profile in the Property List box.

I don’t suspect anything wrong with the template structure as using “New” button I am able to upload it and also I am  able to directly add my profile on my mac laptop.

Any idea why I am getting “File Cannot be processed” error when I use “Upload” option ?

I have reviewed few old posts reporting similar error, but they are slightly different than my issue.

Appreciate any help.

instead of using what docker said, you can follow these instructions with that plist they gave:

https://learn.jamf.com/en-US/bundle/technical-articles/page/Deploying_Custom_Computer_Configuration_Profiles_Using_the_Application_and_Custom_Settings_Payload.html

 

Or better still, create a custom profile schema so you can edit it in the gui instead of a plist.  I’ll end up creating a schema before too long and I’ll post it here if I remember to do so.

 

​@Chubs Thank you. I will  follow the instructions from the link you shared and give it a try.

In case you didn’t get a chance to create a schema, appreciate if you can point me to some references on how to go about it. Thank you.

edit: found some info on custom schemas here: https://github.com/Jamf-Custom-Profile-Schemas Will give it a try.

I would also like to know if Jamf logs any more details on the “File cannot be processed” error, just to understand why it couldn’t.

I would also like to know if Jamf logs any more details on the “File cannot be processed” error, just to understand why it couldn’t.


First place to look is in the JSS Logs.

Usually it means that the file is either:

  1. XML is formatted incorrectly (inadvertent spaces, missing pieces, etc. etc.)
  2. A utility wasn’t leveraged to convert it to a mobileconfig file

 

Check into the use of plutil. I believe there’s a convert option on it (been many moons since I’ve used it) or possibly even a linting option via that utility to validate the mobileconfig. I quit making custom mobileconfigs long ago due to the schemas options. 

Terms & ConditionsCookie settingsAccessibility statement