Skip to main content

Hi,



back again, got soms logs of one of our clients and it still seems after the Jamf Binary upgrades the devices checks for enrollmentComplete!
Watch out with upgrading, i can trigger one of your workflows.



Got an case open @jamf11



2019-03-26 16:02:57+01 lmos-08421 installd[1221]: ./postinstall: Submitting data to https://jss.local.nl.bol.com:8443/...

2019-03-26 16:02:58+01 lmos-08421 installd[1221]: ./postinstall: <computer_id>697</computer_id>

2019-03-26 16:02:58+01 lmos-08421 installd[1221]: ./postinstall: Getting management framework from the JSS...

2019-03-26 16:02:59+01 lmos-08421 installd[1221]: ./postinstall: Enforcing management framework...

2019-03-26 16:02:59+01 lmos-08421 installd[1221]: ./postinstall: Checking availability of https://jss.local.nl.bol.com:8443/...

2019-03-26 16:03:00+01 lmos-08421 installd[1221]: ./postinstall: The JSS is available.

2019-03-26 16:03:02+01 lmos-08421 installd[1221]: ./postinstall: Enforcing login/logout hooks...

2019-03-26 16:03:03+01 lmos-08421 installd[1221]: ./postinstall: Enforcing scheduled tasks...

2019-03-26 16:03:03+01 lmos-08421 installd[1221]: ./postinstall: 2019-03-26 16:03:03.663 jamf[1329:8845] *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid

2019-03-26 16:03:03+01 lmos-08421 installd[1221]: ./postinstall: Creating launch daemon...

2019-03-26 16:03:04+01 lmos-08421 installd[1221]: ./postinstall: Creating launch agent...

2019-03-26 16:03:04+01 lmos-08421 installd[1221]: ./postinstall: Creating jamfAAD launch agent...

2019-03-26 16:03:04+01 lmos-08421 installd[1221]: ./postinstall: Checking availability of https://jss.local.nl.bol.com:8443/...

2019-03-26 16:03:04+01 lmos-08421 installd[1221]: ./postinstall: The JSS is available.

2019-03-26 16:03:07+01 lmos-08421 installd[1221]: ./postinstall: Enroll return code: 0

2019-03-26 16:03:10+01 lmos-08421 installd[1221]: ./postinstall: Upgrading jamf binary...

2019-03-26 16:03:12+01 lmos-08421 installd[1221]: ./postinstall: The management framework will be enforced as soon as all policies are done executing.

2019-03-26 16:03:16+01 lmos-08421 installd[1221]: ./postinstall: Checking for policies triggered by "enrollmentComplete" for user "PRIVATE"...

2019-03-26 16:03:20+01 lmos-08421 installd[1221]: ./postinstall: No policies were found for the "enrollmentComplete" trigger.

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: Writing receipt for QuickAdd10.1.1-t1513360285 to /

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: Installed "casper" ()

2019-03-26 16:03:21+01 lmos-08421 install_monitor[1234]: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: releasing backupd

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: allow user idle system sleep

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: ----- End install -----

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: 62.9s elapsed install time

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: Running idle tasks

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: Removing client PKInstallDaemonClient pid=1211, uid=0 (/usr/sbin/installer)

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: Done with sandbox removals

2019-03-26 16:03:22+01 lmos-08421 installer[1211]: Removing temporary directory "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T//Install.1211rVPiex"

2019-03-26 16:03:22+01 lmos-08421 installer[1211]: Finalize disk "Macintosh HD"

2019-03-26 16:03:22+01 lmos-08421 installer[1211]: Notifying system of updated components

2019-03-26 16:03:22+01 lmos-08421 installer[1211]: 

2019-03-26 16:03:22+01 lmos-08421 installer[1211]: **** Summary Information ****

2019-03-26 16:03:22+01 lmos-08421 installer[1211]:   Operation      Elapsed time

