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
Error 1200 any Policy with a package- the package fails, but the share is mountable manually
+5Best answer by MikeRitacco
OK- our issue has been resolved. It turns out, our Cipers were incorrect in the Windows Server. Apparently, when updating to 10.42 the Cipers on the SSL cert also needed to be changed.
+13On-premise server?
Sounds like:
“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”
https://docs.jamf.com/10.42.0/jamf-pro/release-notes/Deprecations_and_Removals.html
+5On-premise server?
Sounds like:
“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”
https://docs.jamf.com/10.42.0/jamf-pro/release-notes/Deprecations_and_Removals.html
Thank you for the reply!
Yes, on Prem. We are in fact using a trusted SSL certificate. So we were prepared for that coming into 10.42.
+8Thank you for the reply!
Yes, on Prem. We are in fact using a trusted SSL certificate. So we were prepared for that coming into 10.42.
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.
+5OK- our issue has been resolved. It turns out, our Cipers were incorrect in the Windows Server. Apparently, when updating to 10.42 the Cipers on the SSL cert also needed to be changed.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.