Jamf Imaging problems with 10.3.0 ?

I have the same issue. I even checked that the option to "Require login for PreStage Imaging and Autorun imaging" is not checked.

Yes. I too am having the exact same issue. And, it started after I upgraded to JAMF Pro 10.3.0. I have a ticket in with JAMF Support. I will certainly update here if we figure anything out.

Is this an issue with JSS v10.3 or JAMF Imaging v10.3? i.e. if you use JAMF Imaging 10.2.x with your JSS v10.3 do you still have the issue?

This seems to be more an issue with 10.3 Jamf Pro and not Jamf Imaging.

I was on an unrelated support call and brought this thread to my account reps attention.

not trying to be jerky, and it's not going to be relevant much longer with imaging dying, but imaging can be tested pre upgrade in a test environment. It's part of my upgrade checklist that might be helpful to some. Might help ease some of the pain of upgrades.

I can confirm this happens in our 10.3 Development environment tested using both 10.2.x and 10.3 versions of the Jamf Imaging apps..

@gbidwell we're imaging fine with 10.2.1 in production. I won't test 10.3 until it's been out a few weeks in case 10.3.1 is rushed out to fix some issue.

Edit: nevermind now i see what you're saying. Your development is 10.3 and you were testing various versions of apps. Got it, sorry.

I got a response from JAMF Support this morning that cleared up the problem for me. Whatever account you are using for imaging cannot have a password with non-alphanumeric characters in it. Once the password is changed to one that is strictly letters and numbers, JAMF Imaging works just fine. I am assuming that this is a glitch that JAMF will fix soon, but at least imaging can happen until then. Granted, imaging as a whole is definitely on the way out, but I am glad I have it operational again, especially for the older Macs in my school.

I have passwords that are only Alphanumeric and the issue persists.

Any response from JAMF about a fix for this? I am holding off on upgrading until this is fixed. This really should be addressed ASAP since it BREAKS imaging, which worked fine.

I cancelled my upgrade too. I don't think any of our techs use special characters, but it's not worth the headache if they do.

Jamf is aware of this issue and currently reviewing both workarounds and finding a fix.

Wow... what is it with Jamf and "good" passwords. This is not the first time we've run into a bug related to passwords,

Data point for other folks, removing the non-alpha-numeric (aka things that make good passwords) digits from my password solved the problem for us.

It turns out that a special character in the username will also trigger this bug. So, both username and password must not contain non-alphanumeric characters. It's still possible to conform to MS complexity requirements (3 out of 5): Upper character, Lower character, and Number. However, this bug is still silly.

The special characters PI was patched in Jamf Pro 10.4.0.
http://docs.jamf.com/10.4.0/jamf-pro/release-notes/Bug_Fixes_and_Enhancements.html

Jamf Imaging [PI-005660] Fixed an issue that caused an error to display when imaging computers using Jamf Pro administrator passwords containing special characters. Note: When interacting with the Jamf API, the encoding for credentials must be UTF-8. Failure to use this encoding may cause authentication issues with the Jamf API when the username or password contain certain international characters.

Anyone know if this was fixed in the new 10.4 release?

Hey @raven.dover I just tried it on our Dev environment and it looks like it is working fine on 10.4

Ok so the 10.4 update did NOT fix the issue for me. I have to remove special characters from my login.

I will submit a bug notice.

@raven.dover i'd file a support ticket if i were you - you may be dealing with something else entirely. Hope you figure it out!

haha already done!

Never mind it did work for me. I had to put JAMF Imaging 10.4 on my boot stick to image.