jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-02-03 14:13:24 +00:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

Setup Manager Failed | Waiting for Jamf App Failed #58

New Issue
Closed
opened 2026-01-19 18:31:23 +00:00 by michael · 3 comments
michael commented 2026-01-19 18:31:23 +00:00
Owner
Copy Link

Originally created by @Saysor on GitHub.

We are experiencing recurring issues during macOS enrollment using the SetupManager. The enrollment process is occasionally interrupted entirely, which significantly impacts its reliability in production environments.

Observed Behavior
• Enrollment randomly fails to complete.
• No clear error message is shown.
• Logs suggest a hang or timeout within the SetupManager.
• Sometimes the process completes successfully without any issues.

Initial Assumptions (Ruled Out)

At first, we suspected our internal company Wi-Fi as the root cause. However, the issue also occurs:
• on home Wi-Fi,
• as well as on wired LAN connections

This makes network infrastructure an unlikely cause.

Affected Environment
• Various networks (corporate, home, LAN)
• Multiple different devices (not limited to specific hardware)
• Latest version of Jamf SetupManager

Severity
• Critical, as the problem disrupts the entire enrollment process.
• Difficult to reproduce, since it happens sporadically.
• No clear root cause identified so far.

Attached: Logs, Screenshots

Additional Notes

This has become increasingly frustrating, as it’s difficult to pinpoint the issue. Any support or suggestions would be greatly appreciated.

LOG from one Device:

7:12:05 AM Setup Manager v1.2.2 (561)
7:12:05 AM runAt: enrollment, runningAt: enrollment, console user: _mbsetupuser
7:12:05 AM preventing display and system sleep
7:12:06 AM MDM server URL: https://CENSORED.jamfcloud.com/mdm/ServerURL (CENSORED)
7:12:06 AM MDM detected as Jamf Pro
7:12:06 AM starting 'Waiting for Jamf Binary…'
7:12:06 AM posted launch notification (status: 200)
7:12:24 AM completed 'Waiting for Jamf Binary…' (18.2721s)
Exit Code: 0
7:12:24 AM starting 'Waiting for Jamf configuration…'
7:12:27 AM starting 'Waiting for Jamf Keychain…'
7:12:27 AM completed 'Waiting for Jamf configuration…' (3.1943s)
Exit Code: 0
7:12:30 AM completed 'Waiting for Jamf Keychain…' (3.0714s)
Exit Code: 0
7:12:30 AM starting 'Waiting for Jamf.app…'
7:22:31 AM fatal action! 'Waiting for Jamf.app…' failed! Stopping everything...
7:22:31 AM starting 'Warten…'
7:22:31 AM completed 'Waiting for Jamf.app…' (600.3213s)
Exit Code: 0
7:22:31 AM releasing hold on sleep
7:22:36 AM completed 'Warten…' (5.0369s)
Exit Code: 0
7:22:36 AM cancelled 'Jamf Inventar aktualisieren'
7:22:36 AM cancelled 'Warten…'
7:22:36 AM cancelled 'Waiting for Jamf Binary, again…'
7:22:36 AM cancelled 'Waiting for Jamf.app again…'
7:22:36 AM cancelled 'Unloading Jamf Recurring Check-in'
7:22:36 AM fatal action! 'Waiting for Jamf Binary, again…' cancelled! Stopping everything...
7:22:36 AM fatal action! 'Waiting for Jamf.app again…' cancelled! Stopping everything...
4:23:42 PM Setup Manager v1.2.2 (561)
4:23:42 PM runAt: enrollment, runningAt: loginwindow, console user:

Image
Image
Image
Image

