policy failure with "The package could not be verified."

kyoung
Contributor

A policy I have set up is failing with the error message

"Installation failed. The package could not be verified."

Anybody got any ideas what I did wrong?

Thanks.

3 REPLIES 3

chriscollins
Valued Contributor

How was the package added to the JSS?

Did you by any chance add the package manually to your distribution point or copy a new version of the package to it and then change the package name or information in the JSS web interface or just copy a new version over the old one and did nothing else?

Asking because when you use casper admin to upload a package to the distribution point, it writes a checksum to the database and if the package doesn't match that checksum it will fail to install.

Our primary distribution point is on BOX so we can't use Casper Admin to upload packages so we have to manually upload them and then create the package object in the JSS via the web interface. We had to turn off checksum checking in the JSS because of this.

kyoung
Contributor

I believe everything in the jss got there via Composer and Casper Admin. I have been trying to put a version number and/or a date of creation on any pkg I make so they have unique names.

bentoms
Release Candidate Programs Tester

@kyoung Can you try with the "checksum checking" off as @chriscollins advised?