2019-03-26 16:03:22+01 lmos-08421 installer[1211]: -----------------------------

2019-03-26 16:03:22+01 lmos-08421 installer[1211]:        zero      0.00 seconds

2019-03-26 16:03:22+01 lmos-08421 installer[1211]:        disk      0.03 seconds

2019-03-26 16:03:22+01 lmos-08421 installer[1211]:     install      63.67 seconds

2019-03-26 16:03:22+01 lmos-08421 installer[1211]:     -total-      63.69 seconds

2019-03-26 16:03:22+01 lmos-08421 installer[1211]:

Bump! be warned

@txhaflaire This section of the log is confusing to me:



2019-03-26 16:03:07+01 lmos-08421 installd[1221]: ./postinstall: Enroll return code: 0

2019-03-26 16:03:10+01 lmos-08421 installd[1221]: ./postinstall: Upgrading jamf binary...

2019-03-26 16:03:12+01 lmos-08421 installd[1221]: ./postinstall: The management framework will be enforced as soon as all policies are done executing.

2019-03-26 16:03:16+01 lmos-08421 installd[1221]: ./postinstall: Checking for policies triggered by "enrollmentComplete" for user "PRIVATE"...

2019-03-26 16:03:20+01 lmos-08421 installd[1221]: ./postinstall: No policies were found for the "enrollmentComplete" trigger.

2019-03-26 16:03:21+01 lmos-08421 installd[1221]: PackageKit: Writing receipt for QuickAdd10.1.1-t1513360285 to /


Did you run a QuickAdd package on the Mac above? Or was this a normal, Mac checked in to the console, saw that there is a new binary version and downloaded? I see both lines saying the jamf binary needs to be upgraded, but also



PackageKit: Writing receipt for QuickAdd10.1.1-t1513360285 to /


Which seems to indicate it installed a QuickAdd.pkg, though the version shown there doesn't make sense. It says 10.1.1?



If this was a regular check-in, jamf binary gets upgraded process, and it caused an enrollment complete policy check, then that's just silly, and Jamf needs to fix that ASAP.



Thanks for posting about it and bringing it to our attention.

Yeah correct. It seems to pick up an old wuickadd somewhere from the database. It gets enrolled with an old management account. We do not have that version / name of the quickadd stored anywhere

Besides after that enrollment they have newest binary

Jamf.log



Tue Mar 26 16:03:04 lmos-08421 jamf[1787]: Informing the JSS about login for user PRIVATE

Tue Mar 26 16:03:07 lmos-08421 jamf[1329]: Enroll return code: 0

Tue Mar 26 16:03:07 lmos-08421 jamf[1787]: Daemon starting

Tue Mar 26 16:03:08 lmos-08421 jamf[1787]: Informing the JSS about login for user PRIVATE

Tue Mar 26 16:03:10 lmos-08421 jamf[1833]: Upgrading jamf binary...

Tue Mar 26 16:03:12 lmos-08421 jamf[1833]: The management framework will be enforced as soon as all policies are done executing.

Tue Mar 26 16:03:16 lmos-08421 jamf[1914]: Checking for policies triggered by "enrollmentComplete" for user "PRIVATE"...

Tue Mar 26 16:03:20 lmos-08421 jamf[1914]: Adding launchd task com.jamfsoftware.task.checkForTasks...

Tue Mar 26 16:03:24 lmos-08421 jamf[2003]: Enforcing management framework...

End of the ride; It was on an bunch of devices old QuickAdd.pkg's that got installed by Caspercheck. Why? dont know because those packages where there for months + years. So reviewing the caspercheck mechanism and 10.11 as a combination.



it where local cached .pkg that got installed located at /var/root/quickadd/casper.pkg which containts various versions from 10.1.1 to 10.7. :



So, it should be safe to upgrade to 10.11, this issues have nothing to do with the upgrade. (besides things got triggered somewhere)

Terms & ConditionsCookie settings