Originally created by @Saysor on GitHub. We are experiencing recurring issues during macOS enrollment using the SetupManager. The enrollment process is occasionally interrupted entirely, which significantly impacts its reliability in production environments. Observed Behavior • Enrollment randomly fails to complete. • No clear error message is shown. • Logs suggest a hang or timeout within the SetupManager. • Sometimes the process completes successfully without any issues. Initial Assumptions (Ruled Out) At first, we suspected our internal company Wi-Fi as the root cause. However, the issue also occurs: • on home Wi-Fi, • as well as on wired LAN connections This makes network infrastructure an unlikely cause. Affected Environment • Various networks (corporate, home, LAN) • Multiple different devices (not limited to specific hardware) • Latest version of Jamf SetupManager Severity • Critical, as the problem disrupts the entire enrollment process. • Difficult to reproduce, since it happens sporadically. • No clear root cause identified so far. Attached: Logs, Screenshots Additional Notes This has become increasingly frustrating, as it’s difficult to pinpoint the issue. Any support or suggestions would be greatly appreciated. LOG from one Device: > 7:12:05 AM Setup Manager v1.2.2 (561) 7:12:05 AM runAt: enrollment, runningAt: enrollment, console user: _mbsetupuser 7:12:05 AM preventing display and system sleep 7:12:06 AM MDM server URL: https://CENSORED.jamfcloud.com/mdm/ServerURL (CENSORED) 7:12:06 AM MDM detected as Jamf Pro 7:12:06 AM starting 'Waiting for Jamf Binary…' 7:12:06 AM posted launch notification (status: 200) 7:12:24 AM completed 'Waiting for Jamf Binary…' (18.2721s) Exit Code: 0 7:12:24 AM starting 'Waiting for Jamf configuration…' 7:12:27 AM starting 'Waiting for Jamf Keychain…' 7:12:27 AM completed 'Waiting for Jamf configuration…' (3.1943s) Exit Code: 0 7:12:30 AM completed 'Waiting for Jamf Keychain…' (3.0714s) Exit Code: 0 7:12:30 AM starting 'Waiting for Jamf.app…' 7:22:31 AM fatal action! 'Waiting for Jamf.app…' failed! Stopping everything... 7:22:31 AM starting 'Warten…' 7:22:31 AM completed 'Waiting for Jamf.app…' (600.3213s) Exit Code: 0 7:22:31 AM releasing hold on sleep 7:22:36 AM completed 'Warten…' (5.0369s) Exit Code: 0 7:22:36 AM cancelled 'Jamf Inventar aktualisieren' 7:22:36 AM cancelled 'Warten…' 7:22:36 AM cancelled 'Waiting for Jamf Binary, again…' 7:22:36 AM cancelled 'Waiting for Jamf.app again…' 7:22:36 AM cancelled 'Unloading Jamf Recurring Check-in' 7:22:36 AM fatal action! 'Waiting for Jamf Binary, again…' cancelled! Stopping everything... 7:22:36 AM fatal action! 'Waiting for Jamf.app again…' cancelled! Stopping everything... 4:23:42 PM Setup Manager v1.2.2 (561) 4:23:42 PM runAt: enrollment, runningAt: loginwindow, console user: <nil> ![Image](https://github.com/user-attachments/assets/4e1a05db-8527-4678-acc3-eae4baae7c20) ![Image](https://github.com/user-attachments/assets/d3fcd181-214c-40ed-bb67-5906d2d91dd0) ![Image](https://github.com/user-attachments/assets/bf550788-7dd1-4310-9cdc-f34fd337c1d2) ![Image](https://github.com/user-attachments/assets/9cb25353-8864-4a6a-b0eb-6a174eba152a)
michael added the Support label 2026-01-19 18:31:23 +00:00
michael commented 2026-01-19 18:31:23 +00:00
Author
Owner
Copy Link

@Saysor commented on GitHub:

Hi @scriptingosx I was able to fix this issue with my network colleague and the new beta with the network change.
The Problem was that we deployed an SCEP Profile with 802.1x Wifi in it with Install automatically .

This caused the network changes in the Setupmanager enrollment.
Maybe this can added as Instruction that no WiFi Profile will be installed automatically before enrollment complete.

Also thanks for the nice JNL Session in Munich.

BR

@Saysor commented on GitHub: Hi @scriptingosx I was able to fix this issue with my network colleague and the new beta with the network change. The Problem was that we deployed an SCEP Profile with 802.1x Wifi in it with **Install automatically** . This caused the network changes in the Setupmanager enrollment. Maybe this can added as Instruction that no WiFi Profile will be installed automatically before enrollment complete. Also thanks for the nice JNL Session in Munich. BR
michael commented 2026-01-19 18:31:23 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

can you test with Setup Manager 1.3beta and share logs from there?

@scriptingosx commented on GitHub: can you test with Setup Manager 1.3beta and share logs from there?
michael commented 2026-01-19 18:31:23 +00:00
Author
Owner
Copy Link

@fabian1195 commented on GitHub:

We saw the same issue with version 1.2.2 when script based extension attributes are used. Especially when the value is empty.

@fabian1195 commented on GitHub: We saw the same issue with version 1.2.2 when script based extension attributes are used. Especially when the value is empty.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
enhancement
question
Support
wontfix
No Label Support
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#58
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?