Seeing triple recon during finishing steps in JSM 1.4.4

[fraserhess]

In the following finishing log there are two three recons. One during setting the computer name, one for userEntry and then another. This should be consolidated.

2026-02-20T15:47:23Z default [general] starting 'Set Computer Name to b22088'
2026-02-20T15:47:23Z default [general] launch '/Applications/Utilities/Setup Manager.app/Contents/Resources/setComputerName.sh b22088'
2026-02-20T15:47:39Z default [general] starting 'Store User Data'
2026-02-20T15:47:39Z default [general] completed 'Set Computer Name to b22088' (16.5608s)
2026-02-20T15:47:39Z default [general] completed 'Store User Data' (0.0018s)
2026-02-20T15:47:39Z default [general] starting 'Update inventory and assign user data'
2026-02-20T15:47:39Z default [general] launch '/usr/local/jamf/bin/jamf recon -verbose -assetTag 22088'
2026-02-20T15:47:53Z default [general] completed 'Update inventory and assign user data' (14.2073s)
2026-02-20T15:47:53Z default [general] created flag file at /private/var/db/.JamfSetupEnrollmentDone
2026-02-20T15:47:53Z default [general] deleted agent and daemon
2026-02-20T15:47:53Z default [general] starting 'Update inventory'
2026-02-20T15:47:53Z default [general] launch '/usr/local/jamf/bin/jamf recon -verbose'
2026-02-20T15:47:55Z default [general] posted finished notification (status: 200)
2026-02-20T15:48:08Z default [general] starting 'Re-loading Jamf Recurring Check-in'
2026-02-20T15:48:08Z default [general] completed 'Update inventory' (14.4567s)
2026-02-20T15:48:08Z default [general] launch '/bin/launchctl bootstrap system /Library/LaunchDaemons/com.jamfsoftware.task.1.plist'
2026-02-20T15:48:08Z default [general] releasing hold on sleep
2026-02-20T15:48:08Z default [general] completed 'Re-loading Jamf Recurring Check-in' (0.0605s)
2026-02-20T15:48:08Z default [general] Setup Manager finished!

[Isokoloff]

Also doing a late-stage double recon if userEntry is not used but computerNameTemplate is. Perhaps the recon in setComputerName.sh can be removed as the Finishing phase verbose recon is assured to kick off shortly after the rename.

2026-02-18T20:39:06Z default [general] starting 'Set Computer Name to ELSM-FVQ7X3F73Q'
2026-02-18T20:39:06Z default [general] launch '/Applications/Utilities/Setup Manager.app/Contents/Resources/setComputerName.sh ELSM-FVQ7X3F73Q'
2026-02-18T20:39:59Z default [general] starting 'Store User Data'
2026-02-18T20:39:59Z default [general] completed 'Set Computer Name to ELSM-FVQ7X3F73Q' (53.2125s)
2026-02-18T20:39:59Z default [general] completed 'Store User Data' (0.0022s)
2026-02-18T20:39:59Z default [general] created flag file at /private/var/db/.JamfSetupEnrollmentDone
2026-02-18T20:39:59Z default [general] deleted agent and daemon
2026-02-18T20:39:59Z default [general] starting 'Update inventory'
2026-02-18T20:39:59Z default [general] launch '/usr/local/jamf/bin/jamf recon -verbose'
2026-02-18T20:39:59Z default [general] posted finished notification (status: 200)
2026-02-18T20:40:52Z default [general] completed 'Update inventory' (53.3329s)
2026-02-18T20:40:52Z default [general] starting 'Re-loading Jamf Recurring Check-in'

[scriptingosx]

so the double recon when a userEntry is present was implemented intentionally as a reaction to a change in the jamf binary to fix #177

The triple recon you might be seeing seems to be another change in the jamf binary. It looks like it added an automatic recon when doing jamf setComputerName

I'll look into that, but will continue to err on the side more recons, rather than less

[fraserhess]

@scriptingosx there's an explicit recon in the included setComputerName.sh script which is the first one chronologically, but the third one we found

[scriptingosx]

so there is... who put that there!? 🤦

[fraserhess]

I won't expose the responsible party on the internet