I'm now seeing it repeatedly when I assign Site access to an account. Users get hit with that error anytime they try to image with a configuration. If I don't select a config and Casper Imaging sets the name and fixes the ByHost files, then I'm able to image without a hitch. Is there any way to assign permissions to different imaging configurations to allow all users in all Sites access?
Just a quick note to let you know that we are aware of this issue. We are currently are seeing this issue when using Netboot with a user that is a member of a LDAP Group and that LDAP group is added into the JSS. If you are seeing this issue please contact your Account Manger to discuss workarounds for this issue. If this doesn't seem to match the how/where/when you are seeing this issue please contact your Account Manager to further troubleshoot this issue. You can reference this issue with D-005557 in the release notes of future releases for the Casper Suite.
After the upgrade to JSS v9.2 had this notification and was resolved but making a fixed account have Access Level "Full Access" and Privilege Set to "Administrator". Not ideal, so will be looking through these posts to try identify what could be the cause. Will also email our channel rep quoting D-005557 for any possibles answers.
We are seeing this error while using Casper Imaging 9.21 with the JSS running 9.21.
The tech can log into Casper Imaging, but when they press the "Install" button, the error appears.
Because of other related permission errors with Casper Remote, I had been setting each account Privilege Set to Administrator, then back to Custom and reducing to what I thought was needed. What I need is a Privilege set just for techs that image Macs, or a better understanding of each and every privilege.
The short term and very undesirable solution has been to set the Privilege sets to Administrator.
I was getting this issue on my netboot image. I trashed the 9.2.3 casper imaging app as well as the jamf preferences in the user library. I then navigated to my JSS URL in safari and viewed the certificate. I dragged it to the desktop and then double clicked it to bring up Keychain. I made sure it was installed in the Login and System keychain and changed it to always trust. I then installed the Casper Imaging 9.2.4 and now I don't get this error anymore. Before I had to always check the "Allow untrusted SSL".
Posted 10/25/13 at 7:48 AM by Matt JSS Objects: Computer Enrollment Invitations All Computers All but Delete Enrollment Profiles All Mobile Device Enrollment Profiles All Mobile Devices All but Delete Recon: Both of them checked Casper Imaging: Use Casper Imaging
Thanks Matt, Your solution fixed my problem
I was just having this same issue a few days ago and it seemed to be because my password contained symbols in it. My password contained a + and a @. I created a second account with identical permissions and used a password only containing letters and numbers and the error went away. I was able to successfully image using a non-Admin account and only giving the user the permissions as suggested by Matt.
I'm seeing this error as well despite having complete admin access for the account I'm using.
After upgrading from 9.65 -> 9.82 we've had this issue. It's also worth noting that our NBIs are having difficulties seeing the JSS. The DNS hostname of the JSS resolves fine in the terminal, but casper imaging will not communicate with the JSS unless you enter the IP in the JSS location box. Once you connect using the IP instead of the hostname, we get this error when we try to image.
Edit: We're also using autoDMG and AutoCasperNBI for NBI creation.
I am now seeing this issue for the first time, and we just upgraded to 10.3.
So, @anickless , Are you saying that the special character in my AD password is causing this problem? Basically, I have to change my password to not include special characters just to get Jamf imaging to work. Not cool. Anyone else have an update on this?