I am also guessing it's not specifically Jamf Admin 10.35, or else we
would see a lot more comments on this forum. The package that generated
the "package failed to save" error in Jamf Admin 10.35 did not show up
at all when I went to update a policy...
I'm having the same problem with our on-prem Jamf Pro server since
upgrading to 10.35 today. We get the same error message when uploading
packages using Jamf Admin 10.35. I went to another Mac and used Jamf
Admin 10.34.2 and the same package uploaded...
So I've been pulling my hair out dealing with this problem for the last
few days. It seems they changed the Sophos Installer.app between Aug
2017 and October 2017. With Sophos Endpoint 9.6.6, I had to use the
following script: #!/bin/sh chmod a+x