Hello,

Bug/issue in versions 1.4.2 and 1.4.3 where
/usr/local/jamf/bin/jamf recon -verbose is logged but not executed during enrollment completion.
This prevents Extension Attributes from detecting the completed enrollment state, even though the flag file is created (/private/var/db/.JamfSetupEnrollmentDone). Version 1.4.1 works as expected.

Environment

• Version: JSM 1.4.2 / 1.4.3
• Last known working version: 1.4.1
• macOS: 26.2
• Deployment: Jamf Pro (tested with different Jamf Pro Versions and servers.)
• Hardware: Apple Silicon (also with different MacBooks)
• Network: reproduced in multiple networks (corporate and home)

Steps to Reproduce

1. Perform device enrollment
2. Wait for setup workflow to complete
3. Observe logs during "Update inventory"
4. Check Extension Attribute reading enrollment status

Expected Behavior

• jamf recon -verbose should execute successfully after enrollment completion so that:
• inventory is updated
• Extension Attributes can detect enrollment completion via ".JamfSetupEnrollmentDone" file

Example Log File
2026-02-05T13:03:55Z default [general] completed 'Update inventory and assign user data' (17.8848s)
2026-02-05T13:03:55Z default [general] created flag file at /private/var/db/.JamfSetupEnrollmentDone
2026-02-05T13:03:55Z default [general] deleted agent and daemon
2026-02-05T13:03:55Z default [general] starting 'Update inventory'
2026-02-05T13:03:55Z default [general] launch '/usr/local/jamf/bin/jamf recon -verbose'
2026-02-05T13:03:55Z default [general] starting 'Re-loading Jamf Recurring Check-in'
2026-02-05T13:03:55Z default [general] launch '/bin/launchctl bootstrap system /Library/LaunchDaemons/

Thank you for your support — I really appreciate it.