recon error with 10.13.4 pending

tcandela
Valued Contributor II

we have 10.13.3 running with the supplemental update installed. Now that 10.13.4 updates are available I am getting that same recon error that occured before 10.13.3 supplemental update was installed.

there was an error unknown error - an unknown error has occured

is anyone else getting this same error/issue again?

10 REPLIES 10

easyedc
Valued Contributor II

which version of JAMF Pro? We have seen this with 10.13.2 as well. Performing a

jamf enroll -prompt

has fixed it for us.

tcandela
Valued Contributor II

i'm not going through that jamf enroll -prompt. just for this. All my enrollments are fine

TJ_Edgerly
New Contributor III

Not seeing the recon issue in our environment.

OS: 10.13.4
JSS: 9.101.0

*Note: I did however get a machine that prompted for the "User Approved MDM Enrollment" notification under the profiles section.

tcandela
Valued Contributor II

@TJ.Edgerly did you have 10.13.3 installed at the time of recon? or 10.13.4?

I ran the softwareupdate -ai command manually from the terminal to get it up to 10.13.4. and will run jamf recon to see if recon passes

TJ_Edgerly
New Contributor III

@tcandela I ran 2 scenarios:

10.12.6 update to 10.13.4 using app store
10.13.3 (with supplemental update) update to 10.13.4 using app store

remyb
Contributor

Which version of JAMF pro are you on?

This issue was fixed in 10.2.0

See: https://www.jamf.com/jamf-nation/discussions/25648/high-sierra-supplemental-update-breaks-recon

tcandela
Valued Contributor II

@remyb I am on JSS 9.101.0-t1504998263

after i manually install the 10.13.4 update, recon will then complete succesfully

i just did the 'sudo jamf recon' command from terminal on another mac that is running 10.13.3 and get the same 'unknown error'

remyb
Contributor

So this is probably the issue described in the above thread.... Upgrade to at least 10.2.0 or apply the workaround in the thread

tcandela
Valued Contributor II

I'll request that we get upgraded to 10.2.0

tcandela
Valued Contributor II

deleted post, wrong discussion