Posted on 05-23-2022 09:13 AM
Jamf Composer was used to build a simple package
I’ve since been able to successfully build, sign, wrap and deploy using terminal however I would like to figure out what went wrong with the Composer build as I see the need for much more complicated packages in the future.
Because I removed the policy that was failing and rebuilt a successful one I no longer have the error code Intune spit back for this post. There was no useful error message, just the error code close to, but not exactly, 0x87D13BA2. I stress this was not the exact error code as I was unable to find the exact code ANYWHERE, not even from Microsoft documentation of error codes.
I post this hoping someone has run into this issue before and found a way to make Jamf Composer built pkg files deploy successfully. If required I’ll build another and deploy to get the exact error code. Hoping it doesn’t come to that.
Thank you all in advance.
Posted on 05-05-2023 03:24 AM
Hi @Pike, did you manage to fix it? I'm currently in the same situation and it's quite frustrating :(
Many thanks