error message using Casper Remote after upgrading to v6

[Jeff-JAMF]

I upgraded to v6 last week - seemed relatively painless and problem-free.

However, when I tried to use the new Casper Remote for the first time
today, I got this error message:

Sending Wake On LAN command...
Opening SSH Connection to 10.1.1.27...
Authenticating...
Successfully authenticated.
Verifying Computer's Identity...
The MAC Address has been verified.
Checking Operating System Version...
Running Mac OS X 10.4.11 (8S2167)
Verifying /usr/sbin/jamf...
/usr/sbin/jamf is current (6.0)
Verifying /usr/sbin/jamfvnc...
/usr/sbin/jamfvnc is current (4.00)
Verifying /private/etc/jamf.conf...
The jamf.conf file was recreated.
Preparing Management...
Downloading AS36117.dmg...
Verifying DMG...
Error: The downloaded package could not be verified.
Enforcing Management Framework...
The Management Framework will be enforced as soon as all Policies are done
executing.
Submitting log to https://casper:8443/...
Finished.

No matter what dmg file I try to deploy, I get the same error message
("Error: The downloaded package could not be verified.). All of these DMGs
were successfully deployed prior to the upgrade.

Any insights from the JAMF universe?

Thanks

Jeff Johnson
Technology Coordinator
Glendale-River Hills School District
Glendale, WI 53209
jeff.johnson at glendale.k12.wi.us

[ernstcs]

If you try to manually mount that DMG package on the share does the OS say it's bad? Otherwise I'd check permissions on the package.

Craig E

[tatiang]

That did it... thank you! I disabled HTTP downloads and that fixed the
problem. I'm not sure how that got enabled, but apparently it had been.

Tatian

[tatiang]

I am seeing the same thing today. I have a call into JAMF support.

I can mount the DMG file and I can even install it using Casper Imaging. But if I try to install the package using Casper Remote, I get the error
mentioned ("The downloaded package could not be verified."). This seems
independent of which package or which computers I use. These were
packages that installed fine in the past.

---

Tatian Greenleaf
Associate Director of Technology
Saint Mark's School
(415) 472-8000 x1014

[winkelhe]

VErify permissions on the said packages. In my experience this has always been the issue.

--
Eric Winkelhake | Technology Services ? Mundocom | Re:Sources IT
35 West Wacker Drive, Suite 3000 | Chicago, IL 60601
Office: 312-220-1669 | Mobile: 312-519-5632
Email: Eric.Winkelhake at us-resources.com
Open a Service Desk Ticket | Navigating IT | Training Now

[snook]

("The downloaded package could not be verified.")

In our case this was a problem when we had http package distribution turned
on for our CasperShare.

Disabling http in the JSS Utility or JSS Web fixed our issues.

JAMF support

Do you have HTTP enabled? If so, are they pointed to the correct file share? Another reason may be that the packages may be too big if going through HTTP. Can you disable HTTP, redeploy and see what happens.

--------
Kevin D Snook
Senior Macintosh Systems Administrator
Desktop Services - IT Enterprise Systems
Appalachian State University
2020 Raley Hall - Boone, NC 28608
828-262-6682
--------
Apple Certified Desktop Technician
Apple Sales Professional
Apple Product Professional

[Eyoung]

There is a known bug with the JSS setup utility that can enable the HTTP download feature. Launching the utility and authenticating is enough to trigger it. to verify, log into your JSS and make sure HTTP is set to "no" for your distribution points....

unless you use HTTP then just please ignore me :-)

[tatiang]

You're right. I just verified that. Thanks for the advice!

Tatian