Not asking on my behalf, but I figured others are going to ask. Is there going to be a patch for customers on v9.101? An official answer would probably be appreciated by customers.
I'm going to guess the answer is no. I'm perfectly fine with that since we're on v10 already and it makes less sense to dedicate software engineering resources to backtrack changes to a previous version of a product.
and the special characters bug for imaging is not addressed either?
I saw that it wasn't listed, I was asking again for formal clarification.
We really would like to know if the Imaging issue (authentication / invitation) is fixed. This is really a significant problem.
Dan
Considering imaging is a major component of the software that is broken, I sure hope it was fixed and not JUST an IOS issue.
Awesome to hear I'm not alone with imaging being broken and finding that excruciatingly annoying.
I haven't tested 10.3.1 yet to see if imaging has been fixed. But my current work around for 10.3 is to make a standard account with a password that is only characters and numbers. Then share that to the team doing imaging for a temporary workaround.
example username = imaging
example password = 1234qwer
Not asking on my behalf, but I figured others are going to ask. Is there going to be a patch for customers on v9.101? An official answer would probably be appreciated by customers.
@bpavlov No. Jamf has made it clear to me they will not be doing further development work on version 9. I've been through denial, anger, bargaining, depression, and, finally, acceptance. We're updating to Jamf Pro 10.3.1 this Thursday for better or worse. Initial testing has been positive. Fingers crossed!
@mojo21221 That is what we did for a work around as well. It works, but it certainly isn't the best solution. I was really hoping that the update would fix the issue.
We are still running 10.2.2. Will be interested to hear from anyone running 10.3.1 to see how well it works for them. It sounds like the imaging thing can be worked around with an imaging password with no special characters. I'm not sure I've heard about any other issues.
Looks like I am not the only one with Imaging "invitation" issues. I hope it will be fixed soon.
Just updated this morning on our development server to 10.3.1 and as you can see the Jamf Imaging issue has not been resolved for. I Also noticed when opening the Jamf Imaging app and when it goes into the authenticate box to the Jamf Pro Server, the username and password boxes don't show the cursor, you can type but then when you tab it doesn't go to the next line you actually have to click on the password box to go to the next one. I only saw it on Jamf Imaging the other apps seems fine. I tried it on multiple machines etc. etc.
Still up in the air if we are going to update and do the work around of creating a standard user for imaging.
I tried to download the latest version. Somehow I keep getting 10.3.0-t1521825567 instead of the announced version. Tried the root.war file in the Apple installer and the root.war file from the manual install.
I'm puzzled?!
edit: After some backtracking: I did download the latest version and that is the 10.3.1 version. In my installation environment I forgot to update the version number so the old warfile got installed. No panic, all's well :-)
Thanks for the update. Facing this issue currently.
My db server has been blowing up ever since running this update. Normally, CPU is around 4% - 10% and InnoDB hovers around 60%. It's been pushing data all night. Have a ticket in but wondering if anyone else has seen this?
- Nothing else in the environment appears to have changed. My environment variables for Tomcat appear to be untouched.
Sorry I'm a newbie, what does it mean to remain in a failed MDM loop?
@kmorrow Basically, the iOS devices trapped in the loop wouldn't/couldn't report inventory back to the JSS. So, if the JSS (the MDM), can't read-out the devices' state it can't manage it. If the device can't/won't report it's state, it can't be managed - in so far as new MDM commands are issued. ...the device just loops on it's last executed command and is "stuck" until the report of it's state is sent/received.
@gabe2385 On that dev server if you run 'truncate enrollment_inviations;' on the jamfsoftware db, and the restart Tomcat, do you see the same error? With backups if you need them before of course.
I ask because when I upgrade to 10.3, mine fails due to failure to migrate enrollment invitations. The workaround in support was to truncate that table. Just tested imaging in my dev instance, and it works fine.
@chris.miller I definitely noticed 10.3.1 being slower than 10.3 in my testing. Are you seeing that in an upgrade from 10.3 to 10.3.1? Or from an earlier version than that?
@chris.miller Did you get a response to your ticket ? I was thinking of updating but your post isn't instilling me with
confidence.
@lashomb , I tried to run the 'truncate table enrollment_invitations;' command and it did not work for me. Maybe I will reach out to support next week and they have something else up there selves.
@gabe2385
if username or password contains any special characters you will receive that error.
@gabe2385 We are seeing this too now unfortunately. We're just working around it using local account for imaging.
@chris.miller What are you using to monitor in that screenshot?
