We updated to 10.42. We are seeing an error where every single policy that has a package fails to install the package but the rest of the policy goes through. So if the policy has a package payload and a script payload, the package fails with error 1200 and the script runs as expected. We are able to open Jamf Admin and even connect to the share directly. All file share distribution point settings are correct, the SSL cert is valid, and we verified all password are correct.
Solved! Go to Solution.
“Removal of unverified SSL certificates in Jamf Pro”
”The option to use an unverified SSL certificate for Jamf Pro has been removed. Jamf Pro on-premise environments using a trusted third-party certificate and all environments hosted in Jamf Cloud will see no changes. Customers with on-premise environments using Jamf Pro's built-in certificate authority to issue SSL certificates need to move to a trusted third-party certificate. If you do not already have a trusted third-party certificate, make sure that the Skip certificate installation during enrollmentcheckbox is not selected in User-Initiated Enrollment settings in Jamf Pro. If you are unsure whether or not your environment uses a trusted third-party certificate, contactJf Support”
Your distribution points can now only use https as well. If they were setup for http (like mine were), then the 10.42 update removed that option and automatically re-configured it in Jamf Pro to use https.