We in a 10.1 environment that we host ourselves and lately we've had a few machines stop talking to our JSS. However, when we attempt to re-enroll the devices the enrollment using a fresh QuickAdd.pkg the process stalls out and eventually fails. Looking at the installer log show that it stalls out at this point with the following output.
Removing client SUUpdateServiceClient pid=1521, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)
The binary appears to be installed as jamf help responds in terminal, but recon as well as manual enrollments stall out during locating hardware information.
Currently this is happening on a 10.12.6 and a pair of 10.13.3 machines.
We've seen this too, and as for the 'Supplemental Update' bug, we don't track software updates in the JSS so the db schema wouldn't need a change to accommodate.
Enrollment processes never finish when using DEP, because recon hangs. QuickAdd reenrollments fail because recon hangs. Working with Jamf on the issue, but haven't figured it out yet.
@eosrebel We had an EA hanging up the process, but after that was remedied, our DEP enrollment never finishes. If we kill the bash processes or killall jamf and run a sudo jamf policy then things kick in... but whatever condition that enroll is hitting just hangs it.
Our environment is a cluster of 3 tomcat nodes, 1 db server, 1 memcached server.
Hi All, We are seeing similar issue with using any quickadd package, even the self enrolled one using the jamfcloud URL.
I also have tracked it down to Cylance. The problem is that we have had Cylance for almost a year, and this issue didn't start till recently.
But now no matter which version of cylance we install seems to hang Quickadd.
We use a DeployStudio workflow to install the OS then name the computer join it to domain install Office (in process to moving more of this workflow into Jamf) do some other customizations that SIP doesn't allow while booted intot he OS like set DefaultUSer Template (like in the old days of phatimaging) part of this workflow i would install Cylance and then the final was a quickadd package. All was working for about a year. Then something changed, at first I thought it was Jamf Pro 10 upgrade, but after a week or so of troubleshooting it was Cylance. It just would allow Quickadd to finish. Then i moved Cylance into an enrollment policy which also wouldn't finish quickadd process. So finally i moved Cyalnce to a check in policy after quickadd already finished.
So the only issue i need to solve now is, if Cylance is installed and we run the quickadd package (manually by a tech or using the URL by the end user) on a wild machine that has not been in Jamf yet with out reimaging.
I am working with my AV tam so hope to have a solution in the next few days, I will report back here if I find one.
@eosrebel we are seeing our DEP Jamf enrollments stall out for 10 or 15 minutes, always correlated to the same line you referenced in the install log, in your investigation did this line play into the root cause?
MacBook-Pro softwareupdated: Removing client SUUpdateServiceClient pid=2715, uid=0, installAuth=NO rights=(), transactions=0 (/usr/sbin/softwareupdate)