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

Jamf Setup Manager installing Jamf Connect at login window #101

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

Originally created by @fraserhess on GitHub.

In my testing, having Jamf Setup Manager install Jamf Connect at the login window, will result in Jamf Connect killing the loginwindow process and Jamf Setup Manager does not complete successfully.

I am working around this by faking a Setup Assistant process so that Jamf Connect Login's postinstall script thinks it's being installed during Setup Assistant and exits.

I'd much rather that Jamf Connect detects that Jamf Setup Manager is installing it, or that Jamf Connect had a silent install option, where the binaries are put on disk but don't launch until after the next restart.

https://ideas.jamf.com/ideas/ID-I-432

Originally created by @fraserhess on GitHub. In my testing, having Jamf Setup Manager install Jamf Connect at the login window, will result in Jamf Connect killing the `loginwindow` process and Jamf Setup Manager does not complete successfully. I am working around this by faking a `Setup Assistant` process so that Jamf Connect Login's postinstall script thinks it's being installed during Setup Assistant and exits. I'd much rather that Jamf Connect detects that Jamf Setup Manager is installing it, or that Jamf Connect had a silent install option, where the binaries are put on disk but don't launch until after the next restart. https://ideas.jamf.com/ideas/ID-I-432
michael added the bug label 2026-01-19 18:31:32 +00:00
michael commented 2026-01-19 18:31:32 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

implemented finishedTrigger and finishedScript in 1.3 which can be used to perform installations outside of the Setup Manager process.

@scriptingosx commented on GitHub: implemented `finishedTrigger` and `finishedScript` in 1.3 which can be used to perform installations outside of the Setup Manager process.
michael commented 2026-01-19 18:31:32 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

https://github.com/jamf/Setup-Manager/discussions/96

@scriptingosx commented on GitHub: https://github.com/jamf/Setup-Manager/discussions/96
michael commented 2026-01-19 18:31:32 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

we are working on a solution for this, though not in the way you described

@scriptingosx commented on GitHub: we are working on a solution for this, though not in the way you described
michael commented 2026-01-19 18:31:32 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

using this LaunchDaemon to run the installation (from a policy or Installomator) after Setup Manager is finished should do the trick. https://github.com/scriptingosx/SetupManagerFinishedScript

If you want this to be integrated into Setup manager, please create a feature request

@scriptingosx commented on GitHub: using this LaunchDaemon to run the installation (from a policy or Installomator) after Setup Manager is finished should do the trick. https://github.com/scriptingosx/SetupManagerFinishedScript If you want this to be integrated into Setup manager, please create a feature request
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 bug
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#101
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?